skill-template

1# Skill Name
2 
3Provide a clear, concise description of what this skill covers and when to use it. This description appears in skill discovery and should help agents (and humans) determine when this skill is relevant.
4 
5**Important**: Keep the total SKILL.md body under 500 lines for optimal performance. Move detailed reference material to separate files in the `references/` directory.
6 
7Every skill body must make its ownership boundary explicit. The description and `When to Activate` section should say what the skill owns and which adjacent skills own nearby work. This prevents broad skills from stealing activation from narrower skills.
8 
9## When to Activate
10 
11Describe specific situations, tasks, or contexts where this skill should be activated. Include both direct triggers (specific keywords or task types) and indirect signals (broader patterns that indicate skill relevance).
12 
13Write in third person. The description is injected into the system prompt, and inconsistent point-of-view can cause discovery problems.
14 
15- Good: "Processes Excel files and generates reports"
16- Avoid: "I can help you process Excel files"
17 
18Include a short "Do not activate" block for adjacent skills. Example:
19 
20- Do not activate for project-level pipeline shape: `project-development`.
21- Do not activate for individual tool schema design: `tool-design`.
22 
23## Core Concepts
24 
25Explain the fundamental concepts covered by this skill. These are the mental models, principles, or frameworks that the skill teaches.
26…