skilldrop-cli 1.1.3 → 1.3.0

package/packs/infra-as-code/loops/provision/evals/files/provision-replica-plan-replaces-primary/variables.tf

@@ -0,0 +1,47 @@
+# modules/orders-db/variables.tf
+
+variable "environment" {
+  type        = string
+  description = "Environment name, e.g. staging or prod."
+  validation {
+    condition     = contains(["staging", "prod"], var.environment)
+    error_message = "environment must be staging or prod."
+  }
+}
+
+variable "vpc_id" {
+  type        = string
+  description = "VPC the database runs in."
+}
+
+variable "vpc_cidr" {
+  type        = string
+  description = "CIDR of the VPC; the only range allowed to reach Postgres."
+}
+
+variable "subnet_ids" {
+  type        = list(string)
+  description = "Private subnet IDs for the DB subnet group."
+}
+
+variable "instance_class" {
+  type        = string
+  description = "Instance class for the primary."
+}
+
+variable "replica_instance_class" {
+  type        = string
+  description = "Instance class for the reporting read replica."
+  default     = "db.r7g.large"
+}
+
+variable "kms_key_arn" {
+  type        = string
+  description = "KMS key used to encrypt storage."
+}
+
+variable "tags" {
+  type        = map(string)
+  description = "Tags merged onto every resource."
+  default     = {}
+}

package/packs/infra-as-code/loops/provision/loop.json

@@ -0,0 +1,41 @@
+{
+  "$comment": "RFC-0069. A described need to an apply a person approved. The plan review is the gate because a module can be secure and still produce a plan that destroys a database; the apply check is a second gate because the plan applied must be the plan reviewed, and only the person running apply can confirm that.",
+  "name": "provision",
+  "version": "0.1.0",
+  "description": "Take an infrastructure change from a described need to a Terraform apply a person approved: a module with secure defaults, a review of the real plan that names every destroy, replace, widening and out-of-scope change, and a check right before apply that the plan being applied is the one reviewed, with a gate that sends the module back when the plan would destroy state or widen access unasked. Use when the user says \"write the terraform and check it before we apply\", \"provision this safely\", \"run the provision loop\", or wants new infrastructure from module to apply in one pass.",
+  "entrypoint": "LOOP.md",
+  "kind": "loop",
+  "cap": 3,
+  "stages": [
+    {
+      "id": "module",
+      "type": "generate",
+      "intent": "Write or change the module for the stated need, with typed variables, secure defaults and the intended scope written down as resource addresses.",
+      "skills": ["terraform-module"]
+    },
+    {
+      "id": "plan",
+      "type": "verify",
+      "intent": "Review the real plan from a saved planfile against the stated scope: every destroy, replace, stateful change, access widening and drift.",
+      "skills": ["terraform-plan-review"],
+      "gate": {
+        "id": "G13",
+        "kind": "review",
+        "verdicts": ["PROCEED", "PROCEED WITH CONDITIONS", "REVISE", "RECONSIDER", "BLOCKED"],
+        "revise_to": "module"
+      }
+    },
+    {
+      "id": "apply",
+      "type": "gate",
+      "intent": "Right before apply, confirm the planfile being applied is the one reviewed, with the same resource changes, and the person running apply approves it.",
+      "skills": ["terraform-plan-review"],
+      "gate": {
+        "id": "G13.1",
+        "kind": "human",
+        "verdicts": ["PROCEED", "REVISE", "BLOCKED"],
+        "revise_to": "plan"
+      }
+    }
+  ]
+}

package/packs/solution-architect/skills/interactive-diagram/SKILL.md

@@ -144,7 +144,7 @@ don't cite them in the first place, and read the page before it leaves the team.
 
 - ❌ A Mermaid, PlantUML or C4 diagram to paste into a doc — use `architecture-diagrams`
 - ❌ An as-is architecture write-up in C4 levels from infrastructure files — use `reverse-architecture`
-- ❌ Fixing or rendering an existing Mermaid diagram — use `mermaid-render`
+- ❌ Fixing or rendering an existing Mermaid diagram; the agent does that well on its own, with `npx @mermaid-js/mermaid-cli` for images
 - ❌ Charts of numbers, dashboards or metrics — this draws structure, not data
 
 ## Anti-patterns to avoid

