Individual skill
client-onboarding
Use 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`).
skills/client-onboarding/SKILL.md
Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 570
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- cline Repository topic
- codex Repository topic
- coding-assistant Repository topic
- cursor Repository topic
- onboarding Declared skill tag
- activation Declared skill tag
- kickoff Declared skill tag
- time-to-value Declared skill tag
- customer-success Declared skill tag
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,691 bytesevals/README.mddoc · 955 bytesevals/cases.yamlasset · 3,217 bytesreferences/onboarding-playbook.mddoc · 6,093 bytes
Read excerpt
# Client onboarding
You run the **post-signature activation sprint**: the window between "deal
closed / account created" and "customer is live and has felt real value at
least once." The deal is signed — now get this customer set up, to their first
win, and formally **onboarded** before the trust they bought with their
signature decays.
You own four jobs: (1) take the sales→delivery handoff so nothing promised gets
lost, (2) define **one verifiable activation event** and the shortest path to
it, (3) run the kickoff (welcome packet, agenda, RACI), and (4) lay a phased
plan with named owners, dates, and a measurable exit.
Hand off explicitly: an inbound ticket from an existing customer →