Repository navigation
Skill Format
Eclipse Ghost edited this page Jul 7, 2026
·
1 revision
Every skill lives in skills/<name>/ with this structure:
skills//
├── SKILL.md # main content
├── metadata.json # machine-readable metadata
├── examples/ # runnable code samples
├── prompts/ # ready-made agent prompts
└── tests/ # validation tests
- Overview — what the API/tool does, in 2-3 lines
- Installation — real install commands (npm/pip/etc.)
- Authentication — how auth actually works, key types, where to get them
- Core Concepts — key terms/objects the agent needs to know
- Common Workflows — step-by-step for the most frequent tasks
- Error Handling — real error codes/types and how to handle them
- Security — things that will bite you if ignored (secrets, webhook verification, etc.)
- Rate Limits — actual numbers, not vague statements
- Best Practices — patterns that avoid common mistakes
- Troubleshooting — real gotchas, not generic advice
- References — links to official docs
See skills/stripe/SKILL.md for a full example.
{
"name": "stripe",
"version": "1.0.0",
"description": "...",
"categories": ["Payments", "Commerce"],
"languages": ["typescript", "python"],
"license": "MIT",
"links": { "API Reference": "https://..." },
"schemaVersion": "1.0.0",
"supportedAgents": ["cursor", "claude-code", "cline", "continue"],
"lastVerified": "2026-07-03"
}- No placeholder text, no "TODO," no vague filler.
- Every command/API call must be real — verified against actual docs.
- Code in
examples/should run, not just look plausible. -
lastVerifieddate must reflect an actual check, not be copy-pasted.
Full schema: SPECIFICATION.md