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/cases.yaml
View on GitHubskill: client-onboarding
should_trigger:
- prompt: "We just closed a new enterprise account — build me an onboarding plan with a kickoff and a 30/60/90."
why: "Core high-touch motion: post-signature activation plan with kickoff + phased success plan."
- prompt: "How do I define our activation event — what should 'first value' mean for a new signup?"
why: "Core job: defining the one verifiable activation event before onboarding toward it."
- prompt: "The deal is signed, what happens now so they don't go cold before they're live?"
why: "Non-obvious — never says 'onboarding'; it's the post-signature trust-decay window this skill owns."
- prompt: "Plan de onboarding para un cliente nuevo con kickoff y plan de 30/60/90."
why: "Spanish trigger for the same high-touch onboarding plan; must still route here."
- prompt: "Design a day-0 to day-14 nudge sequence to get new free-trial users to their aha moment."
why: "Self-serve PLG motion + time-to-value; the day-0→14 activation sequence is squarely this skill."
- prompt: "Munta'm el handoff de vendes a CS per a un client que acaba de signar."
why: "Catalan, and targets the sales→delivery handoff sub-job specifically."
should_not_trigger:
- prompt: "A current customer emailed that the app is down — handle this support ticket."
route_to: customer-support
why: "Reactive inbound triage from an existing customer, not the proactive first-30-days activation."
- prompt: "Build our renewal and churn-reduction program with customer health scores."
route_to: retention
why: "Ongoing lifecycle after the onboarded gate; this skill ends at that gate."
- prompt: "Write the proposal and SOW to send this prospect before they sign."
route_to: proposals
why: "Pre-close document; client-onboarding starts only after the deal is won."
- prompt: "Move this deal from discovery to negotiation and forecast the quarter."
route_to: sales-pipeline
why: "Pre-close deal stages and forecasting, not the post-close handoff."
capability:
- scenario: "A B2B SaaS just closed a mid-market account. The operator has the signed order form and a one-line sales note ('they bought to consolidate reporting; champion is the VP Ops; hard go-live before their Q3') and asks for a full onboarding plan."
must_include:
- "Picks the high-touch motion and says why (named account, signed order form, multiple stakeholders)."
- "Produces a sales→delivery handoff packet: stakeholders/roles, purchase drivers, promised scope, success criteria the buyer bought, known risks, timeline."
- "Defines one verifiable activation event tied to core value and predictive of retention — written as a measurable sentence, not 'logged in'."
- "Supplies a kickoff agenda covering the six areas (intros, overview, roles/RACI, comms plan, action items, Q&A) plus a compact RACI."
- "Lays a 30/60/90 with an owner + date + exit milestone per phase, front-loading days 1–30."
- "Names onboarding metrics (TTV, activation rate, early-churn) with a realistic target band, not a vanity number."
- "States an explicit 'onboarded' exit gate and hands off to retention."
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 |