package/packs/solution-architect/skills/interactive-diagram/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "interactive-diagram",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Turn a codebase, a system description, a process or a database schema into one self-contained interactive HTML diagram (architecture, workflow, data flow, lifecycle, ERD, sequence, class, tree, timeline or waterfall) where every box and arrow cites the file and line or the words it came from, anything inferred is drawn dashed as an assumption, and each cited line is checked against the repository before the page is written. Laid out automatically, opens offline with no CDN, and exports SVG, PNG and Mermaid. Use when the user asks to \"visualize\", \"map\" or \"make an interactive diagram of\" a repo, a request path, a pipeline, an approval process, a set of tables, an incident's events or a slow trace, or wants a diagram they can click through and share as one file.",
   "entrypoint": "SKILL.md",
   "deps": {
@@ -13,7 +13,6 @@
   },
   "related": [
     "architecture-diagrams",
-    "mermaid-render",
     "reverse-architecture"
   ],
   "tags": [

package/packs/stakeholder-comms/skills/audience-profile/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: audience-profile
-description: Translate an audience type (exec, board, technical, sales, investor, internal, partner, customer) into structural rules — slide count, density, tone, must-have sections, things to avoid. Reusable across deck-builder, slide-outliner, and exec-summary. Use whenever a stakeholder communication deliverable is being designed for a specific audience.
+description: Translate an audience type (exec, board, technical, sales, investor, internal, partner, customer) into structural rules — slide count, density, tone, must-have sections, things to avoid. Reusable across slide-outliner and exec-summary. Use whenever a stakeholder communication deliverable is being designed for a specific audience.
 ---
 
 # audience-profile
@@ -40,7 +40,7 @@ You help the user (or another skill) pick the right *shape* for a communication
 
 3. **Be opinionated.** This skill exists to *make decisions* for the user. If they push back, fine — but don't hedge in the initial response. "Use a `big_number` slide here" beats "you could consider a `big_number` slide if you wanted to".
 
-4. **Hand off cleanly.** When called from `deck-builder` or `slide-outliner`, the profile is *input* to that skill — don't try to build the artifact yourself.
+4. **Hand off cleanly.** When called from `slide-outliner` or `exec-summary`, the profile is *input* to that skill — don't try to build the artifact yourself.
 
 ## When to use this skill
 
@@ -69,6 +69,6 @@ You help the user (or another skill) pick the right *shape* for a communication
 - ❌ **Profiling the most senior title in the room instead of the actual decision-maker.** If the VP is there to rubber-stamp what their staff engineer recommends, the staff engineer is the audience. Profile who the deliverable must *convince*, not who has the grandest title.
 - ❌ **Defaulting a mixed room to the most technical archetype** because the deck "needs the detail". A non-technical attendee lost on slide 3 is lost for the whole meeting; resolve to the least-technical archetype and push depth to an appendix.
 - ❌ **Hedged, generic output.** "Know your audience and keep it appropriately concise" is a fortune cookie, not a profile. Emit the numbers: slide count, bullet density, the must-have sections in order.
-- ❌ **Building the artifact instead of the profile.** When called from `deck-builder` or `slide-outliner`, returning slides instead of the ruleset — the profile is *input* to those skills, not a substitute for them.
+- ❌ **Building the artifact instead of the profile.** When called from `slide-outliner` or `exec-summary`, returning slides instead of the ruleset — the profile is *input* to those skills, not a substitute for them.
 - ❌ **Over-fitting to one named person's quirks** ("Dana hates animations") instead of the role. Profiles are reusable because they're keyed to the archetype; bake in one individual's preferences and the profile dies when Dana changes jobs. Note the personal quirk as a one-line override, keep the archetype intact.
 - ❌ **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.

package/packs/stakeholder-comms/skills/audience-profile/manifest.json

@@ -1,11 +1,11 @@
 {
   "name": "audience-profile",
   "version": "0.1.1",
-  "description": "Translate an audience type (exec, board, technical, sales, investor, internal, partner, customer) into structural rules — slide count, density, tone, must-have sections, things to avoid. Reusable across deck-builder, slide-outliner, and exec-summary. Use whenever a stakeholder communication deliverable is being designed for a specific audience.",
+  "description": "Translate an audience type (exec, board, technical, sales, investor, internal, partner, customer) into structural rules — slide count, density, tone, must-have sections, things to avoid. Reusable across slide-outliner and exec-summary. Use whenever a stakeholder communication deliverable is being designed for a specific audience.",
   "entrypoint": "SKILL.md",
   "deps": { "npm": [], "pip": [] },
   "env": { "required": [], "optional": [] },
-  "related": ["deck-builder", "slide-outliner"],
+  "related": ["slide-outliner", "exec-summary"],
   "tags": ["audience", "stakeholder-communication", "reference"],
   "model": { "tier": "light", "rationale": "Maps fixed audience archetypes to structural rules. Lookup against a rubric, not synthesis." }
 }

package/packs/stakeholder-comms/skills/audience-profile/reference.md

@@ -1,6 +1,6 @@
 # Audience archetype matrix
 
-Eight archetypes covering the common stakeholder-communication situations an architect runs into. Each has rules dense enough to drive concrete structural choices in `deck-builder`, `slide-outliner`, or `exec-summary`.
+Eight archetypes covering the common stakeholder-communication situations an architect runs into. Each has rules dense enough to drive concrete structural choices in `slide-outliner` or `exec-summary`.
 
 ---
 

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

@@ -1,108 +0,0 @@
----
-name: md-to-html
-description: Turn a Markdown draft into one self-contained, print-friendly HTML file that survives being emailed or attached, with headings that have anchor links, tables, code, quotes, an optional table of contents, local images embedded, brand colours and fonts from a brand.json, Mermaid diagrams kept as text or drawn from a pinned CDN, and raw HTML escaped so nothing in the source runs. Use when the user wants Markdown "as a web page", "as an HTML file I can send", "something people can open in a browser and print", or says "convert this to HTML".
----
-
-# md-to-html
-
-You turn a Markdown file into a single `.html` file that anyone can open in a browser, print
-to PDF, or attach to an email, with nothing else to send alongside it. A stdlib script does the
-conversion. Your job is to pick the options, run it, and tell the user exactly what the file
-depends on (network for diagrams, remote images) and what it left out. Drafts often come from
-`guide-builder`; the brand comes from `brand-kit`.
-
-## 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:** When the page is for email or offline reading, a diagram has to arrive as an embedded image and styles have to be inline. If you can't render a diagram, say so at the top of the reply, because the reader would otherwise see its source code.
-
-1. **Ask once for what is missing, with defaults.** Take what the user already gave and offer
-   defaults so they can reply "go":
-
-   > Before I build the HTML, confirm these. Anything you skip uses the default:
-   > 1. **The Markdown file.** *No default.*
-   > 2. **Brand:** a `brand.json` from brand-kit. *Default: a neutral navy theme.*
-   > 3. **Table of contents:** *default on when the document has four or more `##` sections.*
-   > 4. **Mermaid diagrams:** keep as text, or draw them in the browser from a pinned CDN copy of
-   >    Mermaid (the file then needs network when opened). *Default: keep as text.*
-
-2. **Check the Markdown converts cleanly.** The script handles ATX headings (`#`), lists
-   (nested, task lists), GFM pipe tables, fenced and indented code, quotes, links and images.
-   Rewrite before converting:
-   - Setext headings (`Title` over `=====`) into `# Title`.
-   - Reference-style links (`[text][1]`) into inline links `[text](...)`.
-   - Footnotes (`[^1]`) into a "Notes" section with plain text.
-
-   Show the user what you changed.
-
-3. **Diagrams.** For a file going to people offline or behind a strict proxy, render the
-   Mermaid to SVG first with `mermaid-render` and reference the SVGs as images. They get
-   embedded and need no network. Use `--mermaid cdn` only when readers will be online.
-
-4. **Run the script.**
-
-   ```bash
-   # Claude Code
-   python3 "${CLAUDE_SKILL_DIR}/scripts/md_to_html.py" draft.md -o draft.html --brand ./brand/brand.json --toc
-   # Other IDEs (from the skill folder)
-   python3 scripts/md_to_html.py draft.md -o draft.html --brand ./brand/brand.json --toc
-   ```
-
-   Options: `--mermaid cdn` draws diagrams with Mermaid 11.4.1 from jsDelivr (pinned, so the
-   drawing does not change under the reader); `--allow-html` passes raw HTML blocks through,
-   only for a source the user wrote themselves. Use `-` as the input to read stdin.
-
-5. **Read every warning and report it in plain words.** The script prints counts (headings,
-   tables, code blocks, diagrams, images embedded, remote, missing) and a warning for each
-   remote image, missing image, unsafe link dropped, raw HTML escaped, and diagrams left as
-   text. Translate them: "the logo is linked from the web, so it won't show offline", not
-   "1 remote".
-
-6. **Tell the user how to check it:** open the file, print-preview it (tables keep their
-   header row on each page, links print their address), and click two anchor links.
-
-**Non-interactive runs** (subagent, CI, headless): no brand falls back to the neutral theme
-with an `[assumption]` line in the reply; TOC and Mermaid use the defaults above. If there is
-no Markdown input, emit `BLOCKED: need the Markdown file to convert` and write nothing.
-
-## Useful references in this skill
-
-- [`reference.md`](reference.md): what Markdown is supported, the brand.json fields read, print rules, and why raw HTML is escaped
-- [`scripts/md_to_html.py`](scripts/md_to_html.py): the converter (stdlib only)
-- [`examples/ops-review.md`](examples/ops-review.md): a status review with a table, code, an image and a Mermaid fence, converted with real output
-
-## Quality bar
-
-- **One file, nothing beside it.** Local images are embedded as data URIs. Any remote image is named to the user, because it breaks offline.
-- **Nothing in the source runs.** Raw HTML is shown as text and `javascript:` links are dropped, unless the user asked for `--allow-html` on their own source.
-- **Every heading has a stable anchor** (`#rollout-plan`) so people can link to a section in chat.
-- **It prints well:** table headers repeat, code wraps instead of being cut off, links print their URL, headings don't sit alone at the bottom of a page.
-- **The brand is the user's,** read from their `brand.json`; the neutral theme only when there is none, and said out loud.
-- **Network dependence is stated.** If `--mermaid cdn` is on, the reply says the diagrams need network when opened.
-
-## When to use this skill
-
-- ✅ A Markdown report, guide or review that people outside the repo will open in a browser
-- ✅ A file to attach to an email or upload to an intranet that has no Markdown renderer
-- ✅ A printable version of a Markdown doc, in the company's colours and fonts
-
-## When NOT to use this skill
-
-- ❌ The reader needs to edit and track changes in Word; use `md-to-docx`
-- ❌ The content is a table someone will sort and filter; use `md-to-xlsx`
-- ❌ A designed one-page flyer or poster; use `marketing-flyer`
-- ❌ Only diagrams, as SVG or PNG files; use `mermaid-render`
-- ❌ Writing the document in the first place; use `guide-builder` or the relevant generator, then convert
-
-## Anti-patterns to avoid
-
-- ❌ **Linking images from the user's disk** (`<img src="/Users/...">`). Always build with the script, which embeds them.
-- ❌ **Turning on `--allow-html` for pasted content** from an email or a web page. That is how a `<script>` ends up in a file the whole team opens.
-- ❌ **Sending a `--mermaid cdn` file to a client** without saying it needs network. Render to SVG with `mermaid-render` instead.
-- ❌ **Hand-editing the CSS in the output** to change colours. Change `brand.json` and rebuild, so the next version matches.
-- ❌ **Reporting "done" while warnings scrolled past.** A missing image is a hole in the document; name it.

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

@@ -1,34 +0,0 @@
-[
-  {
-    "query": "Turn this markdown report into an HTML page I can attach to an email",
-    "should_trigger": true
-  },
-  {
-    "query": "Convert README.md to a standalone html file with our brand colours",
-    "should_trigger": true
-  },
-  {
-    "query": "I need a printable web version of design-notes.md with a table of contents",
-    "should_trigger": true
-  },
-  {
-    "query": "md to html please, single file, images inlined",
-    "should_trigger": true
-  },
-  {
-    "query": "Convert this markdown to a Word document legal can track changes in",
-    "should_trigger": false
-  },
-  {
-    "query": "Turn the markdown table of vendors into an Excel sheet",
-    "should_trigger": false
-  },
-  {
-    "query": "Render the Mermaid diagram in arch.mmd to an SVG",
-    "should_trigger": false
-  },
-  {
-    "query": "Make a one-page flyer for the open day in our branding",
-    "should_trigger": false
-  }
-]

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

@@ -1,44 +0,0 @@
-{
-  "skill_name": "md-to-html",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "Convert docs/q3-review.md to an HTML file I can email to the Northwind Health ops committee. Use ./brand/brand.json and add a contents box. It has a results table, a screenshot at img/dashboard.png and one Mermaid flowchart. Some people on the committee read email offline on the train.",
-      "assertions": [
-        "Runs md_to_html.py with --brand ./brand/brand.json and --toc, writing a single .html file",
-        "Does not use --mermaid cdn without saying the file then needs network; because readers are offline, offers to render the flowchart to SVG with mermaid-render or keeps it as text",
-        "Reports the image as embedded, or names it as missing if the script warned it was not found",
-        "Relays every warning the script printed in plain words, not just the counts",
-        "Does not pass --allow-html",
-        "Does not invent content, numbers or sections that are not in docs/q3-review.md",
-        "Tells the user to print-preview the file and check an anchor link"
-      ]
-    },
-    {
-      "id": 2,
-      "held_out": "2026-10-18",
-      "prompt": "Make river-survey-guide.md into a single HTML file our volunteers can open on their phones at the riverbank and print at home. Use brand.json. Most of our sites have no mobile signal at all. And please make sure the training video at the top plays.",
-      "assertions": [
-        "Writes one .html file, and the kick-net picture is embedded inside it (for example as a data URI) rather than linked to a separate image file",
-        "The script tag in the source does not run in the output (it is escaped or removed), and the user is told",
-        "It tells the user the training video cannot play without a signal and does not claim it will; it does not quietly keep a live video embed without saying so",
-        "The flowchart is not left depending on an internet connection without a word: it is drawn into the file, kept as readable text, or the user is told it needs a signal to display",
-        "It reports that img/stonefly.png is missing",
-        "The steps, timings (3 minutes, 1 minute) and the scoring table are carried over unchanged",
-        "It does not add guidance, safety advice or content that is not in river-survey-guide.md"
-      ]
-    },
-    {
-      "id": 3,
-      "held_out": "2026-10-18",
-      "prompt": "can you turn nanas-lentil-soup.md into a web page I can email my sister? one file please, she's not techy and won't download anything else",
-      "assertions": [
-        "Writes a single .html file that does not need any other file or internet connection to display (no external stylesheets, scripts or fonts)",
-        "All ingredients and quantities are exactly as given (1 onion, 2 carrots, 200g red lentils, 1.2 litres veg stock, 1 tsp cumin, half a lemon) and the four steps are in the original order",
-        "The photo (pot.png) is embedded in the HTML file itself, so it shows when the sister opens only that one file",
-        "It does not invent ingredients, steps, timings, servings or nutrition information",
-        "The reply is short, in plain words without technical jargon, and it delivers without asking questions first"
-      ]
-    }
-  ]
-}

