Agent skill
evp-onboarding
First-run interactive setup for the EVP skill pack.
Filed under Onboarding, retention and expansion.
From cmj-hub/claude-evp · 5 skills · 2 · pushed 2026-09-09
What it does when it runs
First-run interactive setup for the EVP skill pack. Walks the operator through brand-config.json (awareness tier, outcomes-I-will-claim, proofs reservoir, competitors) and SOUL.md (tier-by-tier voice, won't-claim list, boundaries) in ~10 minutes. Refuses to let the operator skip — generic EVP is worse than no EVP. Loaded automatically when brand-config.json or SOUL.md is missing.
Read from 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
- Read
- Write
- -
- Grep
- 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/cmj-hub/claude-evp.git /tmp/claude-evp git -C /tmp/claude-evp sparse-checkout set "skills/evp-onboarding" mkdir -p ~/.claude/skills/evp-onboarding cp -R "/tmp/claude-evp/skills/evp-onboarding/." ~/.claude/skills/evp-onboarding/
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 5 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add cmj-hub/claude-evp /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 cmj-hub/claude-evp/blob/bd5c27a35eda62287937e9459728a6670f2ae86e/skills/evp-onboarding/SKILL.md, which is licensed MIT (skill frontmatter). 636 words, 12 headings.
EVP Onboarding — first-run setup
10 minutes of setup that makes every downstream EVP differentiated instead of generic.
Activation
Loaded automatically by evp orchestrator when brand-config.json
or SOUL.md is missing.
Also user-invocable: "Set up EVP brand config", "EVP onboarding".
Workflow
Step 1 — ICP + PSP carry-forward
Quick check — do you already have a PSP?
If yes (claude-psp is installed and PSP doc exists): I'll pull ICP + pain + vocabulary from there.
If no: Install cmj-hub/claude-psp first. EVP without a PSP is a guess.
Step 2 — Primary outreach tier
Where is YOUR buyer on the Schwartz tier ladder when they meet you?
Most B2B buyers live in Tiers 2-4. Pick the most common one for your outreach:
Tier 1 (unaware) — you have to reveal the pain first
Tier 2 (problem-aware) — they know the pain, no solutions evaluated
Tier 3 (solution-aware) — they're comparing categories (in-house / agency / tool)
Tier 4 (product-aware) — comparing specific vendors
Tier 5 (most aware) — ready to buy
If you don't know, default to Tier 3 — most outbound campaigns target
that tier.
Save to brand-config.primary_outreach_tier.
Step 3 — Outcomes-I-will-claim list
What specific outcomes are you willing to claim in writing?
Each outcome needs:
1. A specific noun (not a verb — "14 SQLs", not "more pipeline")
2. A specific timeframe (in 30 days, per month, per quarter)
3. A proof point you can back it with
Examples of GOOD outcomes:
"14+ SQLs per month"
"Targeted-outbound CPM under $700"
"First positive reply within 7 days"
Examples of BAD outcomes (refuse to claim):
"Better demand-gen"
"Improved efficiency"
"Best-in-class outreach"
Give me 3-5 outcomes you're willing to claim. These constrain every
downstream EVP variant.
Save to SOUL.md (outcomes-I-will-claim list) + brand-config.evp_drafts.tier_3.outcome.
Step 4 — Tradeoffs you name
For each outcome, what's the obvious tradeoff you spare them from?
The EVP shape is "<outcome> without <tradeoff>". The tradeoff carries
the line — name something they'd otherwise have to give up.
Examples:
"without hiring 2 more SDRs"
"without breaking the PLG self-serve motion"
"without paying agency retainer rates"
Save to brand-config.evp_drafts.tier_3.tradeoff + SOUL.md.
Step 5 — Proofs reservoir
Give me 3-5 concrete proofs you can cite. Each is anonymized but
specific.
Examples:
"Series-B SaaS hit 14 SQLs in 30 days from a PSP rewrite — case study at /case-studies/X"
"Bootstrapped agency went 2% → 11% reply rate by killing demographic targeting"
These become the proof reservoir — EVP variants pull from here, not
fabricated case studies.
Save to SOUL.md.
Step 6 — Competitors (for Tier 4 EVPs)
For Tier 4 EVPs, you need to name competitors and your delta on a
specific axis.
Top 2-3 competitors + the axis you beat them on:
1. Generic outbound agency — CPM efficiency
2. AI SDR vendor — reply quality vs volume
3. In-house SDR build — time-to-payback
Save to brand-config.competitors.
Step 7 — Voice (SOUL.md)
Per-tier voice settings:
Tier 2 (problem-aware) — tone: ?
Tier 3 (solution-aware) — tone: ?
Tier 4 (product-aware) — tone: ?
Won't-write list:
• <e.g. industry guarantees you don't actually back>
• <e.g. competitor names you won't reference by full brand>
Save to SOUL.md.
Step 8 — Write the files + smoke test
Write brand-config.json + SOUL.md at project root. Show:
✓ brand-config.json — Tier 3 primary + 3 outcomes + 3 competitors
✓ SOUL.md — outcomes-will-claim list + 4 proofs + tier voice
Try a smoke test:
> Generate a Tier 3 EVP for my ICP
The output will use:
- Your outcomes-will-claim list (refuses outside it)
- Your tradeoffs
- Proofs from your reservoir
References
../../brand-config.example.json../../SOUL.md../../AGENTS.md- Sister skills:
evp-craft,evp-brief
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 · 50,138
- icp-onboarding by growthenginenowoslawski · 705
- onboarding-cro by OpenClaudia · 691
- onboarding-flow by shawnpang · 324
- customer-onboarding by louisblythe · 153
- suede-onboarding by JasonColapietro · 135
- user-onboarding by manojbajaj95 · 100
- product-onboarding-activation by realjaymes · 60
Need help setting it up?
This page tells you what evp-onboarding 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.