skilldrop-cli 0.16.12 → 0.16.14

package/packs/dev-team/skills/contribution-wizard/SKILL.md

@@ -1,142 +0,0 @@
----
-name: contribution-wizard
-description: Guides an author through creating a new skilldrop skill from scratch — generates the manifest, SKILL.md, eval cases, and skill-catalogue entry from a plain-language description of the skill's purpose. Use when authoring a new skill for this repo or a private fork, ensuring a new skill meets the schema and validation requirements before submission.
----
-
-# contribution-wizard
-
-Walks an author through the full arc of creating a new skilldrop skill: intake → manifest + SKILL.md + evals + skill-catalogue entry. The output is copy-paste-ready — the author drops the files into `packs/<pack>/skills/<name>/` and runs `python3 validate.py` to confirm before opening a PR.
-
-## 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:** Read the target repository first: its contributing guide, its agent instructions and two existing skills. Follow the conventions you find, and produce every file that repository requires for a submission, not a generic skill.
-
-### Step 1 — Intake (ask all at once)
-
-Ask these questions in a single block — not one at a time:
-
-> **New skill intake**
->
-> 1. **Purpose**: what does this skill do in one sentence?
-> 2. **Input**: what does the agent receive? (paste, file, structured data, conversational context)
-> 3. **Output**: what does the agent produce? (artifact type, format, length)
-> 4. **Pack**: which role pack does it belong to? (solution-architect / product-manager / dev-team / sre-oncall / stakeholder-comms / ai-engineering / api-builder / new pack)
-> 5. **Is it a gate?** Does it emit a pass/fail verdict, or generate an artifact?
-> 6. **Related skills**: which existing skills does it complement or hand off to?
-> 7. **External deps**: does it need API keys, npm packages, or pip libraries?
-
-### Step 2 — Generate all artifacts in one response
-
-After intake, produce the following in a single response, each in its own fenced code block:
-
-#### `manifest.json`
-
-```json
-{
-  "name": "<kebab-case-name>",
-  "version": "1.0.0",
-  "description": "<use-case-first description — what it does, then trigger phrases>",
-  "entrypoint": "SKILL.md",
-  "deps": { "npm": [], "pip": [] },
-  "env": { "required": [], "optional": [] },
-  "related": ["<related-skill-1>", "<related-skill-2>"],
-  "tags": ["<tag1>", "<tag2>"],
-  "model": {
-    "tier": "<light|standard|heavy>",
-    "rationale": "<one sentence: why this tier fits what the skill does>"
-  }
-}
-```
-
-If the skill ships `scripts/`, add a `permissions` block before `model`: the hosts the scripts contact, the external programs they run, and where they write (`"none"`, `"named-paths"`, `"project"` or `"anywhere"`). For example: `"permissions": { "network": [], "commands": ["pdftotext"], "files": "named-paths" }`. Validation fails a script skill without it, and fails one whose code does something it doesn't declare.
-
-Tier guidance:
-- **light**: pattern matching, formatting, extraction with no judgment calls
-- **standard**: synthesis, judgment calls, structured output requiring reasoning (most skills)
-- **heavy**: multi-step reasoning with high stakes or adversarial review (gates, threat models)
-
-#### `SKILL.md`
-
-```markdown
----
-name: <skill-name>
-description: <same as manifest description>
----
-
-# <skill-name>
-
-<One paragraph: what this skill does and why it's useful. Name the problem it solves.>
-
-## How to respond
-
-<Numbered steps. Each step is an observable action. No vague "reason about X" steps.>
-
-## Quality bar
-
-<Three to five bullet points: what a good output includes and what it never does. Name anti-patterns explicitly.>
-```
-
-#### `evals/cases.json`
-
-Eight eval cases covering: 2 happy-path, 2 minimal/edge input, 2 anti-pattern (the quality bar failures), 2 refusal or boundary cases. Format:
-
-```json
-[
-  {
-    "id": "happy-path-standard",
-    "trigger": "<realistic input>",
-    "expected_shape": ["<checkable criterion 1>", "<checkable criterion 2>"],
-    "must_not_include": ["<anti-pattern from quality bar>"],
-    "verdict_class": "pass",
-    "notes": "<one sentence on what this tests>"
-  }
-]
-```
-
-#### Skill catalogue entry
-
-One row for `guides/reference/skill-catalogue.md`, under the right category, matching the format of existing rows:
-
-```
-| [`<skill-name>`](../../packs/<pack>/skills/<skill-name>/SKILL.md) | <One sentence describing what the skill does and the output it produces.> |
-```
-
-#### Pack and outcome
-
-State which one pack the skill belongs in (`core` only if every role needs it) — its folder goes at `packs/<pack>/skills/<skill-name>/` — and which `outcomes` entry in `catalogue.json` to add it to.
-
-### Step 3 — Install check reminder
-
-After generating, tell the author:
-
-```
-Next steps:
-1. mkdir -p packs/<pack>/skills/<skill-name> && cd packs/<pack>/skills/<skill-name>
-2. Drop in manifest.json, SKILL.md, and evals/cases.json
-3. python3 validate.py    # must pass before opening a PR
-4. Add the row to guides/reference/skill-catalogue.md under the correct category
-5. Add the skill to an outcome in catalogue.json
-6. If the skill has a how-to guide, add it to guides/how-to/ and guides/README.md
-```
-
-## Anti-patterns
-
-- **Generating manifests without checking the schema.** The most common contribution failure is a manifest missing a required field. Always instruct the author to run `python3 validate.py` before opening a PR.
-- **Generating eval triggers that test nothing.** "Run this skill" is not an eval case. Insist on realistic triggers that would expose a specific failure mode if the model got it wrong.
-- **Listing related skills that don't exist.** A manifest that references a non-existent skill fails validation. Instruct the author to run `ls skills/` before finalizing the `related` array.
-
-After generating eval cases, the author can use `eval-harness-generator` to add more coverage or to regenerate cases after modifying the SKILL.md.
-
-## Quality bar
-
-- **Manifests must be schema-valid.** Every field required by `contracts/skill.schema.json` must be present. Use `python3 validate.py` as the check — not a visual review.
-- **Eval triggers are realistic.** A trigger of "use this skill" is not an eval case. Each trigger should be a plausible user input, not a test harness artifact.
-- **SKILL.md has observable steps.** Every step in "How to respond" must describe an action the agent takes — never "think about X" or "consider Y".
-- **The quality bar names anti-patterns.** A quality bar that only says what good looks like doesn't help the agent avoid common failures. Name at least two things the output must never do.
-- **Related skills are real.** Every skill listed in `related` must exist in the skills directory. Run `ls skills/` to check before outputting.

