agentsclimarketplace

Onboarding handoff

Skill etrebels/claude-code-growth-os/.claude/skills/onboarding-handoff

Claude Code Growth Operating System (OS): Sales, Marketing, Product and Retention as one Revenue system

Install
npx -y skills add etrebels/claude-code-growth-os --skill onboarding-handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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".

SKILL.md

2.4 KB, as published. Nobody here has run it

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):

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Open the row. Create the account in ops/customers.md at 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 in ops/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.md row 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.