composio

Files (6)

• SKILL.md
• adding-a-toolkit-pack.md · references/
• auth-and-accounts.md · references/
• error-recovery.md · references/
• search-execute-pattern.md · references/
• write-safety.md · references/

SKILL.md (first lines)

# Composio (Hermes runtime)

## Overview

This skill is the umbrella entrypoint for the Composio Hermes plugin. Capability comes from a **small stable tool surface**, not from dumping the whole Composio catalog into the model schema.

Prefer loading a toolkit skill before non-trivial app work:

| App | Skill |
| --- | --- |
| Gmail | `composio:composio-gmail` (+ `composio:composio-gmail-inbox-triage` for inbox ranking) |
| GitHub | `composio:composio-github` (+ `composio:composio-github-pr-triage` for PR attention) |

## Preferred Deliverables

- Clear connection/status answers with profile + `user_id`
- Shortlisted tool slugs with why they match
- Read results summarized with scope/confidence
- Drafts before sends; explicit confirmation before side effects

## Core Loop

1. If auth/account state is uncertain: `composio_status` (or `composio_connections`).
2. If the toolkit is disconnected: `composio_connect` with the toolkit slug; tell the user to open `redirect_url`, then re-check status.
3. Discover actions with `composio_search` using a concrete use case string.
4. If arguments are unclear: `composio_schema` on the chosen slug.
5. Execute with `composio_execute`.
6. For raw endpoints with no slug: `composio_proxy` (mutating methods need `confirmed=true` unless yolo).

## Reference Notes

| Topic | Reference |
| --- | --- |
| Auth, profile user ids, single-account v1 | [references/auth-and-accounts.md](./references/auth-and-accounts.md) |
| Search → schema → execute pattern | [references/search-execute-pattern.md](./references/search-execute-pattern.md) |
| Write safety + yolo | [references/write-safety.md](./references/write-safety.md) |
| Error recovery | [references/error-recovery.md](./references/error-recovery.md) |
| Adding a new toolkit pack | [references/adding-a-toolkit-pack.md](./references/adding-a-toolkit-pack.md) |

## Write Safety

- Default to read and draft.
- Side-effectful slugs require `confirmed=true` after explicit user intent, unless Hermes yolo / `approvals.mode=off`.
- Never invent destructive args. Prefer `composio_schema`.
- v1 is single-account per toolkit; do not silently switch accounts.

## Output Conventions

- Lead with the answer, then evidence.
- State which toolkit/account and which tool slug produced the result when useful.
- If results are truncated, say so and offer a narrower query.

## Example Requests

- "What Composio apps are connected?"
- "Connect Gmail."
- "Find the tool to list unread mail, then fetch the latest 10."
- "Search GitHub tools for open PRs in my repo."

## Light Fallback

If Composio is unconfigured, say `COMPOSIO_API_KEY` is missing and point to `hermes composio login-help` / `/composio login-help`.

From kamellperry/hermes-composio, MIT.

More from kamellperry/hermes-composio