Skill

---
name: SKILL_NAME
description: Use when [SPECIFIC_TRIGGERING_CONDITIONS_AND_SYMPTOMS]. Triggers on phrases like [EXAMPLE_PHRASES].
metadata:
  internal: true
---

<!--
  This is a scaffold template — not a real skill. `metadata.internal: true`
  keeps it hidden from the Skills CLI (`npx skills add ... --list`) so
  downstream users don't see an unfilled "SKILL_NAME" entry alongside real
  skills. When you copy this template into your own `skills/<name>/SKILL.md`,
  DELETE the `metadata.internal: true` line.
-->


# Skill Title

## Overview

What this skill does in 1–2 sentences. State the core principle.

## When to Use

- Trigger condition 1 (concrete symptom or scenario)
- Trigger condition 2
- Trigger condition 3

**When NOT to use:** Specific cases where another approach fits better.

## Workflow

<!--
  Shape this section to match the skill's nature:
    - Phased orchestration skills  → "### Phase 1 — NAME" / "### Phase 2 — NAME" ...
    - Linear procedures            → numbered steps
    - Formatters / validators /    → freeform sections ("Rules", "Checks", "Output format")
      style skills                   — no phases or steps needed
  Delete the scaffolding below that doesn't fit and replace with what does.
-->

Describe how the skill actually runs. If it has ordered stages, list them. If it's a set of rules applied in any order, list the rules. If it's a single checked transformation, just say so.

### Section 1 — NAME

What to do. What to produce.

### Section 2 — NAME

What to do. What to produce.

## Quick Reference

| Step | Question | Tool | Output |
|---|---|---|---|
| 1 | ... | ... | ... |
| 2 | ... | ... | ... |

## Common Mistakes

| Mistake | Fix |
|---|---|
| ... | ... |

## Red Flags — You're Doing It Wrong

- Symptom 1
- Symptom 2