package/packs/dev-team/skills/contribution-wizard/evals/eval_queries.json

@@ -1,30 +0,0 @@
-[
-  {
-    "query": "Help me create a new skilldrop skill from scratch",
-    "should_trigger": true
-  },
-  {
-    "query": "Generate the manifest, SKILL.md, and evals for a skill I want to contribute",
-    "should_trigger": true
-  },
-  {
-    "query": "I have an idea for a skill in the dev-team pack — walk me through authoring it",
-    "should_trigger": true
-  },
-  {
-    "query": "Scaffold a new skill for our private fork so it passes validate.py",
-    "should_trigger": true
-  },
-  {
-    "query": "I edited the bug-triage SKILL.md — regenerate its eval cases",
-    "should_trigger": false
-  },
-  {
-    "query": "Add more eval coverage to an existing skill's evals folder",
-    "should_trigger": false
-  },
-  {
-    "query": "Generate an AGENTS.md for this repository",
-    "should_trigger": false
-  }
-]

package/packs/dev-team/skills/contribution-wizard/evals/evals.json

@@ -1,78 +0,0 @@
-{
-  "skill_name": "contribution-wizard",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I want to add a new skill to skilldrop called `sla-credit-calculator`. It takes a customer contract's SLA terms plus a month of uptime data and outputs the service credit owed, with the calculation shown. It belongs in the sre-oncall pack, it generates an artifact (not a gate), it relates to runbook-generator and incident-comms, and it needs no external deps. Generate everything I need to submit it.",
-      "assertions": [
-        "Produces manifest.json, SKILL.md, evals/cases.json, and a skill-catalogue row, each in its own fenced code block, in a single response",
-        "The manifest includes every required field (name, version, description, entrypoint, deps, env, related, tags, model with tier and rationale)",
-        "The related array lists only skills that exist (runbook-generator, incident-comms) and tells the author to check the skills directory before finalizing",
-        "SKILL.md's How to respond steps are observable actions — none read 'think about X' or 'consider Y'",
-        "The quality bar names at least two things the output must never do (e.g. never invent uptime figures not in the input)",
-        "evals/cases.json has eight cases with realistic triggers, covering happy-path, edge, anti-pattern, and boundary cases",
-        "Ends with next steps that place files under packs/sre-oncall/skills/sla-credit-calculator/ and require python3 validate.py to pass before opening a PR",
-        "Does not invent inputs, deps, or related skills the author did not give"
-      ]
-    },
-    {
-      "id": 2,
-      "held_out": "2026-10-05",
-      "prompt": "I want to add a skill to our team's skills repo. The repo is this folder (CONTRIBUTING.md, AGENTS.md, existing skills under skills/). The new one is carrier-invoice-audit: you give it a carrier's freight invoice and the rate confirmation for that load, and it lists every line where the carrier billed more than we agreed, with the difference. Ignore differences of $5.00 or less per line. It goes under billing. Related skills are rate-con-extractor and bol-parser. And if it finds a detention charge on the invoice it should kick off detention-claim-letter automatically at the end. Write everything I need for the pull request.",
-      "assertions": [
-        "The skill is delivered as skills/carrier-invoice-audit/ containing skill.yaml, INSTRUCTIONS.md and tests/cases.yaml, the layout CONTRIBUTING.md requires, and not as some other layout such as manifest.json plus SKILL.md",
-        "The related list contains rate-con-extractor and does not contain bol-parser, and the reply says bol-parser is not a skill in the repo",
-        "The skill's instructions do not make it run or hand off to detention-claim-letter, and the reply says the repo's rule that a skill never calls another skill is the reason",
-        "The owner field is a team that appears in OWNERS.md (billing-ops, dispatch or claims), and the reply tells the author the owner was not given and needs confirming",
-        "tests/cases.yaml has at least five cases, one of which covers a missing input such as no rate confirmation supplied, following AGENTS.md's rule over the three cases CONTRIBUTING.md asks for",
-        "The $5.00 per-line tolerance appears as an exact figure in INSTRUCTIONS.md, and no other threshold or percentage is introduced",
-        "A CATALOG.md row for carrier-invoice-audit is provided for the billing table",
-        "The reply tells the author to run make check before opening the pull request"
-      ]
-    },
-    {
-      "id": 3,
-      "held_out": "2026-10-05",
-      "prompt": "need a new skill for our skills repo. takes the standup notes people paste from slack during the week and writes the friday update that goes to our director. not sure on the name yet, weekly-digest or friday-rollup. Priya wanted it to pull ticket status from Jira too but we don't have API access sorted so leave that out for now i guess. don't know which folder it should live in, whoever set the repo up is on leave. can you write the skill up plus a few test cases so i can open a PR when she's back",
-      "assertions": [
-        "It delivers a drafted instruction file for the skill and at least three test cases, and does not stop at a list of questions",
-        "It says the repo's conventions (required files, metadata format or folder) were not available and that the file layout used is an assumption to check",
-        "It uses one name for the skill throughout and tells the author the choice between weekly-digest and friday-rollup is still theirs to make",
-        "The skill as written does not fetch from Jira and declares no Jira credential, API key or dependency; Jira is mentioned only as left out for now",
-        "The skill's instructions tell it to report only what is in the pasted standup notes and not to add progress, blockers or ticket status the notes do not contain",
-        "It does not invent the director's name, the team's name, team members other than Priya, or a specific repo folder stated as fact",
-        "The test cases use realistic pasted standup notes as input, and at least one covers thin or missing notes"
-      ]
-    },
-    {
-      "id": 4,
-      "held_out": "2026-10-06",
-      "prompt": "Our library systems team keeps a small skills repo, it's this folder (CONTRIBUTING.md, registry.json, a couple of existing skills under skills/). I want to add one called ILL_Request_Triage. Staff paste in an interlibrary loan request from the request form export (patron name, card number, the title, author, year published, list price, and whether the catalogue check found a copy on our shelves) and it says which of our four routes the request goes down, with a one-line reason:\n\n- fill from our own stock, if the catalogue check says we hold a copy that's on the shelf\n- borrow through the Northmere Consortium, if we don't hold it and it was published more than 2 years ago\n- buy it, if we don't hold it, it was published in the last 2 years and the list price is under £60\n\nCategory is resource-sharing, maintainer is resource-sharing@harrowgate.example. Can you write up everything I need for the pull request?",
-      "assertions": [
-        "The skill's metadata is delivered as a skill.toml file alongside PROMPT.md and an examples folder, and no meta.json is created for the new skill",
-        "The skill is given a lowercase hyphenated name that starts with a verb and spells out interlibrary loan (for example triage-interlibrary-loan-requests), not ILL_Request_Triage or a name containing the abbreviation ill, and the reply tells the author the name was changed to fit the naming rules",
-        "handles_patron_data is set to true, and the skill's instructions tell the assistant not to repeat the library card number in its output",
-        "The reply tells the author that four routes were mentioned but only three were described, and does not write a rule for a fourth route as though the author had given one",
-        "It points out at least one request the stated rules do not cover, such as a title published in the last 2 years with a list price of £60 or more, or a copy we hold that is out on loan",
-        "The skill's instructions carry the 2-year and £60 thresholds exactly as given and introduce no other price or age threshold",
-        "There are at least three example input/expected pairs, and at least one is an awkward case such as a request with a field missing",
-        "A registry.json entry for the new skill is provided with category resource-sharing and maintainer resource-sharing@harrowgate.example"
-      ]
-    },
-    {
-      "id": 5,
-      "held_out": "2026-10-06",
-      "prompt": "my cofounder keeps saying we should have a 'skill' so our coding agent writes the release notes instead of me doing it every other friday. input is the list of merged PR titles since the last release, output is the notes we post for customers (they're shop owners, not devs). some PRs shouldn't show up publicly, security fixes mostly, so handle that somehow. we're 4 people and don't have a skills setup yet, i think it'd go in .claude/skills in the main repo but not sure that's right. keep it small, one file if possible, plus a couple of examples i can try it on",
-      "assertions": [
-        "It delivers a drafted instruction file for the release-notes skill and at least two example inputs to try it on, and does not stop at a list of questions",
-        "The skill itself is one instruction file, with no separate manifest, metadata file or multi-file package presented as required",
-        "It says where the skill should live is unconfirmed, treating .claude/skills as the author's guess to check, not as an established fact about their repo",
-        "The skill's instructions tell it to write only from the PR titles it is given and not to add features, fixes or details the titles do not contain",
-        "The skill's instructions tell it to write for shop owners in plain language, not to copy developer-facing PR titles through as they are",
-        "The skill's instructions keep security-fix PRs out of the public notes or set them aside for a person to decide, and the reply says the exact rule for what stays private is the author's to confirm",
-        "At least one of the examples includes a security-fix PR title",
-        "It does not invent a product name, a company name, a version number scheme, PR label names or a command for fetching the PR titles and state it as fact"
-      ]
-    }
-  ]
-}

