Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Route and complete Composio work across Composio For You and Composio Platform.
Install Composio
$ npx skills add ComposioHQ/composio --skill composio -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ComposioHQ/composio composio --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/composio .claude/skills/composio && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "composio" agent skill from https://github.com/ComposioHQ/composio/tree/next/skills/composio into .claude/skills/composio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composio", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ComposioHQ/composio/tree/next/skills/composioType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ComposioHQ/composio --skill composio -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ComposioHQ/composio composio --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/composio .agents/skills/composio && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "composio" agent skill from https://github.com/ComposioHQ/composio/tree/next/skills/composio into .agents/skills/composio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composio", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ComposioHQ/composio --skill composio -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ComposioHQ/composio composio --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/composio .cursor/skills/composio && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "composio" agent skill from https://github.com/ComposioHQ/composio/tree/next/skills/composio into .cursor/skills/composio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composio", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ComposioHQ/composio.git --path skills/composio--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ComposioHQ/composio --skill composio -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ComposioHQ/composio composio --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/composio .gemini/skills/composio && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "composio" agent skill from https://github.com/ComposioHQ/composio/tree/next/skills/composio into .gemini/skills/composio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composio", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ComposioHQ/composio composioInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ComposioHQ/composio --skill composio -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/composio .github/skills/composio && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "composio" agent skill from https://github.com/ComposioHQ/composio/tree/next/skills/composio into .github/skills/composio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composio", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ComposioHQ/composio --skill composio -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ComposioHQ/composio composio --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/composio .opencode/skills/composio && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "composio" agent skill from https://github.com/ComposioHQ/composio/tree/next/skills/composio into .opencode/skills/composio/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composio", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
composio- GitHub stars
- 30k
- Used in
- 1 other repo
- Token cost
- ~1.7k tokens
- SKILL.md length
- 903 words
- Files
- 4 (incl. references)
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Route and complete Composio work across Composio For You and Composio Platform.
- Works in 3 steps: Choose the product → Choose the job → Load only the relevant guidance
- The user mentions Composio
- SKILL.md covers 1. Choose the product, 2. Choose the job, 3. Load only the relevant… and Complete the selected job, plus 2 more sections
- Reaches docs.composio.dev; needs COMPOSIO_API_KEY
What it does
Composio is an agent skill from ComposioHQ/composio. Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help diagnosing a connection or tool call.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/errors.md`, `references/for-you.md` and `references/platform.md`).
It sits in Productivity & Automation, covering App automation through connectors and MCP servers. It works with Composio, GitHub, Gmail and Notion. The repository describes itself as: Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action. The licence is MIT.
When your agent uses it
- The user mentions Composio
- Wants an agent to use apps such as Gmail
- Needs first-time setup
- MCP integration
Example prompts
- “/composio”
Requirements
- A credential in COMPOSIO_API_KEY
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f6f9667. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.composio.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
COMPOSIO_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Composio loads about 1.7k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 903 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ComposioHQ/composio at commit f6f9667, republished under its MIT licence (© ComposioHQ). 903 words, ~1,658 tokens.
Download SKILL.mdSave it as
.claude/skills/composio/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- composio
- description
- Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help diagnosing a connection or tool call.
Composio
Use this skill as a router. Identify the product and the job, load only the relevant guidance, consult canonical documentation for volatile details, and then answer or do the work the user requested.
1. Choose the product
Do not blend the products. They use different credentials and setup paths.
| Composio For You | Composio Platform | |
|---|---|---|
| Use when | Someone wants their own agent to use their own apps | A developer is building a product whose users connect accounts |
| Primary surface | MCP or the Composio CLI | SDK sessions inside an application |
| Credential | ck_... consumer key when the client requires a header | COMPOSIO_API_KEY project key |
| Dashboard | dashboard.composio.dev → For You | dashboard.composio.dev → Platform |
Ask one short question only when context does not establish the product:
Is this for your own agent and accounts, or for a product where your users connect their accounts?
Treat a named personal AI client with no product code as For You. Treat an application codebase, SDK, user or tenant identity, backend, or product agent as Platform.
2. Choose the job
Identify the requested outcome before taking action:
- Explain or discover: answer a question, compare approaches, or find the current API.
- Set up: establish credentials, an MCP client, the CLI, or an SDK for the first time.
- Build or change: integrate Composio into an existing agent or application.
- Operate: find, connect, and run tools for a real task.
- Debug or migrate: diagnose a failure, update an older integration, or move from legacy direct execution or Tool Router.
Do not turn an explanation, documentation lookup, or narrow bug fix into onboarding.
3. Load only the relevant guidance
- For You: read Composio For You.
- Platform: read Composio Platform.
- Provider, connection, or execution failure: also read Errors and provider gotchas.
Complete the selected job
- For a question, fetch current documentation when needed and give the concrete answer. Do not mutate a project or force a tool call.
- For setup or integration, inspect the existing environment, preserve its architecture and identity model, make the smallest useful change, and verify it with one safe real tool call when credentials and user authorization are available.
- For an operational request, connect only the apps the task needs and execute the requested workflow.
- For debugging, get the Composio log or request ID, identify the failing boundary, fix that boundary, and retry when the user authorized execution.
Stable rules
- Establish the product before choosing credentials, URLs, SDKs, or commands.
- Treat dashboard onboarding as a context, not the skill's identity. When the developer arrives with an existing
COMPOSIO_API_KEYfrom Getting Started, use it and never create, rotate, replace, print, or request it in chat. Do not runcomposio dev initin that path. - For a general first-time Platform setup with no dashboard credential handoff, follow the current setup path in the Platform guide.
- Never invent toolkit or tool slugs. Discover them at runtime or with the CLI.
- Do not build a provider OAuth flow. Composio returns a Connect Link when authentication is needed.
- Use sessions for new Platform integrations. Preserve the application's existing user identity and agent architecture.
- Keep credentials out of source control, URLs, logs, chat, and command output.
- Get the log or request ID before diagnosing a failed tool call.
- Prefer the smallest configuration that completes the current job. Keep toolkit filters, tag policies, sandbox controls, custom auth, provider-specific hardening, and other advanced options out of the first path unless the request or existing code requires them.
- Do not invent repository facts. Never claim that a file, framework, environment loader, identity field, agent path, or dependency exists until it was provided or inspected. If codebase context is unavailable, state the unknown and ask for access or one necessary detail.
- In SDK or API examples, use exact identifiers and call shapes from a current public page or schema. Copy the documented shape for the requested language instead of translating names between TypeScript and Python; if a required detail is not documented, explain the behavior without inventing code.
Show full SKILL.md (235 more words)Show less
Canonical information
Use bundled references for stable decisions. A user-facing source list contains only public https://docs.composio.dev/... pages actually consulted; bundled reference names, local paths, and file:// URLs are omitted. For versions, provider adapters, client-specific setup, toolkit behavior, or APIs that may have changed, use the current canonical documentation and current CLI or tool schemas as the primary sources before answering or editing code:
When sources disagree, prefer the current API reference and live endpoint behavior over any page marked Legacy, and name the REST API version explicitly.
https://docs.composio.dev/llms.txt
https://docs.composio.dev/docs/<page>.md
https://docs.composio.dev/toolkits/<toolkit>.mdIf those primary sources do not answer a Composio product or troubleshooting question, query the public unified knowledge search at https://docs.composio.dev/api/knowledge-search?q=<question>.
Results may be canonical docs, KB, toolkit, example, or reference pages. Use the returned evidence to answer the question; public records do not establish the live state of a user's account, project, connection, or tool call.
When knowledge search supplies evidence, cite the result's returned canonicalUrl, not the search API URL. If canonicalUrl is relative, prefix it with https://docs.composio.dev before citing it.
Only treat a result as evidence when its excerpt or page directly addresses the question. If no public source directly documents an exact error or symptom, say so instead of diagnosing from adjacent results; request the log or request ID, or the necessary live evidence.
Use the documentation to complete the task. Do not merely hand the user a link unless they asked for one.
© ComposioHQ, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/composio of ComposioHQ/composio.
- SKILL.md
- references/errors.md
- references/for-you.md
- references/platform.md
Open the folder on GitHubat commit f6f9667
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in ComposioHQ/composio, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Composio next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Composio this skillComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Composio Cloud Toolsquarqlabs/argus | 277 | — | ~543 | Automated safety check: Pass | Apache-2.0 | |
| Openloomi Connectorsmelandlabs/openloomi | 1k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| ConnectComposioHQ/awesome-claude-skills | 77k | 3 repos | ~987 | Automated safety check: Pass | None | |
| Superset Integration Toolssuperset-sh/superset | 15k | — | ~1.6k | Automated safety check: Warn | Custom licence |
Similar skills
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Openloomi Connectors
melandlabs/openloomi
openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…
Connect
ComposioHQ/awesome-claude-skills
Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.
Superset Integration Tools
superset-sh/superset
Lists and calls the tools of connected integrations such as Linear, GitHub, Sentry or Notion through the superset mcp command, without storing a token on the machine.
Integrations
butterbase-ai/butterbase-skills
Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…
More from ComposioHQ/composio
Effect V4
ComposioHQ/composio
Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to effect@4.0.0-rc.117 — Context.Service and explicit layers…
CLI Release
ComposioHQ/composio
Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification…
Good Docs Audit
ComposioHQ/composio
Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations.
Good Docs Writing
ComposioHQ/composio
Writing style guide derived from Modal's documentation voice.
CLI Command
ComposioHQ/composio
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, effect/unstable/cli, services, output conventions, configuration and environment variables, and local vendor…
Typescript Testing
ComposioHQ/composio
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests.
Related
Categories
Questions about Composio
What does Composio do?
Route and complete Composio work across Composio For You and Composio Platform. Composio is an agent skill from ComposioHQ/composio. Route and complete Composio work across Composio For You and Composio Platform.
When should I use Composio?
Composio fits situations like: the user mentions Composio; wants an agent to use apps such as Gmail; needs first-time setup; MCP integration.
How do I install Composio in Claude Code?
Run `npx skills add ComposioHQ/composio --skill composio -a claude-code`. Or copy the skill folder (skills/composio in ComposioHQ/composio) into .claude/skills/composio in your project. Claude Code loads it when a task matches its description.
How do I install Composio in Codex?
Run `npx skills add ComposioHQ/composio --skill composio -a codex`. Or copy the skill folder (skills/composio in ComposioHQ/composio) into .agents/skills/composio in your project. Codex loads it when a task matches its description.
Can I use Composio in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ComposioHQ/composio --skill composio -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/composio, .gemini/skills/composio, .github/skills/composio and .opencode/skills/composio in your project.
What does Composio need to run?
Going by SKILL.md and its folder, Composio needs credentials named COMPOSIO_API_KEY. Our summary lists: A credential in COMPOSIO_API_KEY.
Does Composio access the network?
SKILL.md names 1 domain. In commands or code: docs.composio.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Composio safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Composio use?
Composio is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Composio use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.
What are the alternatives to Composio?
Skills that share tags, products or a category with Composio: Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Composio Cloud Tools (quarqlabs/argus, 277 stars), Openloomi Connectors (melandlabs/openloomi, 1k stars) and Connect (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Composio?
ComposioHQ (a GitHub organization) maintains it in ComposioHQ/composio, which has 30,467 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.
Source: ComposioHQ/composio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.