<!--
Practice example for the "Make a Skill" chapter (Chapter 16). A Skill is a saved,
re-runnable "recipe" you invoke by name instead of re-typing the whole request each
time. This file shows what a plain-English recipe looks like BEFORE it's saved, so you
can recognize the shape and write your own. It uses this pack's sample-data.csv as the
source and example.com addresses only — no real people, no real business, no secrets.

You don't need to memorize any format. The point is: a good recipe names the goal, the
inputs, the steps, the rules, and — crucially here — the safety gate. When you ask Claude
to "turn this routine into a saved recipe," something like this is what you're describing.
-->

# Recipe: Weekly Update Summary

**What it does (goal):**
Read the latest rows of the data file, summarize what changed since last week, and
prepare a short, bulleted update — ready for me to review. It PREPARES only; it never
sends anything on its own.

**Inputs:**
- `sample-data.csv` (the data source for practice; later, a live read-only connection)

**Steps:**
1. Read every row in the data file.
2. Note which rows are new or changed since the last time this ran.
3. Write a short summary: three to six bullets, plain language, most important first.
4. Save the summary as `weekly-update.md` in the `output/` folder.
5. Stop and show me the result. Do not send, post, or share it.

**Rules (the standards only I know):**
- Keep it to one page — if it's longer, tighten it, don't pad it.
- Lead with anything that needs my attention (a stalled item, a due date passing).
- Use plain names, no jargon.
- If a row looks incomplete or odd, flag it rather than guessing.

**Safety gate (required):**
- This recipe is **prepare-only**. It never sends or posts anything.
- If I later want it to deliver the update, that becomes a *prepare-and-send* automation
  with a human gate: it prepares the message, shows me exactly what would go out and
  where, and waits for my approval before anything leaves. Send to myself first.

**How I run it:**
Invoke it by name (for example, ask Claude to run the "weekly update summary" recipe).
The current, exact way to invoke a saved recipe is in the Companion Pack — the naming and
setup can change.

**Done looks like:**
I open `output/weekly-update.md` and see a clear, one-page summary I'd be happy to send
myself — after I've read it.