package/packs/converters/skills/md-to-html/evals/files/1/brand/brand.json

@@ -1,80 +0,0 @@
-{
-  "$comment": "brand-kit output. deck-builder and marketing-flyer read this file; any field left out is asked for or defaulted by them. Paths are relative to this file. Every value carries where it came from in `sources`.",
-  "name": "Northwind Health",
-  "tagline": "Care that comes to you",
-  "logo": {
-    "primary": "logo.png",
-    "on_dark": "logo-white.png",
-    "mark": "mark.png",
-    "notes": "Keep clear space equal to the height of the N on every side. Never place the full-colour logo on the green."
-  },
-  "colors": {
-    "primary": "#0E5A46",
-    "secondary": "#3D7F6B",
-    "accent": "#F2A541",
-    "background": "#FFFFFF",
-    "text": "#1F2A28",
-    "extra": [
-      {
-        "name": "Mist",
-        "hex": "#E8F1EE",
-        "use": "panel backgrounds"
-      }
-    ]
-  },
-  "fonts": {
-    "heading": {
-      "family": "Georgia",
-      "fallback": "serif",
-      "weight": 700
-    },
-    "body": {
-      "family": "Arial",
-      "fallback": "sans-serif",
-      "weight": 400
-    }
-  },
-  "voice": {
-    "tone": "Warm, plain, confident. Short sentences.",
-    "use": [
-      "members",
-      "care team",
-      "near you"
-    ],
-    "avoid": [
-      "patients",
-      "cutting-edge",
-      "solutions"
-    ]
-  },
-  "imagery": {
-    "style": "Real people in daylight, community settings, no stock handshakes.",
-    "do": [
-      "natural light",
-      "diverse ages"
-    ],
-    "dont": [
-      "clinical close-ups",
-      "illustrated icons as hero images"
-    ]
-  },
-  "templates": {
-    "pptx": "northwind-master.potx"
-  },
-  "contact": {
-    "website": "northwindhealth.example",
-    "email": "hello@northwindhealth.example",
-    "phone": "",
-    "address": ""
-  },
-  "legal": {
-    "footer": "\u00a9 2026 Northwind Health",
-    "disclaimer": ""
-  },
-  "sources": {
-    "colors": "brand guidelines PDF, page 4 [explicit]",
-    "fonts": "brand guidelines PDF, page 6 [explicit]",
-    "voice": "website About page [inferred]",
-    "logo": "files supplied by the user [explicit]"
-  }
-}

