skill

Topics in the source

• Skill
• When to use
• Overview
• Layout
• Frontmatter
• Body
• Linking
• Agents

User asks to create, rename, split, merge, or rewrite a ni skill, agent, or command A skill does not trigger, or triggers on unrelated prompts A SKILL.md grows past 300 lines or carries content another skill also needs User asks how ni is laid out, linked, validated, or installed A skill is a reference guide for a proven technique, not a story about one task. It loads only when its description matches the prompt, so the description decides whether the body is ever read. Write the smallest body that changes behaviour. Every ni skill fits one plugin. Same voice, same sections, same linking. A new skill that reads like its neighbours costs the reader nothing to learn. Template: template.md. Copy it, then delete the sections you do not need. Names are short nouns or noun pairs, lowercase, hyphens: plan, tdd, code-review. Folder name equals frontmatter name. Claude exposes it as ni: . Description rules: 1. Triggers first. Say when to load. One short clause on what the skill is may precede it. Never summarise the workflow: a description that summarises the steps gets followed instead of the body. 2. Start with "Use when". Third person. Double quotes. Name under 64 characters. 3. List con

This is an excerpt. Refer to the complete source and its current requirements.