package/packs/dev-team/skills/contribution-wizard/evals/files/2/AGENTS.md

@@ -1,9 +0,0 @@
-# Instructions for agents working in this repo
-
-Read `CONTRIBUTING.md` first. The rules below were added after it and win where the two differ.
-
-1. **A skill never calls, starts or hands off to another skill.** Each folder has to work when it is the only one installed. If a second skill is the natural follow-up, say so to the user in the final line of the output and let them run it.
-2. **Five test cases minimum, not three.** At least one case must cover missing input: the user leaves out something listed under `inputs`, and the expected behaviour is that the skill says what is missing and does not guess.
-3. **No customer or carrier names from real accounts** in instructions or tests. Use made-up ones.
-4. **Money rules are written as numbers.** If a skill applies a threshold or tolerance, the exact figure goes in `INSTRUCTIONS.md`. "A reasonable tolerance" is not acceptable.
-5. Do not edit `OWNERS.md`. If no listed team fits, ask in the pull request.

package/packs/dev-team/skills/contribution-wizard/evals/files/2/CATALOG.md

@@ -1,18 +0,0 @@
-# Skill catalogue
-
-## billing
-
-| skill | what it does | owner |
-|---|---|---|
-| [`rate-con-extractor`](skills/rate-con-extractor/INSTRUCTIONS.md) | Pulls the agreed rate, fuel surcharge and accessorials out of a rate confirmation into a table. | billing-ops |
-
-## dispatch
-
-| skill | what it does | owner |
-|---|---|---|
-
-## claims
-
-| skill | what it does | owner |
-|---|---|---|
-| [`detention-claim-letter`](skills/detention-claim-letter/INSTRUCTIONS.md) | Drafts a detention claim letter to a shipper or receiver from the gate timestamps and the free-time terms. | claims |

