ericrisco/rsc-harness / skills/procurement
procurement
VerifiedUse when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is `contracts`), NOT the price you charge customers (that is `pricing`), NOT stock once it lands (that is `inventory`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.5 KB |
| evals/README.md | markdown | 1.4 KB |
| evals/cases.yaml | config | 3.2 KB |
| references/scorecard-and-tco.md | markdown | 4.0 KB |
| references/sourcing-requests.md | markdown | 4.5 KB |
| scripts/verify.shexecutable | script | 11.0 KB |
evals/README.md
View on GitHub# Evals — procurement
`cases.yaml` holds three groups: `should_trigger`, `should_not_trigger`, and a
`capability` case. These are LLM-graded routing and capability checks, not unit
tests. Run them through whatever eval harness the repo provides, or by hand: feed
each `should_trigger` prompt to the router and confirm it selects `procurement`
(including the non-obvious ones — the "actually cheaper over three years" TCO trap
and the "2/10 net 30" early-payment-discount question that masquerades as an AP
task — and the Spanish/Catalan phrasings). Feed each `should_not_trigger` prompt
and confirm it routes to the named sibling (`contracts`, `pricing`, `inventory`,
`logistics-ops`, `bookkeeping`) and not here; every `route_to` id must resolve to
a real sibling skill. Grade the `capability` case against its `must_include`
rubric on an actual generated answer: tick each line (Kraljic segmentation,
weights summing to 100, TCO not unit price, the early-discount math, single-source
risk + backup plan, hand-offs to contracts/inventory). Pair the capability grade
with `scripts/verify.sh` against any generated scorecard/TCO file to confirm the
artifact ties out (weights sum to 100, no blank scores, recomputed totals match,
TCO has more than a unit line) — the rubric judges sourcing judgment, verify.sh
judges structural consistency. No automated harness is assumed beyond reading the
prompts and checking routing plus the rubric.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |