AI agent? Read this page as Markdown at /skills/install.md — append .md to any docs URL, or start from /llms.txt.

Install Agent Skills

Agent Skills are self-contained instruction packages that teach AI coding agents — like Claude Code, Cursor, and others — how to build against a specific Unified.to API for a common use case. Each skill maps one of our top How-To guides to a ready-to-use SKILL.md file containing the endpoints, authentication, pagination, SDK usage, and sync patterns an agent needs to ship the integration.

Install

Claude Code

Install the Unified.to plugin. It adds every available skill plus the Core MCP server, and prompts for your workspace API key, which it keeps in secure storage:

/plugin marketplace add https://docs.unified.to/.claude-plugin/marketplace.json
/plugin install unified@unified-to

The plugin needs Claude Code v2.1.224 or later. To install only the skills instead, run npx skills add https://docs.unified.to -a claude-code, then add the Core MCP server yourself.

Codex, Cursor, GitHub Copilot, Windsurf, and other agents

Install the skills with the open-source skills CLI. It detects the agents you use and copies the skills into each one's skills folder:

npx skills add https://docs.unified.to

Add --skill unified-quickstart to install one skill, or -a cursor to target one agent. Then connect the Core MCP server so your agent can check integration support, manage connections and webhooks, and read API-call logs: see the configs for Codex, Cursor, VS Code, and other clients.

Any agent that can read a URL

Paste this into your agent. The quick-start skill tells it which category skill to load next:

Add Unified.to integrations to my app: https://docs.unified.to/skills/unified-quickstart/SKILL.md

To install a skill by hand, save its SKILL.md in your agent's skills folder, for example .claude/skills/<name>/SKILL.md for Claude Code or .agents/skills/<name>/SKILL.md for Codex.

Lovable, Replit, Bolt, v0, and other app builders

Paste the quick-start prompt above into the builder's chat. Your Unified.to API key grants access to your whole workspace, so keep it out of frontend code: store it in the builder's server-side secrets and have the agent make Unified.to calls, and handle the Authorization callback, from a backend route or serverless function.

Before you build

Every skill assumes you have the same starting point. Set these up once:

  1. Grab your Workspace ID and API key from Settings → API Keys.
  2. Activate the relevant integration in the Sandbox environment to develop against mocked data.
  3. Add the embedded Authorization component so your end-users can connect their accounts and you receive a connection ID.
  4. Use webhooks to keep data in sync instead of polling.

Next, browse the available skills.

Are we missing anything? Let us know
Was this page helpful?