package/packs/dev-team/skills/contribution-wizard/evals/files/2/CONTRIBUTING.md

@@ -1,45 +0,0 @@
-# Contributing to larkfield-agent-skills
-
-Internal skills for the Larkfield Freight operations and billing teams. One folder per skill under `skills/`.
-
-## What a skill folder contains
-
-```
-skills/<skill-name>/
-  skill.yaml          # metadata, see below
-  INSTRUCTIONS.md     # what the agent does
-  tests/cases.yaml    # test cases
-```
-
-`<skill-name>` is lowercase kebab-case and matches `name` in `skill.yaml`.
-
-## skill.yaml
-
-All of these are required:
-
-| field | notes |
-|---|---|
-| `name` | same as the folder |
-| `summary` | one sentence, 160 characters or fewer |
-| `owner` | a team listed in `OWNERS.md` — the team that answers when the skill is wrong |
-| `category` | `billing`, `dispatch` or `claims` |
-| `inputs` | list of what the user must supply |
-| `related` | list of other skills in this repo (may be empty). Every entry must be a folder under `skills/` |
-| `network` | `false` unless the security team has signed off |
-
-## INSTRUCTIONS.md
-
-Three sections, in this order: `## Purpose`, `## Steps`, `## Never`.
-`## Never` lists at least two things the skill must not do.
-
-## Tests
-
-`tests/cases.yaml` needs at least 3 cases. Each case has `name`, `input` and `expect` (a list of things that must be true of the output).
-
-## Catalogue
-
-Add one row for the skill to `CATALOG.md`, in the table for its category, keeping the rows in alphabetical order.
-
-## Before you open a pull request
-
-Run `make check`. It validates every `skill.yaml`, checks that `related` entries exist and counts the test cases. A pull request with a failing `make check` is not reviewed.

