Agent skill
onboarding-handoff
Run the Won→onboarding handoff — the seam most teams drop.
Filed under Onboarding, retention and expansion.
From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03
What it does when it runs
Run the Won→onboarding handoff — the seam most teams drop. Trigger when a deal is marked won/closed-won, when the user says "we won X", "hand this off to onboarding", "kick off the new customer", or "onboarding checklist".
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/onboarding-handoff" mkdir -p ~/.claude/skills/onboarding-handoff cp -R "/tmp/claude-code-growth-os/.claude/skills/onboarding-handoff/." ~/.claude/skills/onboarding-handoff/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/onboarding-handoff/SKILL.md, which is licensed MIT (repository). 349 words, 2 headings.
Onboarding Handoff (Won → onboarding)
The handoff most teams never define: a signed deal drops silently into a customer-success void, the value the buyer was sold gets lost, and the renewal clock starts late. This is handoff H3 in docs/operating-model.md — made concrete as a 48-hour checklist that turns a won deal into the first row of the account book.
From the won deal (point me at the row in ops/pipeline.md, or paste the deal context):
- Carry the value hypothesis forward. Write down, in one line, what the customer bought this to do — in their words, from discovery. This becomes the value hypothesis in
ops/customers.md, and the thing every adoption check is measured against. Lose it here and onboarding optimizes for activity, not value. - Set the date markers. Record the renewal date, the contract value (ARR — the number the book rolls up to NRR), and note the day-60 renewal-motion trigger (not day-85). Set a first-expansion check date too — the moment to look for a second team or use case.
- Identify the power user / champion. Name who will actually use it and who sponsors it internally. A single-threaded account is a churn risk before it's even live — if there's only one name, that's the first gap to close.
- Write the first adoption milestone. One concrete, dated outcome that proves value is landing (the first workflow live, the first cross-system answer, the first report shipped). Vague onboarding has no finish line.
- Open the row. Create the account in
ops/customers.mdat stage Onboarding, with the value hypothesis, the ARR, the first adoption signal to watch, the renewal date, an owner, and the next step. Offer to log the handoff inops/daily-log.md.
Don't invent commitments the deal didn't contain. Bring your own onboarding playbook; this carries the deal's context across the seam so nothing drops.
Depth
- quick: open the
ops/customers.mdrow with value hypothesis, renewal date, and owner. - standard: the full 48-hour checklist above.
- deep: + a single-threading risk read and the first two adoption milestones with dates.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- onboarding by coreyhaines31 · 54,316
- icp-onboarding by growthenginenowoslawski · 759
- onboarding-cro by OpenClaudia · 714
- onboarding-flow by shawnpang · 350
- handoff by sno-ai · 264
- customer-onboarding by louisblythe · 179
- handoff-detection by louisblythe · 179
- suede-onboarding by JasonColapietro · 127
Need help setting it up?
This page tells you what onboarding-handoff does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.