write-a-skill

原文涵盖的主题

• Writing Skills
• Process
• Skill Structure
• SKILL.md Template
• Description Requirements
• When to Add Scripts
• When to Split Files
• Review Checklist

Derived from Matt Pocock's write-a-skill (MIT). Matt's voice and 3-phase workflow preserved verbatim. Additions: validation tools + references + cs- wrapper (see Tooling + Companions below). 1. Gather requirements - ask user about: What task/domain does the skill cover? What specific use cases should it handle? Does it need executable scripts or just instructions? Any reference materials to include? 2. Draft the skill - create: SKILL.md with concise instructions Additional reference files if content exceeds 500 lines Utility scripts if deterministic operations needed 3. Review with user - present draft and ask: Does this cover your use cases? Anything missing or unclear? Should any section be more/less detailed? The description is the only thing your agent sees when deciding which skill to load. It's surfaced in the system prompt alongside all other installed skills. Your agent reads these descriptions and picks the relevant skill based on the user's request. Goal: Give your agent just enough info to know: 1. What capability this skill provides 2. When/why to trigger it (specific keywords, contexts, file types) Format: Max 1024 chars Write in third person First sentence: what it do

这里只展示节选，请以完整原文和当前要求为准。