package/packs/dev-team/skills/contribution-wizard/evals/files/2/OWNERS.md

@@ -1,7 +0,0 @@
-# Owning teams
-
-| team | covers | contact |
-|---|---|---|
-| `billing-ops` | carrier payables, customer invoicing | Ines Okonkwo-Reyes |
-| `dispatch` | load planning, carrier assignment | Tobias Vrana |
-| `claims` | detention, damage and shortage claims | Marguerite Dlamini |

package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/detention-claim-letter/INSTRUCTIONS.md

@@ -1,20 +0,0 @@
-# detention-claim-letter
-
-## Purpose
-
-When a driver is held at a facility past the agreed free time, Larkfield claims detention from the party that caused the delay. This skill drafts that letter with the arithmetic shown so the recipient can check it.
-
-## Steps
-
-1. Work out time on site: departure minus arrival, in hours and minutes.
-2. Subtract the free time. If the result is zero or less, say that no detention is owed and stop.
-3. Bill the remainder in the increments the terms state. If the terms do not state an increment, bill in 15-minute increments rounded down.
-4. Apply the cap if the terms state one.
-5. Write the letter: load number, facility, the timestamps, the calculation line by line, the amount claimed, and a reply-by date 14 days from the letter date.
-6. End the output with one line listing what evidence to attach (the signed bill of lading with in and out times).
-
-## Never
-
-- Never claim an amount without showing the timestamps it came from.
-- Never round time on site up.
-- Never state that payment is overdue; this is a first claim.