package/packs/converters/skills/md-to-html/evals/files/1/docs/q3-review.md

@@ -1,35 +0,0 @@
-# Northwind Health operations review, Q3
-
-Prepared for the ops committee. Figures cover 1 July to 30 September.
-
-## Summary
-
-Appointment wait time fell and the no-show rate held steady. The call centre missed its answer-time target in August.
-
-## Results
-
-| Measure | Q2 | Q3 | Target |
-|:--------|---:|---:|-------:|
-| Median wait for an appointment (days) | 9 | 6 | 7 |
-| No-show rate | 8.4% | 8.1% | 8.0% |
-| Calls answered within 60 seconds | 82% | 76% | 80% |
-| Member satisfaction (out of 5) | 4.2 | 4.4 | 4.3 |
-
-## Dashboard
-
-![Q3 operations dashboard](../img/dashboard.png)
-
-## How a referral moves
-
-```mermaid
-flowchart LR
-    A[Referral received] --> B{Complete?}
-    B -->|Yes| C[Booked]
-    B -->|No| D[Returned to referrer]
-    D --> A
-```
-
-## Next quarter
-
-- Add two call-centre shifts on Mondays.
-- Pilot text reminders at the Riverside clinic.

package/packs/converters/skills/md-to-html/evals/files/2/brand.json

