skilldrop-cli 0.16.34 → 0.16.36

package/packs/converters/skills/md-to-pptx/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: md-to-pptx
+description: Turn an existing Markdown document (a status report, runbook, review or notes) into a PowerPoint deck (.pptx) that opens without a repair prompt, with nothing to install. Each heading becomes a slide, lists keep their nesting, tables become real PowerPoint tables, images are embedded, and comments become speaker notes. A section too long for one slide is split onto "continued" slides instead of shrinking the text, and the reply names every split, everything dropped, and any speaker note that would go out with the file. Use when the user says "turn this markdown into slides", "make this report a PowerPoint", "convert the .md to pptx", "I need this as a deck for Thursday", or "export these notes to PowerPoint".
+---
+
+# md-to-pptx
+
+This skill turns a Markdown document into a `.pptx` mechanically: the headings decide the
+slides and the words stay the user's own. A stdlib Python script writes the PowerPoint file,
+checks it, and prints an outline of the slides. The agent's job is the part around it: get the
+Markdown into a shape that converts well, run the script, read what it reports, and tell the
+user what changed. Designing a persuasive deck is `deck-builder`; planning what slides should
+say is `slide-outliner`.
+
+## How to respond
+
+**Four rules come before the steps and outrank them:**
+
+- **Answer what was asked, first.** Open with the answer, the decision or the artifact, in plain words. Scores, matrices, frameworks and tags come after it, and anything that doesn't change the answer is cut.
+- **Use only what you were given.** Don't add facts, names, numbers, incidents, history, steps or sections the input doesn't contain. What you need and don't have is left out of the artifact and listed once at the end under "To confirm".
+- **Deliver from what you have.** When the request gives you something to work on, state your assumptions in a line and produce the result. When it gives you nothing to work on, ask for it in one or two plain sentences and say what you will do once you have it.
+- **Write for someone who has never heard of this skill.** No skill names, no paths or scripts from this folder, no internal terms, and nothing about how the run was set up. A next step is one plain sentence at the end that describes the work.
+- **For this skill:** Convert, don't redesign. Each `##` section becomes one slide, or more when it splits, in the document's own words. Never add an agenda, summary, "Key takeaways" or "Questions?" slide, and never reword bullets to make them punchier. If the user wants that, the job is designing a deck, not converting one.
+
+1. **Get the Markdown, and nothing else.** A path, or text pasted in the chat. Save pasted text to
+   a `.md` file next to any images it uses. Don't ask about brand or slide size: 16:9 and the
+   built-in look are the defaults, and a `brand.json` (fonts and colours, the same file the Word
+   converter reads, often made with `brand-kit`) is used when the user names one.
+
+2. **Fix a copy so it converts well. Change formatting only, and list each change.**
+   - **Slide headings.** `#` is the title slide, each `##` starts a slide and `###` is a bold line
+     on it. A bold line used as a heading becomes `##`: ✅ `## Risks`, ❌ `**Risks**` (that stays a
+     paragraph, and the slide never starts).
+   - **Speaker notes are `<!-- notes: ... -->`**, the only form the converter reads. A
+     `Notes:` paragraph stays on the slide as text. Convert those paragraphs into comments only
+     when the user said they are speaker notes ("the Notes: bits are what I'll say").
+   - **What doesn't convert:** rewrite an HTML table as a pipe table, fold a footnote's text into
+     its sentence, and render a Mermaid block to PNG with `mermaid-render` (PNG output needs
+     mermaid-cli), then embed it as an image. Remote images are not fetched. Ask for a local copy,
+     or leave the alt text and say so.
+   - **Facts are untouched.** Same numbers, names, dates and order. Don't renumber a list that
+     skips a number. Report it (step 4).
+   - **Check the document against itself** while it's open: a count in a bullet against the rows
+     of its table, a total against its parts. ✅ *"Slide 2 says 9 of 12 depots surveyed; the
+     table on slide 3 marks 10 as Done. Left both as written."* ❌ Quietly changing 9 to 10. A
+     slide deck puts both figures in front of the room at once.
+
+3. **Convert.**
+
+   ```bash
+   # Claude Code
+   python3 "${CLAUDE_SKILL_DIR}/scripts/md_to_pptx.py" report.md -o report.pptx --brand ./brand/brand.json
+   # Other IDEs (from the skill folder)
+   python3 scripts/md_to_pptx.py report.md -o report.pptx --brand ./brand/brand.json
+   ```
+
+   Options: `--aspect 4:3` for older projectors; `--title "..."` replaces the title slide text.
+
+4. **Read every `WARN` line and act on it.** Each names a source line. Fix what is yours to fix
+   (a missing image path, an HTML block) and rerun. Report the rest in plain words. Three need
+   judgment:
+   - **A split** (`did not fit on one slide; split into N slides`) is reported, never hidden.
+     The text stays at full size. When a section runs to three slides or more, say so: it reads
+     as a document page, and the user may want to cut it.
+   - **A numbering jump** (`goes from 7 to 9`): PowerPoint numbers items in order, so "step 9"
+     in the text now points at a different step. Name the missing number and the reference.
+   - **A dropped construct** (footnote, HTML, remote image): say what was lost and where.
+
+5. **Read every speaker note before handing over.** The outline marks slides with `[notes]`.
+   Notes are invisible in the Markdown but travel inside the `.pptx`. Anyone it is emailed to
+   can read them. When a note reads as internal (*"don't raise the penalty clause"*, prices,
+   people, legal), name the slide and quote the note in the reply. Leave the note in place.
+   Deleting it is the user's call.
+
+6. **Check it, and claim only the checks that ran.** The script reopens the file and prints
+   `checked: N XML parts parse, N relationships resolve`. Compare the slide outline it prints
+   with the document's headings. Say it opened in PowerPoint, Keynote or LibreOffice only if it
+   did.
+
+7. **Reply in four lines or fewer:** where the file is and how many slides; what split and where
+   (*"Risks continues on slide 6, from the scanner risk"*); what was dropped, changed or doesn't
+   add up; any note to look at before sending. Example in
+   [`examples/support-weekly.md`](examples/support-weekly.md).
+
+**Non-interactive runs** (subagent, CI, headless): with no Markdown there is nothing to convert.
+Emit `BLOCKED: need the Markdown file or text to convert`, write nothing, and say in a sentence
+what the deck will contain once it arrives. A missing brand or aspect uses the defaults, and
+treating `Notes:` paragraphs as slide text is an `[assumption]` stated at the top.
+
+## Useful references in this skill
+
+- [`reference.md`](reference.md): the full mapping, slide geometry and sizes, how splitting decides, the brand fields read, the package parts written, exit codes
+- [`scripts/md_to_pptx.py`](scripts/md_to_pptx.py): the converter (stdlib only, Python 3.9+)
+- [`examples/support-weekly.md`](examples/support-weekly.md): worked example, a weekly report with a table, a chart, notes and a split section
+
+## Quality bar
+
+- **The slides follow the headings.** The printed outline matches the document's `##` headings one for one, plus "(continued)" slides.
+- **No text below its set size.** Overflow is split onto continued slides, and every split is named in the reply.
+- **Tables are tables.** A pipe table becomes a PowerPoint table the user can edit, not a picture or tab-separated text, and a split table repeats its header row.
+- **Nothing is lost silently.** Every `WARN` is fixed and gone on rerun, or reported in plain words.
+- **Notes were read.** Any note that would embarrass the sender if forwarded is quoted back by slide number.
+- **Facts are untouched.** No number, name, date or list order changed, and no slide added that the document lacks.
+- **Mismatches are named, not fixed.** A count or total the document contradicts is quoted back with both figures.
+- **The file checks out.** The `checked:` line is in the run, and no check is claimed that wasn't run.
+
+## When to use this skill
+
+- ✅ A status report, review or runbook in Markdown that has to be shown as slides
+- ✅ Meeting notes or a design doc someone wants "as a PowerPoint" with its structure intact
+- ✅ A branded version of the same, using the `brand.json` the Word documents use
+
+## When NOT to use this skill
+
+- ❌ Designing a persuasive deck for an audience, with charts, layouts and a narrative; use `deck-builder`
+- ❌ Planning what each slide should say before any document exists; use `slide-outliner`
+- ❌ A Word document to edit and track changes in; use `md-to-docx`
+- ❌ A web page or a file to open in a browser; use `md-to-html`
+- ❌ A `.pptx` back to Markdown; use `file-to-markdown`
+
+## Anti-patterns to avoid
+
+- ❌ **Shrinking text to make a slide fit.** 12 pt bullets are unreadable from the back of the room. Split, and say so.
+- ❌ **Installing python-pptx for a conversion.** The script needs nothing, so the deck builds on a locked-down laptop or in CI.
+- ❌ **"Improving" the deck.** An agenda slide, a "Thank you" slide or punchier bullets put words in the user's mouth they never wrote.
+- ❌ **Handing over notes unread.** A comment written for the presenter ships to every recipient of the file.
+- ❌ **Silently turning `Notes:` paragraphs into speaker notes.** "Notes: figures exclude VAT" is content. Ask, or keep it on the slide.
+- ❌ **Fixing a list that skips a number.** Renumbering hides that a step may be missing. Report it.
+- ❌ **Claiming "opens fine in PowerPoint"** when only the script's own check ran.
+- ❌ **Showing the machinery.** The reply and the artifact are for the person who asked. Don't mention this skill, its files, templates, caps or internal terms, or that the run is non-interactive. Name another skill once, at the end, as a suggested next step, never inside the artifact.
+- ❌ **A bare `BLOCKED` line.** Keep the `BLOCKED: need <X>` line, then write for a person: what is missing in plain words, what you will produce once you have it, and anything the request already lets you say.