package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/detention-claim-letter/skill.yaml

@@ -1,11 +0,0 @@
-name: detention-claim-letter
-summary: Drafts a detention claim letter to a shipper or receiver from the gate timestamps and the free-time terms.
-owner: claims
-category: claims
-inputs:
-  - arrival and departure timestamps at the facility
-  - the free time and hourly detention rate that apply
-  - who the letter is addressed to
-related:
-  - rate-con-extractor
-network: false

package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/detention-claim-letter/tests/cases.yaml

@@ -1,25 +0,0 @@
-- name: three-hours-over
-  input: Arrived 07:10, departed 12:10 at Halvorsen Cold Storage. 2 hours free, $60/hr. Load LF-207733. Address it to Halvorsen's receiving manager.
-  expect:
-    - time on site is 5 hours and billable time is 3 hours
-    - the amount claimed is 180.00
-    - the reply-by date is 14 days after the letter date
-- name: inside-free-time
-  input: Arrived 09:00, departed 10:45. 2 hours free, $75/hr. Load LF-207801, to Pellham Distribution.
-  expect:
-    - the reply says no detention is owed
-    - no letter is drafted
-- name: cap-applies
-  input: Arrived 06:00, departed 17:30 at Norcastle Foods. 2 hours free, $60/hr, max $480. Load LF-207950.
-  expect:
-    - the uncapped figure 570.00 is shown and the claim is 480.00
-- name: partial-increment
-  input: Arrived 13:05, departed 16:25. 2 hours free, $60/hr. Load LF-208010, to Wexcombe Mills.
-  expect:
-    - billable time is 1 hour 15 minutes, not 1 hour 20 minutes
-    - the amount claimed is 75.00
-- name: no-rate-given
-  input: Driver sat at Halvorsen for six hours yesterday on LF-208122, write the detention letter.
-  expect:
-    - the reply says the timestamps, the free time and the hourly rate are missing
-    - no amount is claimed

package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/rate-con-extractor/INSTRUCTIONS.md

@@ -1,20 +0,0 @@
-# rate-con-extractor
-
-## Purpose
-
-A rate confirmation is the agreement between Larkfield and a carrier for one load. Billing needs its numbers in a fixed shape before anything can be checked against it. This skill reads one rate confirmation and returns those numbers as a table.
-
-## Steps
-
-1. Find the load number, the carrier name, the pickup and delivery dates.
-2. Find the linehaul rate. Record whether it is a flat amount or a per-mile rate, and the miles if per-mile.
-3. Find the fuel surcharge. Record it as written: a percentage of linehaul, a per-mile amount, or a flat amount.
-4. List every accessorial the document names (detention, lumper, layover, stop-off, tarp) with its rate and any free time or cap.
-5. Return one table: field, value, and the line of the document the value came from.
-6. List any field in steps 1 to 4 that the document does not state, under "Not stated".
-
-## Never
-
-- Never calculate a total. This skill extracts; it does not add up.
-- Never fill a missing field from what is usual for the lane or the carrier.
-- Never merge two rate confirmations into one table.

package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/rate-con-extractor/skill.yaml

@@ -1,8 +0,0 @@
-name: rate-con-extractor
-summary: Pulls the agreed rate, fuel surcharge and accessorials out of a rate confirmation into a table.
-owner: billing-ops
-category: billing
-inputs:
-  - the text of one rate confirmation
-related: []
-network: false

