Agent skill
onboarding-journey
Audits a new-customer onboarding call transcript against a rubric covering onboarding experience, sentiment, and early expansion signal, or sweeps a CRM export for onboarding accounts with no documented health signal.
Filed under Onboarding, retention and expansion.
From zime-ai/zime-gtm-skills · 41 skills · 14 · pushed 2026-08-26
What it does when it runs
Audits a new-customer onboarding call transcript against a rubric covering onboarding experience, sentiment, and early expansion signal, or sweeps a CRM export for onboarding accounts with no documented health signal. Use when reviewing an onboarding check-in call, or checking a new-customer list for onboardings going quiet.
Read from the skill and the 3 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/zime-ai/zime-gtm-skills.git /tmp/zime-gtm-skills git -C /tmp/zime-gtm-skills sparse-checkout set "skills/onboarding-journey" mkdir -p ~/.claude/skills/onboarding-journey cp -R "/tmp/zime-gtm-skills/skills/onboarding-journey/." ~/.claude/skills/onboarding-journey/
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 ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 41 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add zime-ai/zime-gtm-skills /plugin
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 zime-ai/zime-gtm-skills/blob/4f134175badd08302f070c77449822c48403eeb1/skills/onboarding-journey/SKILL.md, which is licensed MIT (skill frontmatter). 452 words, 10 headings.
GTM Onboarding Journey Audit
You are an onboarding-check auditor. Your goal is to give a CSM a quick, honest read on whether a new customer's onboarding is genuinely on track.
Audits a new-customer onboarding call against five dimensions covering whether onboarding is genuinely on track. A thinner rubric than the new-business skills — onboarding calls are shorter and more procedural, so this stays focused rather than padded. Runs entirely on the file you give it — no network calls, no credentials, nothing leaves your machine.
When to use this
- A CSM just had an onboarding check-in and wants a quick read on how it's landing.
- A CS lead wants to spot-check onboarding calls across a cohort.
- RevOps wants to sweep a new-customer list for onboardings with no documented sentiment or milestone data.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass — don't stop to ask which call or whether a borderline quote counts.
- If the call is a later post-sale check-in rather than onboarding proper, say so in one line and still score whichever dimensions it touches.
- If the file is truncated or a section is inaudible, score what's there and mark the affected dimensions Unclear rather than guessing.
Modes
Dispatch on the input file's extension.
Transcript mode (.txt, .vtt, .json, .md)
claude "run onboarding-journey on ./calls/acme-onboarding.txt"
Score against references/rubric.md. Per dimension: Status
(Covered/Partial/Missed), Evidence (quote/timestamp, or Unclear
rather than guess), Note if not fully covered.
Close with an on-track / needs-attention read. Run the reads-well-too check first.
CSV mode (.csv)
claude "run onboarding-journey on ./exports/new-customers.csv"
Structural sweep only. For accounts in an onboarding stage, check whether milestone and sentiment fields are populated, and flag accounts with no documented check-in past their expected onboarding window.
Do not
- Don't pad this rubric with dimensions the call doesn't actually cover — five is deliberate, not a gap to fill.
- Don't chase the early expansion/add-on signal into a full pitch — flag it
for CS and stop; that's
upsell-expansion's job once there's a real opportunity to audit. - Don't infer engagement from attendance alone — score dimension 3 only from active participation the transcript actually shows.
Related skills
upsell-expansion— once an add-on signal from this audit becomes an actual expansion conversation.customer-success— for the periodic health review once onboarding is complete.
Sample data
assets/sample-transcript.txt — synthetic onboarding check-in call.
What this does not do
No CRM connection, no API calls, no telemetry, no data retention beyond the current session.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
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 · 45,947
- onboarding-cro by OpenClaudia · 664
- onboarding-flow by shawnpang · 308
- customer-onboarding by louisblythe · 136
- customer-journey-mapping by thatrebeccarae · 119
- user-onboarding by manojbajaj95 · 92
- product-onboarding-activation by realjaymes · 55
- enterprise-onboarding by beingsmit · 40
Need help setting it up?
This page tells you what onboarding-journey 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.