@devries-cameron20 / composio-1 / commits / b0dd6fd44
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: add Skills page

Skills are execution playbooks Composio derives from real usage: for one concrete task, the tools it needs, the order to call them in, and the pitfalls that make it fail. The page leads with why that saves work — an agent that has to discover a tool sequence and its failure modes pays for it in tokens and retries — then covers what a skill contains and how to browse the catalog. Skills are dashboard-only today, so this page has no cURL examples. That runs against the usual preference for machine-readable API docs, so the absence is called out explicitly rather than left implicit. A screenshot will be added in a follow-up.

Palash Kala committed Aug 5, 2026 at 19:24 UTC b0dd6fd442cbc39c4ce7f024f44c7d39f79647af
2 files changed +58
docs/content/docs/meta.json
+2
@@ -27,6 +27,8 @@
27 "setting-up-triggers/subscribing-to-events",
28 "setting-up-triggers/managing-triggers",
29 "setting-up-triggers/custom-oauth-webhooks",
30 + "---Skills---",
31 + "skills",
32 "---Security and Data---",
33 "security/overview",
34 "security/data-retention",
docs/content/docs/skills.mdx new
+56
@@ -0,0 +1,56 @@
1 +---
2 +title: Skills
3 +description: Browse the execution playbooks Composio derives from real usage, so your agent spends fewer tokens and fewer retries getting a task right
4 +keywords: [skills, playbooks, use cases, execution plan, pitfalls, tool sequence, efficiency, tokens]
5 +---
6 +
7 +A **skill** is an execution playbook for one concrete task — "send an email to someone", "post a message to a Slack channel", "query a Notion database". Each skill records the tools the task needs, the order to call them in, and the mistakes that make it fail.
8 +
9 +Composio derives skills from real usage across the platform rather than hand-writing them, so the catalog reflects how these tasks are actually completed in practice.
10 +
11 +## Why skills matter
12 +
13 +Handing an agent a toolkit tells it *what* it can call. It does not tell it *how* the call usually goes wrong. An agent discovering that on its own pays for it in tokens and retries:
14 +
15 +- It calls a tool with the wrong identifier, reads the error, and tries again.
16 +- It fetches a whole inbox when it needed one search.
17 +- It skips a lookup step and posts to a channel that never resolves.
18 +
19 +A skill front-loads that knowledge. The sequence is already known, and so are the pitfalls, so the work that would have gone into rediscovering them is not spent at all.
20 +
21 +<Callout type="info">
22 +Skills are read-only. They are a catalog you browse to understand how a task is normally executed — there is nothing to install, enable, or configure.
23 +</Callout>
24 +
25 +## What a skill contains
26 +
27 +**Use case** — the task in plain language, e.g. *Start a direct message with someone in Slack and send a message*. This is what search matches against.
28 +
29 +**Tools** — the tool slugs the task uses, such as `SLACK_FIND_USERS`, `SLACK_OPEN_DM`, `SLACK_SEND_MESSAGE`. A skill distinguishes the main tools from supporting ones.
30 +
31 +**Execution plan** — the ordered steps for completing the task, including optional steps and fallback paths for when the primary route is unavailable.
32 +
33 +**Pitfalls** — the known failure modes for this task: the wrong-identifier mistakes, the missing lookups, the assumptions that do not hold.
34 +
35 +A skill is not limited to one app. A task may span Slack and Gmail, and a skill that spans several toolkits appears under each of them.
36 +
37 +## Browsing skills
38 +
39 +Skills live in the [Composio dashboard](https://platform.composio.dev) under **Skills**, alongside Toolkits.
40 +
41 +You can:
42 +
43 +- **Search by use case** — describe the task the way you would say it ("archive promotional emails from last week") rather than guessing a tool name.
44 +- **Filter by app** — narrow to a single toolkit, or use the app chips to see how many skills each one covers.
45 +- **Open a skill** — see its full execution plan, the tools each step calls, and its pitfalls.
46 +
47 +Browsing with no query lists the catalog by maturity, so the most-refined skills come first.
48 +
49 +<Callout type="warn">
50 +There is no public API for skills yet. The catalog is currently dashboard-only, so unlike most of Composio there is no cURL equivalent for these operations. This page will be updated when an API is available.
51 +</Callout>
52 +
53 +## Related
54 +
55 +- [How Composio works](/docs/how-composio-works) — where tool execution fits in the platform
56 +- [Configuring sessions](/docs/configuring-sessions) — how you give an agent access to tools