@devries-cameron20 / composio Mirror · read-only
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

next
md 2.03 KB

Skill Format

Canonical Tree

  • .agents/skills is canonical.
  • .claude/skills is a compatibility symlink to .agents/skills.
  • Do not maintain parallel hand-edited skill copies.

Required Structure

Each skill directory must contain SKILL.md with YAML frontmatter:

---
name: skill-name
description: What the skill does and when to use it.
---

Rules:

  • name must match the directory name.
  • Use lowercase letters, digits, and hyphens only.
  • Include trigger boundaries in description; it is the routing surface agents see before loading the body.
  • Keep SKILL.md short. Put detailed examples, command recipes, and package-specific notes in first-level references/*.md.
  • Link every reference directly from SKILL.md; avoid nested reference-chasing.
  • Do not add agents/openai.yaml unless repo tooling explicitly needs UI metadata.

Primary Sources Checked

  • OpenAI Codex Agent Skills docs: skills are directories with SKILL.md, optional scripts/, references/, assets/, and optional agents/.
  • Claude Agent Skills docs: every skill requires SKILL.md frontmatter with name and description.
  • VS Code Agent Skills docs: name should match the parent directory and use lowercase hyphenated identifiers.

Validation

Run:

bun run validate:agent-skills
bun run validate:skill-routing

Both validators are deterministic, and .github/workflows/agent-substrate.yml runs them in CI on every push and pull request — the stale-guidance scan covers the whole repo, so any change can affect the result.

validate:agent-skills checks frontmatter, names, reference links, compatibility symlink state, stale guidance references, and known command names.

validate:skill-routing is a deterministic routing smoke test (ts/scripts/test-skill-routing.ts): for representative tasks it asserts the expected skill is the unique top match by distinctive trigger phrases, and fails if any skill has no probe. When you add or rename a skill, or rewrite a description, add or update its probe so routing stays covered.