/SKILL.md`).
## Creating Skills
Skill layout:
```
skill-name/
├── SKILL.md # Required: instructions + YAML frontmatter
├── scripts/ # Optional: helper scripts for deterministic steps
├── references/ # Optional: long-form docs loaded only when needed
└── assets/ # Optional: templates or files used in outputs
```
Basic SKILL.md template:
```markdown
---
name: my-skill-name
description: What the skill does and when Codex should use it.
---
# My Skill Name
Clear instructions and steps for Codex to execute the task.
```
Best practices:
- Keep the `description` exhaustive about when to trigger; keep the body focused on execution steps.
- Use progressive disclosure: put detailed references in `references/` and call them out from `SKILL.md` only when needed.
- Include scripts for repeatable or deterministic operations; mention when Codex should run them.
- Avoid extra docs (README, changelog) inside the skill folder to keep context lean.
## Contributing
PRs welcome. Add real, reusable skills, keep descriptions precise, and include any needed scripts or references. If you add new skills, ensure the `description` clearly states when Codex should trigger and test that metadata fits within context limits.
## Join the Community
- [Join our Discord](https://discord.com/invite/composio) - Chat with other developers building Codex skills.
- [Follow on X](https://twitter.com/composio) - Updates on new skills and features.
- Questions? [support@composio.dev](mailto:support@composio.dev)
---
Join thousands of developers building agents that ship