ericrisco/rsc-harness / skills/logistics-ops
logistics-ops
VerifiedUse when an order is paid and packed and the box now has to move, go sideways, or come back — picking a carrier and service and cutting a label, reacting to a delivery exception, getting ahead of where-is-my-order tickets, running a return, exchange or refund with its reverse label, filing a carrier claim before the window closes, and setting return-window and restocking-fee policy. NOT setting stock levels or reorder points (that is `inventory`), NOT sourcing or buying from suppliers (that is `procurement`), NOT writing the apology to the customer (that is `customer-support`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.9 KB |
| evals/README.md | markdown | 1.4 KB |
| evals/cases.yaml | config | 3.8 KB |
| references/carriers-and-claims.md | markdown | 5.6 KB |
evals/README.md
View on GitHub# Evals — logistics-ops
`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 — there is no `verify.sh`, because the skill emits operational judgment (a
carrier choice, an exception-response plan, a return disposition, a claim-filing
call), not a single machine-checkable artifact. Run them through whatever eval
harness the repo provides, or by hand: feed each `should_trigger` prompt to the
router and confirm it selects `logistics-ops` — including the non-obvious one (the
"delivery exception, what do I tell the customer" prompt that never says "shipping")
and the Spanish/Catalan return and rate-shop phrasings. Feed each
`should_not_trigger` prompt and confirm it routes to the named sibling
(`inventory`, `procurement`, `customer-support`, `bookkeeping`, `webhooks`) 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 — damage → same-business-day outreach, the claim window + evidence at
detection, the dual 60-day/15-day clocks, the proactive tracker-fact message with
tone handed to customer-support, exchange/store-credit before cash with no
restocking fee on a defect, and the hand-offs to bookkeeping and inventory — and
confirm it never invents an ETA the carrier didn't give.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |