Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 16:00 UTC
feat(skills): publish the Composio agent skill (#4084)
## Summary - publish the first-party `composio` skill from the SDK repository - route first by product (Composio For You or Composio Platform), then by the requested job - preserve progressive disclosure, credential safety, and a strict evidence boundary - explain exactly what the CLI, raw MCP, OpenAI/Codex plugin, and Claude Code plugin make discoverable ## Starting point This keeps Palash's generic router design and Soumya's canonical-link and cross-language corrections from temporary-repository PRs [#1](https://github.com/composio-temp/composio-skill/pull/1) ([Glen](https://app.tryglen.com/composio-temp/composio-skill/pull/1)) and [#2](https://github.com/composio-temp/composio-skill/pull/2) ([Glen](https://app.tryglen.com/composio-temp/composio-skill/pull/2)). The maintained copy now lives with Composio's SDK, CLI, and docs source instead of the temporary evaluation repository. ## Installation and discovery Project-scoped, with agent selection when needed: ```bash npx skills add ComposioHQ/composio --skill composio ``` Global, non-interactive install for the detected agent: ```bash npx skills add ComposioHQ/composio --skill composio --global --yes ``` This public skill is installed explicitly. A raw MCP connection exposes tools but does not install a skill. The CLI-owned `composio-cli` skill and the OpenAI plugin-owned `composio-runtime` skill remain separate because they own current CLI operation and hosted-versus-local runtime routing, respectively. The Claude Code plugin does not bundle another skill. ## Dashboard handoff Dashboard Getting Started is one context handled by the generic Platform route, not the skill's identity. When the developer already has the Step 1 `COMPOSIO_API_KEY`, the skill uses that existing project key, never creates or replaces it, avoids `composio dev init`, and inspects the real agent path and user identity before proposing code. ## Forward evaluation Four blind requests were run through fresh agents: 1. Personal Cursor access to Gmail and Google Calendar passed the For You/MCP route and avoided Platform credentials. 2. First-time Python setup initially overexposed advanced options; after progressive-disclosure rules, the replay stayed on the minimum SDK/session/auth path. 3. A GitHub 401 with a working project key remained a narrow provider-auth debugging task and did not restart onboarding. 4. A TypeScript dashboard handoff initially invented repository facts; after the evidence boundary, the replay preserved the key and requested the actual framework and entrypoint. These are manual routing and response-quality evaluations, not reusable eval infrastructure. A live provider/OAuth run remains part of the separate dashboard E2E gate. ## Validation - skill-creator validator: passed - canonical repository validator: 18 skills passed before this documentation-only follow-up - routing smoke test: 18/18 probes passed - isolated local `skills add --copy`: passed - current head CI: pending after the discovery clarification - no SDK package, backend, CLI, database, or release-metadata changes
No changes.