authoring-skills

Use this skill when creating or modifying agent skills in .agents/skills/ . Create a skill when content is: Keep in AGENTS.md instead when: Only use fields from this list. Unknown fields are silently ignored. The description is the primary matching surface for auto-activation. Include: Skills should tell the agent what to do , not just what to know : When adding a skill, also add a one-liner summary to the relevant AGENTS.md section with a $skill-name reference. For complex skills, use a hub + detail pattern: - Too detailed for AGENTS.md (code templates, multi-step workflows, diagnostic procedures) - Only relevant for specific tasks (not needed every session) - Self-contained enough to load independently - It's a one-liner rule or guardrail every session needs - It's a general-purpose gotcha any agent could hit - What the skill covers (topic) - When to use it (trigger scenario) - Key file names the skill references (e.g. config-shared.ts ) - Keywords a user or agent might mention (e.g. "feature flag", "DCE") - Lead with "Use this skill when..." - Include step-by-step procedures - Add code templates ready to adapt - End with verification commands - Cross-reference related skills in a "Related Skills" section - Short, descriptive, topic-scoped: flags , dce-edge , react-vendoring - No repo prefix (already scoped by .agents/skills/ ) - Hyphens for multi-word names