skill-architect

Capabilities

Guides users to design and build high-quality Agent skills from scratch, covering standalone skills and MCP-enhanced workflows.

Typical triggers:

• “I want to create a new skill”
• “Help me turn this workflow into a skill”
• “I want to automate this workflow”
• “How do I teach my Agent to do X”
• When you need to author a SKILL.md

Not for: creating subagents or writing technical design documents.

Five-stage workflow

Execute strictly in order; do not skip steps:

① Discovery — clarify the need

• Understand the problem
• Define 2–3 concrete examples
• Clarify triggers and success criteria
• Identify edge cases and existing tooling

② Architecture — pick pattern + outline structure

Choose a suitable pattern:

Plan directory layout and craft description (trigger phrases + negative boundaries).

③ Craft — author content

• Frontmatter (name in kebab-case + description ≤ 1024 chars)
• Instruction body (≤ 500 lines)
• Real examples
• Error-handling paths

④ Validate — check quality

• Structure (frontmatter format, kebab-case, no README.md as substitute)
• Trigger test (does the description actually invoke correctly?)
• Instruction review (ambiguity, redundancy, gaps)

⑤ Deliver — ship

Use skills_create(name, description, content). Pass only Markdown body (# heading onward); no --- frontmatter block in content.

Hard rules

Anti-patterns (avoid)

• description reads like prose with no trigger phrases
• Starting Craft before Discovery
• Pasting raw user chatter into the skill instead of distilled rules
• Missing negative boundaries (“Not for…”)

How to trigger

/skill-architect I want to turn our “weekly report cleanup” routine into a skill

Natural language examples:

• “Help me wrap my common SQL queries in a skill”
• “Teach my Agent how to produce A/B test reports”
• “Turn this workflow into a skill”

Related docs

• skill-refinement — improve an existing skill (vs. greenfield)
• Custom skill development
• Core concepts · Skill system