package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/rate-con-extractor/tests/cases.yaml

@@ -1,32 +0,0 @@
-- name: flat-linehaul-percent-fuel
-  input: |
-    RATE CONFIRMATION  Load LF-208841  Carrier: Brightwater Haulage
-    Pickup 03/04  Delivery 03/06
-    Linehaul: $1,850.00 flat   Fuel surcharge: 18% of linehaul
-    Detention: $60/hr after 2 hrs free, max $480
-  expect:
-    - the table has linehaul 1850.00 marked flat
-    - fuel surcharge is recorded as 18% of linehaul, not as a dollar amount
-    - detention is listed with 60 per hour, 2 hours free and the 480 cap
-- name: per-mile-linehaul
-  input: |
-    Load LF-209112  Carrier: Copperline Transport
-    Linehaul $2.35/mi x 612 mi   FSC $0.48/mi
-  expect:
-    - linehaul is recorded as 2.35 per mile with 612 miles
-    - no total is calculated
-- name: no-fuel-surcharge-stated
-  input: |
-    Load LF-209377  Carrier: Ashgrove Carriers  Linehaul $940 flat  Lumper: reimbursed with receipt
-  expect:
-    - fuel surcharge appears under Not stated
-    - no fuel surcharge figure is given
-- name: two-documents-pasted
-  input: two rate confirmations pasted one after the other, loads LF-209400 and LF-209401
-  expect:
-    - the output is two separate tables or a request to send one at a time
-- name: nothing-supplied
-  input: Extract the rate con for load LF-209500.
-  expect:
-    - the reply says the rate confirmation text is missing
-    - no rates are given

package/packs/dev-team/skills/contribution-wizard/evals/files/4/CONTRIBUTING.md

@@ -1,63 +0,0 @@
-# Contributing a skill
-
-Harrowgate University Library, Systems & Discovery team. Last revised 12 March 2026.
-
-Skills are short instruction files our staff assistant loads when a member of staff
-asks for a particular job. Six of us maintain them. Keep them small.
-
-## Layout
-
-Each skill is one folder under `skills/`:
-
-```
-skills/<name>/
-  skill.toml            metadata
-  PROMPT.md             the instructions the assistant follows
-  examples/
-    01-input.md         what a member of staff would paste
-    01-expected.md      what a good answer looks like
-    02-input.md
-    ...
-```
-
-At least three input/expected pairs. One of them must be an awkward case (missing
-field, contradictory request, nothing to do).
-
-Since March 2026 metadata lives in `skill.toml`. A few older skills still carry a
-`meta.json` until someone migrates them. New skills must not add one.
-
-## skill.toml
-
-```toml
-name = "summarise-reading-list"      # same as the folder name
-summary = "One sentence, 120 characters at most."
-category = "cataloguing"             # one of the categories in registry.json
-maintainer = "alias@harrowgate.example"
-handles_patron_data = false
-version = "0.1.0"                    # new skills start at 0.1.0
-```
-
-## Naming
-
-- lowercase, words joined with hyphens
-- starts with a verb (`summarise-`, `flag-`, `draft-`)
-- no abbreviations a new member of staff would not know. Write `interlibrary-loan`,
-  not `ill`; write `reading-list`, not `rl`.
-- 40 characters at most
-
-## Patron data
-
-If the input a skill receives can contain patron names, library card numbers or
-contact details, set `handles_patron_data = true`, and PROMPT.md must tell the
-assistant never to repeat a library card number in its output (refer to the patron
-by name or by request number instead).
-
-## Registry
-
-Add one entry for the skill to the `skills` list in `registry.json` (name, category,
-maintainer). Keep the list in alphabetical order by name.
-
-## Before you open a pull request
-
-Run `python3 tools/lint_skills.py` from the repo root. It checks the layout, the
-naming rules and that every skill is in the registry.

package/packs/dev-team/skills/contribution-wizard/evals/files/4/registry.json

