Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nthnclrk/enablement-skills --skill onboarding-to-value-playbookgit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nthnclrk/enablement-skills/onboarding-to-value-playbook)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/onboarding-to-value-playbook"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/onboarding-to-value-playbook/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/onboarding-to-value-playbook"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/onboarding-to-value-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.00937 |
| Opus 5 | $0.00030 | $0.00468 |
| Sonnet 5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
onboarding-to-value-playbook scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding to value playbook
Get a customer to first value by segment. This is customer onboarding, not seller ramp.
A good playbook names the first observable value event, who confirms it, and the few milestones that make it happen. If the user wants new-hire seller ramp, use onboarding-program-builder. If they want a partner pack, use partner-enablement-package.
First value. "Mid-market assisted: the ops owner closes their first exception from the new queue without a workaround. Evidence: product event plus customer confirmation in the week-2 review."
Not value. "Users provisioned. Kickoff held. Admin logged in twice."
If setup completion is being sold as time-to-value, rewrite it.
Confirm Inputs First
Ask only for the inputs that change the journey:
- Customer segment and motion: self-serve, assisted, enterprise
- Desired first-value outcome, the observable event that would prove it, and any customer-agreed horizon
- Measurement clock: start event, end event, pauses, window, owner
- Implementation constraints and sales-to-CS-to-services handoffs
- Known early-risk patterns and commercially critical checkpoints
If a baseline, SLA, or horizon is missing, leave it TBD. Do not invent usage thresholds, TTV targets, or pricing.
Read The Right Reference
Read references/ttv-playbook-framework.md before setting value events, milestones, or risk triggers. Skip it if the user already defined first value and only wants the operating cadence.
Default Workflow
- Define first value, not first login. Actor, observable result, evidence source, acceptance criteria, who confirms. Setup and login are activation unless the customer agreed they are the outcome. Done when you can say what "they got value" looks like in one sentence.
- Set the clock. Start event, end event, pauses, owner. Do not default the start to kickoff when contract activation, provisioning, or data-ready governs the work. An unagreed horizon is proposed, not promised.
- Segment the journey. Depth and support intensity change by self-serve, assisted, and enterprise. Done when the same playbook is not being forced on every segment.
- Work backward from the value event. Only the enabling activation, adoption, and outcome milestones needed. Each has owner, output, due window, and acceptance criteria.
- Make handoffs inspectable. Who owns the transition and what context must transfer. Sales-to-CS is not "the deal closed."
- Attach early-risk controls.
Qualitative triggers unless a threshold comes from the customer, an SLA, historical segment data, or a measured baseline. Numeric invention stays
TBD. - Split the two views. Customer-visible plan: milestones, owners, due windows, success checks. Internal plan: risk, escalation, caveats. Keep dates aligned.
- Set cadence to the horizon. Check-ins follow dependencies and risk, not a blanket weekly calendar.
- Hook renewal and expansion later.
Readiness checks from the contract horizon and demonstrated value. Do not bolt on an upsell track during first-value work. For reusable renewal plays, use
renewal-and-expansion-enablement.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 79 lines · 59 tokens per session scan A 9ae8301ebc28
onboarding-to-value-playbook is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 23d ago), licensed MIT. It adds 59 tokens to every session and 937 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…