---
name: your-skill-name
description: One or two sentences. Say WHAT the skill does and WHEN to use it. Name the trigger words and phrases you would actually type. The clearer this is, the more reliably the skill loads at the right moment.
---

# Your Skill Name

<!--
  This is a starter skill file. Rename it to SKILL.md, fill in the four parts
  below, and delete these comment blocks as you go. A good skill is short,
  specific, and written the way you would explain the task to a sharp new hire.
  Source for the format: Anthropic Agent Skills documentation.
-->

## What this does

<!--
  One short paragraph. What is the job? What does "done" look like?
  Example: "Turns a rough set of meeting notes into a clean status update
  with three sections: Decisions, Owners, and Next steps."
-->

## When to use it

<!--
  List the moments this should fire. Be concrete.
  Example:
  - After any client call, when I paste raw notes
  - When I say "write the status update" or "clean up these notes"
  Do NOT use it for: drafting net-new proposals, or anything with no notes yet.
-->

## How to do it

<!--
  Numbered steps, in order. This is the heart of the skill. Write each step as
  an instruction, not a description. Keep one idea per step.
  Example:
  1. Read the notes once before writing anything.
  2. Pull out every decision that was made. Put each under "Decisions."
  3. For each decision, name the owner and the due date. If a date is missing,
     write "date TBD" rather than guessing.
  4. End with a "Next steps" list of three items, biggest impact first.
-->

## Rules and guardrails

<!--
  The non-negotiables. What must always happen, and what must never happen.
  Example:
  - Never invent a name, number, or date that is not in the notes.
  - Keep the whole update under 200 words.
  - If a decision is unclear, flag it with "[needs confirmation]" instead of
    smoothing it over.
-->

---

## Worked example (delete before using)

Here is the same template filled in, so you can see the shape of a finished skill.

```markdown
---
name: weekly-status-update
description: Use after a client or team call when I paste raw meeting notes and want a clean weekly status update. Triggers on "write the status update" or "clean up these notes."
---

# Weekly Status Update

## What this does
Turns rough meeting notes into a clean status update with three sections:
Decisions, Owners, and Next steps. Reads in under a minute.

## When to use it
- After any client or team call, when I paste raw notes
- When I say "write the status update" or "clean up these notes"
Do NOT use it for drafting net-new proposals or anything with no notes yet.

## How to do it
1. Read the notes once before writing anything.
2. List every decision that was made under "Decisions."
3. For each decision, name the owner and the due date. If a date is missing,
   write "date TBD" rather than guessing.
4. End with a "Next steps" list of three items, biggest impact first.

## Rules and guardrails
- Never invent a name, number, or date that is not in the notes.
- Keep the whole update under 200 words.
- Flag anything unclear with "[needs confirmation]" instead of smoothing it over.
```