ericrisco/rsc-harness / skills/customer-support
customer-support
VerifiedUse when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is `technical-writing`), a win-back program (`retention`), or the auto-answer bot (`chatbot`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| evals/README.md | markdown | 836 B |
| evals/cases.yaml | config | 4.3 KB |
| references/macros-and-sla.md | markdown | 5.5 KB |
evals/README.md
View on GitHub# Evals — customer-support
These cases are graded by an LLM judge against `cases.yaml`, run through the
repo's eval harness. `should_trigger` and `should_not_trigger` check routing —
that a real support ticket loads this skill while near-misses (writing the KB
doc, the onboarding flow, the win-back program, the voice guide, the bot) route
to their correct sibling. The `capability` case checks reply *quality*: the
judge scores the produced triage + draft against the `must_include` rubric
(P1 + FRT target, acknowledge-before-promise, de-escalation without banned
phrases, no invented fix/ETA, an escalation handoff packet, the right metric).
There is no `verify.sh` — this is a judgment skill whose output is a triaged
ticket and a drafted reply, not a machine-checkable artifact, so the capability
rubric carries the rigor.
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 |