Skill Creator
Contract
This skill guarantees:
- New skill follows conformance standard (frontmatter + required sections)
- MECE check: no overlap with existing skills' triggers
- Frontmatter
triggers:route the intended phrases - New skill shows up in
list_skills - Skill passes the conformance checks (
memrain skillify check <name>andmemrain skillpack lint)
Phases
- Identify the gap. What capability is missing? What user intent has no skill?
- MECE check. Enumerate the installed skills with
list_skillsand read their frontmattertriggers:viaget_skill. Does any existing skill already cover this? If so, extend it instead of creating a new one. - Create SKILL.md. Use this template:
---
name: {skill-name}
version: 1.0.0
description: |
{One paragraph describing what the skill does and when to use it.}
triggers:
- "{trigger phrase 1}"
- "{trigger phrase 2}"
tools:
- {tool1}
- {tool2}
mutating: {true|false}
---
# {Skill Title}
## Contract
{What this skill guarantees — 3-5 bullet points}
## Phases
{Numbered workflow steps}
## Output Format
{What good output looks like}
## Anti-Patterns
{What NOT to do — 3-5 items}
## Tools Used
{MCP tools used, with descriptions}
- Write the routing. The frontmatter
triggers:array IS the routing — phrase each entry the way a user would actually say it. There is no separate routing file to update. - Confirm discovery.
list_skillsshould return the new slug, andget_skill {name}should return the file you just wrote. - Verify. Run
memrain skillify check <name>andmemrain skillpack lintto confirm the new skill passes conformance.
Output Format
New skills/{name}/SKILL.md file, discoverable via list_skills with
triggers that route.
Anti-Patterns
- Creating a skill that overlaps with an existing one (violates MECE)
- Skipping the MECE check against existing skills
- Creating a skill without triggers in frontmatter
- Shipping a skill that never shows up in
list_skills - Creating a skill without an Anti-Patterns section