We welcome contributions — especially new skills for the music industry.
- Create a new directory under
skills/with aSKILL.md:
skills/my-new-skill/
└── SKILL.md
- Fill in the frontmatter:
---
name: my-new-skill
description: What it does and when to use it. Include trigger phrases.
----
Write clear instructions in the body. Keep it under 5,000 words — move heavy reference material to a
references/subdirectory. -
Open a pull request.
- One skill, one job. Each skill does one thing well.
- Self-contained. No cross-dependencies between skills.
- Description is the trigger. The
descriptionfield determines when an agent loads the skill. Be specific — include the phrases a user would actually say. - Real instructions, not theory. Tell the agent exactly what to do, step by step.
- No secrets. Don't include API keys, tokens, or credentials. Reference environment variables instead.
SKILL.mdbody: under 5,000 words- Put large reference material in
references/ - Put executable code in
scripts/ - Critical instructions go at the top
Be kind, be helpful, build things that help artists.