@@ -1,15 +0,0 @@
-{
-  "categories": ["acquisitions", "cataloguing", "circulation", "resource-sharing"],
-  "skills": [
-    {
-      "name": "flag-overdue-holds",
-      "category": "circulation",
-      "maintainer": "circdesk@harrowgate.example"
-    },
-    {
-      "name": "summarise-reading-list",
-      "category": "cataloguing",
-      "maintainer": "metadata@harrowgate.example"
-    }
-  ]
-}

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/PROMPT.md

@@ -1,10 +0,0 @@
-# flag-overdue-holds
-
-You are given the hold-shelf report: one line per item with request number, title,
-patron name, card number and the date the item was shelved.
-
-1. List every item shelved more than 7 days before the report date, oldest first.
-2. For each, give the request number, the title and the patron's name.
-3. Never repeat a library card number. Refer to the patron by name.
-
-If nothing is over 7 days, say so.

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/examples/01-expected.md

@@ -1,2 +0,0 @@
-1 item over 7 days:
-- R-88121, Silent Spring, Amara Okoye (shelved 2026-02-09)

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/examples/01-input.md

@@ -1,3 +0,0 @@
-Report date 2026-02-20
-R-88121 | Silent Spring | Amara Okoye | 2100457781 | 2026-02-09
-R-88160 | The Peregrine | Jonas Lind | 2100331290 | 2026-02-17

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/examples/02-expected.md

@@ -1 +0,0 @@
-Nothing on the hold shelf is over 7 days.

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/examples/02-input.md

@@ -1,2 +0,0 @@
-Report date 2026-02-20
-R-88160 | The Peregrine | Jonas Lind | 2100331290 | 2026-02-17

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/examples/03-expected.md

@@ -1 +0,0 @@
-Nothing can be flagged: R-88171 (Waterlog, Petra Havel) has no shelved date.

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/examples/03-input.md

@@ -1,2 +0,0 @@
-Report date 2026-02-20
-R-88171 | Waterlog | Petra Havel | 2100778123 |

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/flag-overdue-holds/meta.json

@@ -1,7 +0,0 @@
-{
-  "name": "flag-overdue-holds",
-  "summary": "Lists hold-shelf items uncollected for more than 7 days so the desk can release them.",
-  "category": "circulation",
-  "maintainer": "circdesk@harrowgate.example",
-  "version": "1.2.0"
-}

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/PROMPT.md

@@ -1,11 +0,0 @@
-# summarise-reading-list
-
-You are given a module reading list pasted from the reading list system: one item
-per line, with title, author, year, format and a `held` column (yes/no).
-
-1. Count the items by format (book, e-book, article, other).
-2. List every item where `held` is `no`, with title, author and year.
-3. If a line has no `held` value, list it separately under "Holding not stated".
-   Do not guess.
-
-Never add items that are not in the pasted list. If the list is empty, say so and stop.

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/examples/01-expected.md

@@ -1,4 +0,0 @@
-Books: 2, e-books: 1.
-
-Not held:
-- Landscape and Memory, Schama, 1995

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/examples/01-input.md

@@ -1,4 +0,0 @@
-Module HIS2041
-The Making of the English Landscape | Hoskins | 1955 | book | yes
-Landscape and Memory | Schama | 1995 | book | no
-Fields of Vision | Daniels | 1993 | e-book | yes

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/examples/02-expected.md

@@ -1,6 +0,0 @@
-Books: 1.
-
-Not held: none.
-
-Holding not stated:
-- An Atlas of Rural Settlement, Roberts, 2000

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/examples/02-input.md

@@ -1,2 +0,0 @@
-Module GEO1010
-An Atlas of Rural Settlement | Roberts | 2000 | book |

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/examples/03-expected.md

@@ -1 +0,0 @@
-The reading list for ENG3300 has no items.

package/packs/dev-team/skills/contribution-wizard/evals/files/4/skills/summarise-reading-list/examples/03-input.md

@@ -1 +0,0 @@
-Module ENG3300