package/packs/converters/skills/md-to-pptx/evals/eval_queries.json

@@ -0,0 +1,12 @@
+[
+  { "query": "turn this markdown status report into slides for Thursday", "should_trigger": true },
+  { "query": "Convert runbook.md to a pptx", "should_trigger": true },
+  { "query": "Can you make my meeting notes in notes.md into a PowerPoint? Keep the tables as tables", "should_trigger": true },
+  { "query": "Export docs/q3-review.md as a PowerPoint deck with our brand.json fonts and colours", "should_trigger": true },
+  { "query": "I need this README as slides, nothing fancy, one slide per section", "should_trigger": true },
+  { "query": "Build an investor pitch deck from these bullet points, with charts and our corporate template", "should_trigger": false },
+  { "query": "Outline the slides for my architecture review next week: what should each slide say?", "should_trigger": false },
+  { "query": "Convert this markdown report to a Word document legal can track changes in", "should_trigger": false },
+  { "query": "Turn the .pptx the client sent back into markdown", "should_trigger": false },
+  { "query": "Make the markdown onboarding guide a single HTML page I can email", "should_trigger": false }
+]

package/packs/converters/skills/md-to-pptx/evals/evals.json

@@ -0,0 +1,84 @@
+{
+  "skill_name": "md-to-pptx",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "turn status-report.md into slides for Thursday's steering group, I'll present it and then email the deck round afterwards",
+      "files": [
+        "evals/files/1/status-report.md",
+        "evals/files/1/img/defect-burndown.png"
+      ],
+      "assertions": [
+        "Writes a .pptx whose slides follow the document's sections in order (title, Summary, Milestones, Defect burn-down, Risks and issues, Decisions needed, Next two weeks) and says it was checked by reopening the file, without claiming checks that were not run",
+        "The long Risks and issues section continues on a 'Risks and issues (continued)' slide at full text size instead of shrinking, and the reply says so",
+        "The milestones are a real PowerPoint table with all five rows, and the owners, dates and statuses exactly as in the file",
+        "The defect burn-down chart is embedded on its slide",
+        "The two notes comments become speaker notes on their slides (Summary, and the Risks slides) rather than slide text",
+        "It warns that the speaker note on the Risks slides mentions the Pellow Freight penalty clause and legal review, and that this note goes out to everyone the deck is emailed to, without deleting the note itself",
+        "It does not invent content: no agenda, summary, 'Next steps' or 'Questions?' slide, and no dates, owners or figures that are not in status-report.md",
+        "The reply opens with the file and slide count, is a few lines long, and does not mention scripts, skill names or file paths from the skill"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "can you make this into a powerpoint for the steering committee tomorrow? the Notes: bits under each section are what I'll say, they shouldn't be on the slides\n\n# Depot Wi-Fi refresh\n\n## Where we are\n\n- 9 of 12 depots surveyed\n- Installs start 3 Nov at Selby\n- Spend so far £84,200 of £150,000\n\nNotes: the unsurveyed sites are all waiting on landlord access.\n\n## Survey results\n\n| Depot | Access points | Survey |\n|---|--:|---|\n| Selby | 18 | Done |\n| York | 22 | Done |\n| Hull | 31 | Done |\n| Goole | 12 | Done |\n| Doncaster | 26 | Done |\n| Wakefield | 24 | Done |\n| Leeds | 29 | Done |\n| Bradford | 20 | Done |\n| Harrogate | 14 | Done |\n| Scunthorpe | 16 | Done |\n| Grimsby | - | Booked 6 Nov |\n| Barnsley | - | Booked 10 Nov |\n\nNotes: Hull needs the most because of the mezzanine.\n\n![Coverage heatmap](https://files.example.com/wifi/heatmap.png)\n\n## Ask\n\n1. Approve the install order above\n2. Approve a £12,000 contingency\n\nNotes: if they push back on contingency, say it's 8% of budget.",
+      "assertions": [
+        "Saves the pasted text to a Markdown file and produces a .pptx with a title slide and one slide each for Where we are, Survey results and Ask (plus any continued slide)",
+        "The three Notes: paragraphs end up as speaker notes on their own slides and do not appear as slide text",
+        "Survey results is a real PowerPoint table with all twelve depots, the access point numbers right-aligned, and every value as written",
+        "Says the coverage heatmap is a web link that was not embedded, and asks for a local copy or says what appears in its place",
+        "Points out that '9 of 12 depots surveyed' does not match the table, which shows 10 depots as Done, and does not change either figure",
+        "It does not invent content: no agenda, summary or 'Questions?' slide, and no numbers, dates or sites that are not in the pasted text",
+        "Delivers the file without asking questions first, in a short reply in plain words"
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Convert night-shift-induction.md into a 4:3 PowerPoint using brand.json, it's going on the induction room projector and new starters get a copy of the file afterwards.",
+      "files": [
+        "evals/files/3/night-shift-induction.md",
+        "evals/files/3/brand.json"
+      ],
+      "assertions": [
+        "Writes a 4:3 .pptx with the headings in Georgia and body text in Arial from brand.json",
+        "Reports that the accent colour '#F2A5' in brand.json is not a valid colour and that a default was used, rather than silently applying or replacing it",
+        "Points out that the start-of-shift checks jump from 7 to 9 in the source, so the slides number them in sequence and 'go back to step 9' now points at a different check; it does not invent a step 8 or quietly renumber the reference",
+        "The thirteen checks continue on a '(continued)' slide with the numbering carrying on, at full text size, and the reply says the section was split",
+        "Deals with the Mermaid flowchart: renders it to an image and embeds it, or says plainly that it appears as code text",
+        "The footnote 'Near misses count as incidents' is folded into the text rather than dropped silently, and the retired paper-form HTML block is either rewritten as text or reported as dropped",
+        "It does not add steps, times, sites or slides that are not in night-shift-induction.md",
+        "The reply is short, leads with the file, and does not mention scripts, skill names or the skill's file paths"
+      ]
+    },
+    {
+      "id": 4,
+      "held_out": "2026-10-20",
+      "prompt": "Can you turn qbr-q3.md into a PowerPoint for the Harlow Freight review on Thursday? I'm emailing the deck to their ops team tomorrow so they can read it beforehand.",
+      "assertions": [
+        "Produces a .pptx file in the working directory built from qbr-q3.md",
+        "Does not quietly ship the HTML comment's internal note (7% renewal floor, 11% margin, 'Dana to confirm') to the client: either the .pptx has no speaker note or slide text containing it, or the reply names that note as going out with the file and says to remove it before emailing Harlow",
+        "The reply says the 12-item 'Risks and mitigations' section was split across more than one slide (continued slides) rather than squeezed onto one",
+        "The reply says charts/cost-per-shipment.png is missing from the folder and was not embedded, naming that file",
+        "The .pptx embeds charts/ontime.png as an image (a media file present in the package)",
+        "The .pptx contains the lane table as a real table with all 9 lanes, Columbus to Atlanta through Cincinnati to Memphis, and their figures as in the source (e.g. Toledo to Milwaukee 91.7)",
+        "Invents nothing that is not in qbr-q3.md: no extra lanes, figures, risks, owners, dates or slides of made-up content",
+        "Answers the request directly: hands over the deck with a short reply naming the file and the things the sender must know before emailing it, not a long tutorial on how to build slides"
+      ]
+    },
+    {
+      "id": 5,
+      "held_out": "2026-10-20",
+      "prompt": "can u make these into 5 slides for my boss, she just wants the gist before friday. notes are in vendor-sync-notes.md. nothing fancy",
+      "assertions": [
+        "Produces a .pptx file in the working directory",
+        "The .pptx has 5 slides (or 6 where the reply says the extra one is a title slide), with topic titles the agent chose because the notes have no headings, rather than one slide per paragraph or a single wall of text",
+        "Uses the current figures from the 20 Oct meeting: go-live 1 December and budget $52,000; the superseded $48,000 / 17 November from the pasted 13 Oct section are not presented as current, and the reply says that pasted section was left out (or flags it)",
+        "Leaves Marco's private aside (his dad's surgery) out of every slide and speaker note in the .pptx, and the reply says it was left out or flags it",
+        "Keeps the action items with their owners and dates as written: Sanna demo by 13 Nov, Dev archive rule with legal by 30 Oct, Ruth training rooms week of 23 Nov",
+        "Presents the undecided points as open, not as decisions: the 6-versus-12-month read-only question and the archive-older-than-2-years idea",
+        "Invents nothing that is not in vendor-sync-notes.md: no new numbers, people, dates, risks or recommendations",
+        "Answers the request directly with a short reply naming the file and slide count, suited to a casual 'nothing fancy' ask"
+      ]
+    }
+  ]
+}

