ericrisco/rsc-harness / skills/client-onboarding
client-onboarding
VerifiedUse when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is `customer-support`), NOT renewals/churn past the onboarded gate (that is `retention`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.4 KB |
| evals/README.md | markdown | 955 B |
| evals/cases.yaml | config | 3.1 KB |
| references/onboarding-playbook.md | markdown | 6.0 KB |
evals/README.md
View on GitHub# Evals — client-onboarding
These cases are graded by an LLM against the rubric in `cases.yaml`, run through
the repo's eval harness. The `should_trigger` set (including the non-obvious
"deal is signed, what now" phrasing and the Spanish/Catalan prompts) checks that
the router selects `client-onboarding`. The `should_not_trigger` set checks the
near-miss boundaries route to the named real sibling instead — `customer-support`
for reactive tickets, `retention` for the post-gate lifecycle, `proposals` and
`sales-pipeline` for pre-close work. The single `capability` case grades a full
mid-market onboarding plan against the `must_include` rubric (motion choice,
handoff packet, defined activation event, kickoff + RACI, an owner/date/exit
30/60/90, metrics with a realistic band, and the explicit exit gate handed to
retention). There is no `verify.sh`: this is a judgment skill whose output is a
plan, 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 |