---

name: skill-name description: Use when users say "[trigger phrase 1]", "[trigger phrase 2]", or when [specific scenario]. [WHAT this skill does]. [Additional trigger keywords for searchability].

CRITICAL: The description field determines if this skill gets activated.

Must answer THREE questions:

1. WHAT: What does this skill do? (functionality)

2. WHEN: In what situations should it be used? (trigger scenarios with "Use when...")

3. KEYWORDS: What terms should trigger this skill? (action verbs, file types, domain terms)

✅ GOOD: "Use when users say 'create X', 'build Y', or when working with .ext files for purpose A, purpose B, or purpose C"

❌ BAD: "Helps with various tasks" (vague, no triggers, no keywords)

license: Apache-2.0 metadata: author: accelint version: "1.0.0"

Skill Name

Brief introduction to what this skill provides (1-2 sentences maximum).

NEVER Do [Domain-Specific Anti-Patterns]

• NEVER [specific anti-pattern 1] - [Why this fails / non-obvious consequence]. [Example if helpful].
• NEVER [specific anti-pattern 2] - [Concrete reason from experience].
• NEVER [specific anti-pattern 3] - [What happens when violated].
• NEVER [generic mistake in this domain] - [Why experts avoid this].
• NEVER [common beginner error] - [Non-obvious reason it's problematic].

Before [Domain Action], Ask

Apply these tests before [performing key domain action]:

[Expert Thinking Framework 1]

• [Key Question]? [Guidance on what to consider]. [Consequence if ignored].
• [Key Question]? [How experts think about this]. [Example if needed].

[Expert Thinking Framework 2]

• [Key Question]? [Critical consideration]. [Trade-off to understand].
• [Key Question]? [Decision criteria]. [What to optimize for].

[Expert Thinking Framework 3]

• [Key Question]? [Edge case consideration]. [When standard approach fails].

How to Use

This skill uses progressive disclosure to minimize context usage:

1. Start with the Workflow (SKILL.md)

Follow the [workflow/decision tree/process] below for [domain task].

2. Reference Implementation Details (AGENTS.md)

Load AGENTS.md for [specific type of guidance: file conventions / optimization rules / architectural patterns].

3. Load Specific Examples as Needed

When [specific scenario], load corresponding reference files for ❌/✅ examples:

• [Scenario 1] → Load reference-file-1.md
• [Scenario 2] → Load reference-file-2.md

[Main Workflow / Decision Tree / Process]

[Your workflow/decision tree/creative guidance here]

Freedom Calibration

Calibrate guidance specificity to task fragility:

Task Type	Freedom Level	Guidance Format	Example
Creative/Design	High freedom	Principles, thinking patterns, anti-patterns	"[Creative principle]"
Analysis/Review	Medium freedom	Guidelines with examples, decision frameworks	"Priority: [ordered list]"
File Operations	Low freedom	Exact scripts, specific steps, no variation	"Use exact command: [cmd]"

The test: "If the agent makes a mistake, what's the consequence?"

• High consequence (corruption, data loss) → Low freedom with precise scripts
• Medium consequence (suboptimal result, style issues) → Medium freedom with examples
• Low consequence (aesthetic choices, multiple valid approaches) → High freedom with principles

Important Notes

• [Critical non-obvious consideration that affects success]
• [Edge case that's easy to miss]
• [Domain-specific constraint or requirement]