agentleFS
Sign inStart free
ezocomp118-sourceezocomp118-source/twiko/.agents/skills/composio/SKILL.md

composio

Skill2 starsChanged 3 months agoApache-2.0View on GitHub

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.

  • Reads credentials

32 other projects use a version of this, 7 of them edited; 4 new projects in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 4 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 4 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use albert-dm, new-client-system and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yawningwhaleAISkill

    albert-dm

    Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).

    Also in 5 projects that use this

  • yawningwhaleAISkill

    new-client-system

    Scaffold a new client's full stack — Next.js 16 frontend dashboard + Trigger.dev backend worker — from the Shiney automations template. Use when the user says "new client", "onboard a client", "scaffold a client system", "set up <client-name>", or wants to start a fresh frontend+backend project styled and structured like the Shiney automations dashboard. Produces structure only; no automations are scaffolded — those are added later.

    Also in 6 projects that use this

  • xfstudioSkill

    trigger-dev

    Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

    Also in 11 projects that use this

  • huyvpSkill

    cost-reducer

    Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.

    Also in 9 projects that use this

  • ffsshhttiikkSkill

    scalability

    Core foundational concepts and principles for Scalability

    Also in 9 projects that use this

  • RoxenRobloxSkill

    youtube-broll-maker

    Generate 10-second B-roll footage of yourself doing an action using the Higgsfield MCP (Seedance 2.0). Upload one photo of yourself, describe the action ("typing on laptop", "walking at night"), pick from 5 cinematography style presets, get an MP4. Use when the user wants B-roll, cutaway footage, "me doing X" video, YouTube B-roll, or any image-to-video of themselves performing an action.

    Also in 3 projects that use this

  • +4 more from yawningwhaleAI

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 14 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill as a router.

    line 8
  2. Distinctive:

    Do not blend the products.

    line 12
  3. Distinctive:

    Ask one short question only when context does not establish the product:

    line 21
  4. Distinctive:

    Treat a named personal AI client with no product code as For You.

    line 25
  5. Distinctive:

    Do not turn an explanation, documentation lookup, or narrow bug fix into onboarding.

    line 37
  6. Very specific:

    Treat dashboard onboarding as a context, not the skill's identity.

    line 55
  7. Distinctive:

    Never invent toolkit or tool slugs.

    line 57
  8. Distinctive:

    Do not build a provider OAuth flow.

    line 58
  9. Distinctive:

    Use sessions for new Platform integrations.

    line 59
  10. Distinctive:

    Keep credentials out of source control, URLs, logs, chat, and command output.

    line 60
  11. Distinctive:

    Prefer the smallest configuration that completes the current job.

    line 62
  12. Distinctive:

    Do not invent repository facts.

    line 63
  13. Distinctive:

    Use bundled references for stable decisions.

    line 67
  14. Distinctive:

    When sources disagree, prefer the current API reference and live endpoint behavior over any page marked Legacy, and name the REST API …

    line 69
  15. Distinctive:

    Use the documentation to complete the task.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 YouComposio Platform
Use whenSomeone wants their own agent to use their own appsA developer is building a product whose users connect accounts
Primary surfaceMCP or the Composio CLISDK sessions inside an application
Credentialck_... consumer key when the client requires a headerCOMPOSIO_API_KEY project key
Dashboarddashboard.composio.dev → For Youdashboard.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

  1. Establish the product before choosing credentials, URLs, SDKs, or commands.
  2. Treat dashboard onboarding as a context, not the skill's identity. When the developer arrives with an existing COMPOSIO_API_KEY from Getting Started, use it and never create, rotate, replace, print, or request it in chat. Do not run composio dev init in that path.
  3. For a general first-time Platform setup with no dashboard credential handoff, follow the current setup path in the Platform guide.
  4. Never invent toolkit or tool slugs. Discover them at runtime or with the CLI.
  5. Do not build a provider OAuth flow. Composio returns a Connect Link when authentication is needed.
  6. Use sessions for new Platform integrations. Preserve the application's existing user identity and agent architecture.
  7. Keep credentials out of source control, URLs, logs, chat, and command output.
  8. Get the log or request ID before diagnosing a failed tool call.
  9. 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.
  10. 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.

Canonical information

Use bundled references for stable decisions. For versions, provider adapters, client-specific setup, toolkit behavior, or APIs that may have changed, fetch the current Markdown source 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>.md

Use the documentation to complete the task. Do not merely hand the user a link unless they asked for one.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free