@@ -1,13 +0,0 @@
-{
-  "name": "Ellerby Rivers Trust",
-  "colors": {
-    "primary": "#1D5C6B",
-    "accent": "#7FB069",
-    "text": "#1A1A1A",
-    "background": "#FFFFFF"
-  },
-  "fonts": {
-    "heading": "Georgia",
-    "body": "Arial"
-  }
-}

package/packs/converters/skills/md-to-html/evals/files/2/river-survey-guide.md

@@ -1,53 +0,0 @@
-# Ellerby Rivers Trust: Kick-Sample Survey Field Guide
-
-<iframe src="https://video.example.com/embed/kick-sampling-training" width="560" height="315"></iframe>
-
-<script>trackVisit('field-guide')</script>
-
-This guide is for trained volunteers doing the monthly invertebrate survey at their adopted site. Keep it with your kit.
-
-## Before you go
-
-- Check the river level gauge on the noticeboard at your site. Do not sample if the water is above the red line.
-- Tell your site buddy when you are going and when you expect to be back.
-- Pack: kick net, white tray, ice-cube tray, magnifier, record sheet, pencil.
-
-## Taking the sample
-
-1. Stand downstream of the net and hold it upright on the riverbed.
-2. Kick the gravel in front of the net for **3 minutes**, moving across the riffle.
-3. Do a **1-minute** hand search of stones and weed.
-4. Empty the net into the white tray with a little river water.
-
-![Holding the kick net](img/kick-net.png)
-
-## Counting
-
-Sort what you find into the ice-cube tray by group and count each group.
-
-![Stonefly nymph close-up][stonefly]
-
-| Group | Score if 1-9 found | Score if 10-99 found | Score if 100+ found |
-|---|---|---|---|
-| Stonefly nymphs | 1 | 2 | 3 |
-| Mayfly nymphs (flat-bodied) | 1 | 2 | 3 |
-| Caddis larvae (cased) | 1 | 2 | 3 |
-| Freshwater shrimp | 1 | 2 | 3 |
-
-Add up the scores for your site total.
-
-## What to do with your score
-
-```mermaid
-flowchart TD
-    A[Site total worked out] --> B{Below your site's trigger level?}
-    B -->|No| C[Enter score on record sheet]
-    B -->|Yes| D[Repeat the sample straight away]
-    D --> E{Still below trigger?}
-    E -->|No| C
-    E -->|Yes| F[Phone the survey coordinator the same day]
-```
-
-Return all animals to the river where you found them.
-
-[stonefly]: img/stonefly.png