package/packs/converters/skills/md-to-pptx/evals/files/1/status-report.md

@@ -0,0 +1,75 @@
+---
+title: Atlas WMS migration — week 42 status
+author: Priya Nair, Programme Lead
+date: 22 October 2026
+---
+
+# Atlas WMS migration: week 42 status
+
+## Summary
+
+- Overall status: **Amber** (Green in week 40)
+- Leeds go-live moves from 9 Nov to 23 Nov
+- Budget: £412k spent of £640k (64%)
+- Two of five integration streams complete
+
+<!-- notes: Open with the date change; the steering group will ask about it first. -->
+
+## Milestones
+
+| Milestone | Owner | Planned | Forecast | Status |
+|---|---|---|---|---|
+| Data migration dry run 1 | Tomasz | 15 Sep | 15 Sep | Done |
+| Carrier API integration | Lena | 1 Oct | 8 Oct | Done |
+| Data migration dry run 2 | Tomasz | 20 Oct | 27 Oct | Late |
+| User acceptance testing | Aisha | 27 Oct | 10 Nov | At risk |
+| Leeds go-live | Priya | 9 Nov | 23 Nov | At risk |
+
+## Defect burn-down
+
+![Open defects by week, weeks 36 to 42](img/defect-burndown.png)
+
+Open defects fell from 148 to 61 over seven weeks. 9 of the 61 are severity 1.
+
+## Risks and issues
+
+### Risks
+
+- **Dry run 2 slips again.** The source extract from the legacy system still times out on the
+  pallet history table, which holds eleven years of movements.
+  - Mitigation: archive movements older than three years before the extract
+  - Owner: Tomasz, decision needed by 24 Oct
+- **UAT testers not released.** Leeds shift managers are needed for five days and peak season
+  starts on 16 Nov.
+  - Mitigation: split UAT into two blocks of two and a half days
+  - Owner: Aisha
+- **Carrier label format change.** One carrier changes its label layout on 1 Nov, which the
+  integration built in October does not support yet.
+  - Mitigation: Lena has the new specification; estimate is three days of work
+- **Handheld scanner firmware.** 40 of the 120 handhelds at Leeds run firmware older than the
+  minimum the new WMS supports.
+  - Mitigation: firmware update in the week of 2 Nov, outside picking hours
+
+### Issues
+
+- **Severity 1 defects.** 9 open, 6 of them in replenishment rules; fixes are due in the
+  build of 29 Oct.
+- **Training rooms.** The Leeds training room is booked for audits in the week of 9 Nov, so
+  training moves to the Wakefield site.
+- **Test data.** UAT needs a masked copy of production data, and the masking job has not been
+  approved by the data protection officer yet.
+
+<!-- notes: Don't raise the Pellow Freight penalty clause (£35k if go-live slips past 30 Nov) unless they ask; legal is still reviewing it. -->
+
+## Decisions needed
+
+1. Approve archiving pallet movements older than three years before dry run 2
+2. Approve the new Leeds go-live date of 23 Nov
+3. Release four Leeds shift managers for UAT in two blocks
+
+## Next two weeks
+
+- Dry run 2 on 27 Oct, with the archive in place
+- Replenishment fixes in the 29 Oct build
+- Scanner firmware update in the week of 2 Nov
+- Full plan and RAID log: [programme site](https://atlas.harbourline.example/programme)

package/packs/converters/skills/md-to-pptx/evals/files/3/brand.json

@@ -0,0 +1,12 @@
+{
+  "name": "Harbourline Logistics",
+  "colors": {
+    "primary": "#1D4E89",
+    "accent": "#F2A5",
+    "text": "#1F1F1F"
+  },
+  "fonts": {
+    "heading": "Georgia",
+    "body": { "family": "Arial" }
+  }
+}

package/packs/converters/skills/md-to-pptx/evals/files/3/night-shift-induction.md

@@ -0,0 +1,53 @@
+# Night shift induction: Wakefield cross-dock
+
+Ops team, version 3. Read before your first shift.
+
+# Before your first shift
+
+- Collect your badge from security at Gate 2
+- Book the forklift refresher if your licence is over 12 months old
+  - Counterbalance and reach trucks only
+    - Reach trucks: the refresher includes the 9 m racking test
+      - Bring your old licence card to the test
+- Read the [incident reporting section](#reporting-an-incident) before you start
+
+# Start-of-shift checks
+
+The checks take about 25 minutes. Do them in this order.
+
+1. Sign in on the shift board in the transport office
+2. Pick up a handheld scanner from the charging rack
+3. Log in to the scanner with your badge number
+4. Check the scanner battery is above 80%
+5. Walk the dock doors 1 to 14 and check each leveller is down
+6. Check the fire exits on the east wall are clear
+7. Read the handover notes from the late shift
+9. Check the trailer schedule for the first three arrivals
+10. Confirm the yard shunter has the same schedule
+11. Test the dock door 7 sensor (it fails most often)
+12. Check the chilled bay reads 2 to 5 °C
+13. Report any fault to the shift lead before 22:30
+
+If the scanner fails at check 3, go back to step 9 and tell the shift lead.
+
+```mermaid
+flowchart LR
+  A[Sign in] --> B[Scanner] --> C[Dock walk] --> D[Handover notes]
+```
+
+# Reporting an incident
+
+Report every incident within the shift, even with no injury.[^1]
+
+<details>
+<summary>Old paper form</summary>
+Form OPS-7 is retired; do not use it.
+</details>
+
+The scanner command to open an incident is:
+
+```text
+MENU > 7 > INCIDENT > NEW
+```
+
+[^1]: Near misses count as incidents.

package/packs/converters/skills/md-to-pptx/evals/files/4/qbr-q3.md

@@ -0,0 +1,85 @@
+# Harlow Freight: Q3 2026 Business Review
+
+Prepared by Northwind Logistics Services for Harlow Freight, 22 October 2026
+
+## Summary
+
+- On-time delivery for the quarter was **94.2%** against a 95% target
+- Shipments handled: 18,430 (up 6% on Q2)
+- Damage claims fell from 41 to 27
+- Two lanes are well below target and have recovery plans (see Risks)
+
+## Delivery performance by lane
+
+![On-time delivery by month, Jul to Sep 2026](charts/ontime.png)
+
+| Lane | Shipments | On-time % | Target % |
+|---|---:|---:|---:|
+| Columbus to Atlanta | 3,120 | 96.8 | 95 |
+| Columbus to Chicago | 2,870 | 95.4 | 95 |
+| Dayton to Nashville | 1,940 | 93.1 | 95 |
+| Dayton to Pittsburgh | 1,610 | 95.9 | 95 |
+| Toledo to Detroit | 2,250 | 97.2 | 95 |
+| Toledo to Milwaukee | 1,480 | 91.7 | 95 |
+| Akron to Buffalo | 1,330 | 95.0 | 95 |
+| Akron to Charlotte | 2,060 | 94.6 | 95 |
+| Cincinnati to Memphis | 1,770 | 92.8 | 95 |
+
+## Cost per shipment
+
+![Cost per shipment, Q1 to Q3 2026](charts/cost-per-shipment.png)
+
+Average cost per shipment was $212 in Q3, down from $219 in Q2, mainly from consolidating the Akron loads.
+
+## Risks and mitigations
+
+1. **Toledo to Milwaukee on-time at 91.7%**
+   - Owner: Priya Raman (Northwind)
+   - Cause: driver shortage on the Thursday wave
+   - Mitigation: second carrier contracted from 1 November
+2. **Cincinnati to Memphis dock congestion**
+   - Owner: Owen Castell (Harlow)
+   - Cause: shared dock doors with inbound returns
+   - Mitigation: move returns to doors 9 to 12 after 2 pm
+3. **Dayton to Nashville weather exposure in Q4**
+   - Owner: Priya Raman (Northwind)
+   - Mitigation: pre-agreed reroute through Louisville
+4. **Peak season volume (+22% forecast for November)**
+   - Owner: Jonah Wilde (Northwind)
+   - Mitigation: 14 additional trailers on short-term lease
+   - Mitigation: weekend dispatch cover from 8 November
+5. **Fuel surcharge volatility**
+   - Owner: Mei Takahashi (Harlow)
+   - Mitigation: monthly surcharge review instead of quarterly
+6. **Telematics vendor contract ends 31 December**
+   - Owner: Jonah Wilde (Northwind)
+   - Mitigation: renewal or replacement decision by 15 November
+7. **Akron to Charlotte just below target (94.6%)**
+   - Owner: Priya Raman (Northwind)
+   - Mitigation: earlier cut-off for Friday pickups
+8. **Proof-of-delivery photo gaps**
+   - Owner: Owen Castell (Harlow)
+   - Cause: older handheld scanners at two depots
+   - Mitigation: scanner swap at Dayton and Akron in November
+9. **Claims process takes 19 days on average**
+   - Owner: Mei Takahashi (Harlow)
+   - Mitigation: target 10 days with a shared claims inbox
+10. **Single point of contact for after-hours escalations**
+    - Owner: Jonah Wilde (Northwind)
+    - Mitigation: rota of three named duty managers from December
+11. **Yard capacity at Columbus during peak**
+    - Owner: Owen Castell (Harlow)
+    - Mitigation: overflow yard at Grove Road, 40 spaces
+12. **Data feed delays into Harlow's planning system**
+    - Owner: Priya Raman (Northwind)
+    - Cause: nightly batch finishes after 6 am
+    - Mitigation: move batch start to 1 am
+
+<!-- INTERNAL, do not share with Harlow: our renewal floor is a 7% discount and margin on this account is 11%. Dana to confirm the number before Thursday. -->
+
+## Next quarter priorities
+
+- Bring Toledo to Milwaukee and Cincinnati to Memphis back above 95%
+- Land the peak plan without missed collections
+- Cut average claims time from 19 days to 10
+- Agree the 2027 contract renewal

package/packs/converters/skills/md-to-pptx/evals/files/5/vendor-sync-notes.md

@@ -0,0 +1,28 @@
+vendor sync, help desk move to Tessellate, tues 20 oct
+
+present: me, Ruth Okafor, Marco Belli, Sanna Lind (Tessellate), Dev Patel (IT)
+
+overall we are still on track but go-live moved. Tessellate can't finish the phone integration in time so go-live is now 1 December (was 17 Nov). Ruth ok with it as long as we don't overlap with the year-end freeze starting 14 Dec.
+
+budget went up to $52,000 total because of the extra integration work. Ruth approved it in the meeting, no need to go back to finance since it's under the $60k sign-off limit.
+
+ticket migration - Sanna says the test run moved 4,800 of 5,000 open tickets cleanly, the other 200 have attachments over 25 MB and need a manual pass. Dev thinks we can just archive anything older than 2 years instead of migrating it, nobody objected but not formally decided
+
+training
+- agents get 2 x 90 min sessions, week of 23 Nov
+- Sanna will send the recording + quick ref card
+- team leads get an extra admin session
+
+(Marco out next week - his dad's surgery, keep that between us. Ruth covering his bits)
+
+open question: do we keep the old system read-only for 6 months or 12? Ruth wants 12, Dev says licence cost makes 6 more realistic. nobody decided, comes back next sync
+
+actions
+- Sanna: fix phone integration, demo by 13 Nov
+- Dev: confirm archive rule for >2yr tickets with legal by 30 Oct
+- Ruth: book training rooms for week of 23 Nov
+- me: send these notes round + update the project plan
+
+---- pasted from last week's sync (13 oct), already covered ----
+
+go-live 17 November, budget $48,000, Tessellate confident on phone integration. training TBC. Marco to draft comms email to agents.

package/packs/converters/skills/md-to-pptx/examples/support-weekly-input.md

@@ -0,0 +1,48 @@
+---
+title: Kestrel Support weekly review
+date: Week 41
+---
+
+# Kestrel Support: weekly review
+
+## This week
+
+- 1,006 tickets opened, 1,041 closed
+- Median first response: 2.8 hours (target 4)
+- Backlog down to 233 from 268
+- Chat hand-off rule live for the billing queue
+
+Notes: lead with the backlog, it's the number the ops director watches.
+
+## Tickets by week
+
+![Tickets opened per week, weeks 37 to 41](tickets-by-week.png)
+
+## Queue health
+
+| Queue | Open | Oldest (days) | Owner |
+|---|--:|--:|---|
+| Billing | 61 | 9 | Ruth |
+| Accounts | 48 | 6 | Dev |
+| Integrations | 72 | 14 | Ana |
+| Hardware returns | 52 | 11 | Sam |
+
+## Follow-ups
+
+### Carried over
+
+- Weekend rota for November still not agreed; Ruth to bring two options to the next review
+  - Option A keeps the current four-person rota and adds an on-call fifth person for peaks
+  - Option B moves to two-person weekend shifts with a Monday catch-up block
+- The integrations backlog has grown three weeks in a row; Ana asked for one more engineer
+  from the platform team for two sprints
+- Hardware returns are waiting on the courier contract renewal, which procurement owns
+
+### New
+
+- Customer survey goes out on 3 November to everyone with a ticket closed in October
+- The billing macro library needs a review before the price change on 1 December
+- Two new starters join on 10 November and need shadowing slots on every queue
+- Knowledge base articles for the new export feature are still in draft, owner to be agreed
+
+<!-- notes: Ana's request for an engineer is not approved yet; don't promise it in the room. -->

package/packs/converters/skills/md-to-pptx/examples/support-weekly.md

@@ -0,0 +1,75 @@
+# Worked example: a weekly support review becomes a six-slide deck
+
+## Input given to the skill
+
+> Can you turn support-weekly-input.md into slides? I'm presenting it at the ops review on
+> Thursday. The Notes: line is what I'll say, not slide text.
+
+The source is [`support-weekly-input.md`](support-weekly-input.md), with its chart
+[`tickets-by-week.png`](tickets-by-week.png) next to it. It has front matter, four `##`
+sections, a right-aligned table, an image, a `Notes:` paragraph, a long "Follow-ups" section
+with two `###` groups and nested bullets, and an HTML notes comment at the end.
+
+---
+
+## What the agent did
+
+**First run, to see what doesn't convert:**
+
+```
+$ python3 scripts/md_to_pptx.py support-weekly-input.md -o support-weekly.pptx
+WARN line 1: YAML front matter dropped (lines 1-4); used on the title slide: title, date
+WARN line 15: paragraph starting "Notes:" stays on the slide as text; wrap it in <!-- notes: ... --> to make it speaker notes
+WARN line 30: "Follow-ups" did not fit on one slide; split into 2 slides (5-6) at a text boundary, text kept at full size
+wrote support-weekly.pptx (6 slides, 1 of them continued, 1 table, 1 image, speaker notes on 1; 16:9; brand: no)
+```
+
+**Fixed the source in a copy.** The user said the `Notes:` line is what they'll say, so it
+becomes a notes comment. Nothing else changed:
+
+```diff
+- Notes: lead with the backlog, it's the number the ops director watches.
++ <!-- notes: lead with the backlog, it's the number the ops director watches. -->
+```
+
+**Second run:**
+
+```
+$ python3 scripts/md_to_pptx.py support-weekly-fixed.md -o support-weekly.pptx
+WARN line 1: YAML front matter dropped (lines 1-4); used on the title slide: title, date
+WARN line 30: "Follow-ups" did not fit on one slide; split into 2 slides (5-6) at a text boundary, text kept at full size
+wrote support-weekly.pptx (6 slides, 1 of them continued, 1 table, 1 image, speaker notes on 2; 16:9; brand: no)
+  checked: 35 XML parts parse, 34 relationships resolve, every part has a content type
+   1. Kestrel Support: weekly review [title]
+   2. This week [notes]
+   3. Tickets by week [image]
+   4. Queue health [table]
+   5. Follow-ups
+   6. Follow-ups (continued) [notes]
+2 warning(s): the items above were dropped, split or changed; tell the user before sharing
+```
+
+The outline matches the four `##` headings, plus one continued slide. The front matter warning
+is expected: its title and date are on the title slide. The split kept the text at 20 pt. The
+"Carried over" group and the first two "New" items are on slide 5, and the last two items are
+on slide 6.
+
+**Read both notes.** Slide 2's note is presenter guidance. Slide 6's note says *"Ana's request
+for an engineer is not approved yet; don't promise it in the room."* That is fine to present
+from, but anyone the file is forwarded to can read it.
+
+**Checked it opens.** Microsoft PowerPoint for Mac 16.114 (2026-10-20) opened the file with no
+repair prompt and counted six slides. A Quick Look thumbnail of each slide showed the table
+with a shaded header and right-aligned numbers, and the chart centred under its title.
+
+---
+
+## Reply to the user
+
+> Here's the deck: `support-weekly.pptx`, 6 slides (title, then This week, Tickets by week,
+> Queue health, and Follow-ups over two slides). Follow-ups was too long for one slide, so it
+> continues on slide 6 at full text size rather than shrinking.
+>
+> Your "Notes:" line is now the speaker note on slide 2. **Before you send the file to anyone:**
+> slide 6's speaker note says Ana's engineer request isn't approved and not to promise it. It
+> travels with the deck, so delete it from the notes pane if the deck goes beyond the room.