Client Onboarding
ericrisco/rsc-harnessUse 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`).
At a glance
This skill is for Support and helps you create a client onboarding plan, plan a sales to delivery handoff, and define activation milestones for new customers.
git clone --depth 1 https://github.com/ericrisco/rsc-harness
cp -r rsc-harness/skills/client-onboarding ~/.claude/skills/client-onboarding
Setup, runtime and requirements describe ericrisco/rsc-harness, the repo this skill ships in.
Activation306090Customer SuccessKickoffHandoffOnboarding Plan
Also in ericrisco/rsc-harness
View the repoUse when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CU...
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA...
Use when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platfo...
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge,...
Use when bounding an LLM agent that already runs — scoping its task domain, gating tools to least privilege, defending against prompt inject...
Use when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-vid...
Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PI...
Use when constitution, spec, plan and tasks all exist and you want them cross-read against each other before any code is written — the rsc-s...
Use when building, refactoring, or debugging Angular (v20/21+): standalone components, signals, zoneless change detection, @if/@for/@defer c...
Use when writing a client for someone else's REST or GraphQL API: auth flow choice and token refresh, pagination to exhaustion, retry-with-j...
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error...
Use when writing one long-form article end to end — answer-first lede, question-shaped headings, plus its on-page surface (title, meta, slug...
Other Support skills
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the con...
Implement a piece of work based on a spec or set of tickets.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve th...
Google Model Armor: Filter user-generated content for safety.
Manage customer support — track tickets, respond, escalate issues.
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL fil...