How to Create Skills

---
name: your-skill-name
description: >
  What this skill does and when Claude should use it.
  Be specific: mention the types of input (meeting notes,
  code files, support tickets) and the expected output.
---

# Your Skill Name

## Goal
One-sentence description of the skill's purpose.

## Output structure
Define the exact format Claude should produce:
1. Section one
2. Section two
3. Section three (table, list, prose — your choice)

## Guidelines
- Rule one: be concrete, not vague
- Rule two: cover edge cases (what if a field is missing?)
- Rule three: specify tone, length, or style if it matters

## Example
**Input:** Brief example of raw input text.

**Output:**
### [Section heading from your output structure]
[Example of what Claude should produce here]

---
name: meeting-notes-formatter
description: >
  Formats raw meeting notes into a structured summary with
  key decisions, action items, and open questions.
  Use when the user shares meeting notes, a transcript, or
  asks to clean up or summarise meeting content.
---

# Meeting Notes Formatter

## Goal
Turn unstructured meeting notes into a clear, scannable
document that anyone can read in under a minute.

## Output structure
Always produce these four sections in order:

1. **Meeting summary** — 2-3 sentences covering the main
   topic and outcome.
2. **Key decisions** — bulleted list of what was agreed.
3. **Action items** — table with columns:
   | Owner | Task | Due date |
4. **Open questions** — items raised but not resolved.

## Guidelines
- Extract owner names from context; default to "TBD" if unclear.
- Use plain language; keep jargon only if it appears in the notes.
- If no due date is mentioned, leave that column blank.
- Do not infer or add information that isn't in the notes.
- If notes are very short, all four sections may still appear
  (some will just be "None noted.").

## Example

**Input:**
we met today about the Q3 launch. sarah said we should push
back the date by 2 weeks. john will update the roadmap by
friday. still unsure about the pricing model.

**Output:**
### Meeting Summary
The team discussed the Q3 product launch and agreed to a
two-week schedule extension.

### Key Decisions
- Launch date pushed back by two weeks.

### Action Items
| Owner | Task           | Due date |
|-------|----------------|----------|
| John  | Update roadmap | Friday   |

### Open Questions
- Pricing model still to be determined.