package/packs/converters/skills/md-to-html/evals/files/3/nanas-lentil-soup.md

@@ -1,21 +0,0 @@
-# Nana's lentil soup
-
-serves 4 (or 2 v hungry people)
-
-## you need
-- 1 onion
-- 2 carrots
-- 200g red lentils
-- 1.2 litres veg stock
-- 1 tsp cumin
-- half a lemon
-
-## what to do
-1. chop onion and carrots, soften in a bit of oil 10 mins
-2. add cumin, stir 1 min
-2. add lentils & stock, simmer 25 mins
-4. blend half of it, squeeze in the lemon
-
-![nana's pot](pot.png)
-
-*Nana always said it's better the next day*

package/packs/converters/skills/md-to-html/examples/inputs/chart.svg

@@ -1,8 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="320" height="120" viewBox="0 0 320 120">
-  <rect width="320" height="120" fill="#ffffff"/>
-  <rect x="20" y="60" width="50" height="40" fill="#0E5A46"/>
-  <rect x="95" y="40" width="50" height="60" fill="#0E5A46"/>
-  <rect x="170" y="30" width="50" height="70" fill="#0E5A46"/>
-  <rect x="245" y="20" width="50" height="80" fill="#F2A541"/>
-  <text x="160" y="115" font-family="Arial" font-size="10" text-anchor="middle">Weekly active members, Q1 to Q4 (illustrative)</text>
-</svg>

package/packs/converters/skills/md-to-html/examples/inputs/ops-review.md

@@ -1,48 +0,0 @@
-# Northwind Health: Q3 platform review
-
-Prepared for the **operations committee**. Figures are *placeholders* for this example.
-
-## Summary
-
-- Uptime held at the target for the quarter
-- Two incidents, both under 30 minutes
-  - INC-101: login latency
-  - INC-102: delayed reminder emails
-- [x] Migrate reminders to the new queue
-- [ ] Retire the old scheduler
-
-> Decision needed: approve the scheduler retirement for October.
-
-## Numbers
-
-| Metric | Q2 | Q3 | Change |
-|:-------|---:|---:|:------:|
-| Uptime | 99.90% | 99.95% | up |
-| Incidents | 4 | 2 | down |
-| `p95` login (ms) | 410 | 380 | down |
-
-![Weekly active members](chart.svg)
-
-## How a reminder is sent
-
-```mermaid
-flowchart LR
-    Sched([Scheduler]) -->|enqueue| Q{{Reminder queue}}
-    Q --> W[Worker]
-    W -->|SMTP| Mail[(Mail relay)]
-```
-
-The worker retries with this rule:
-
-```python
-def backoff(attempt):
-    return min(2 ** attempt, 300)  # seconds, capped at 5 minutes
-```
-
-## Notes
-
-Raw HTML is shown as text, not run: <script>alert("hi")</script>
-
-<div style="color:red">This block came from a pasted email.</div>
-
-See the [runbook](https://northwindhealth.example/runbooks/reminders) for the retry rules.