Build the open registry for agent intelligence.
Every skill, playbook, soul and guardrail in our network starts as a YAML file in a public GitHub repo. Download what you need. Fork what's almost right. Ship what's missing — and it lands in front of every agent on the platform.
Four steps from idea to merged PR.
- 01
Fork & clone
Fork on GitHub, clone locally, install deps with bun install.
git clone git@github.com:<you>/super-agent-skill.git bun install - 02
Copy a template
Each folder ships a _template.yaml. Rename it to your slug and fill it in.
cp content/skills/_template.yaml content/skills/my-skill.yaml - 03
Validate locally
The validator checks schema, slug uniqueness, file naming and minimum quality.
bun run validate:content - 04
Open a PR
Use the Package submission template. A maintainer reviews for safety, quality and overlap.
Pick what fits — split if it doesn't.
Skills
Single sharply-scoped capabilities with an input → output contract. The atomic unit.
Playbooks
Multi-step decision graphs that orchestrate skills and tools for a recurring scenario.
Souls
Personality and value layers that bias an agent's tone, taste and trade-offs.
Guardrails
Refusal, safety and compliance policies enforced before a response leaves the agent.
A package is accepted when it…
- Has a clear, scoped purpose — does one thing well.
- Includes at least 2 worked examples with realistic input + exact expected output.
- States must and must_not rules explicitly.
- Uses a unique kebab-case slug not already in the registry.
- Is original work, public-domain, or properly attributed.
- Contains no secrets, PII or copyrighted prompts from a paid product.
Validate locally with bun run validate:content before opening a PR. CI runs the same script.
Ready to ship something?
Open a PR or start a discussion. Maintainers review for quality, safety and overlap, then your package is imported into the live registry on the next sync.