AGENT SKILL

evp-craft

Generate 3 EVP variants for a single Schwartz awareness tier. Each variant follows the 22-word shape and explores a different emphasis (outcome / tradeoff / ICP). Loaded by the main evp skill when the user wants to craft EVPs for a specific tier.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
evp-craft
license
MIT
description
Generate 3 EVP variants for a single Schwartz awareness tier. Each variant follows the 22-word shape and explores a different emphasis (outcome / tradeoff / ICP). Loaded by the main evp skill when the user wants to craft EVPs for a specific tier.
allowed-tools
Read Write - Grep
user-invocable
false

02 资源文件 1

03 SKILL.md 正文

EVP Craft — sub-skill

Generates 3 EVP variants for a specific awareness tier.

Activation

Loaded by evp on:

  • "Write an EVP for <tier>"
  • "EVP for solution-aware prospects"
  • "Tier 3 EVP"

Workflow

1. Lock the awareness tier

Ask the user which Schwartz tier (1-5). If they don't know, walk them through the 5-tier table from ../../evp/SKILL.md and ask: "Which describes your audience right now?"

Most B2B buyers are in Tiers 2-4. If the user says "Tier 5," push back — that's product-team thinking, not buyer-where-they-are thinking.

2. Capture the inputs

Required:

  • icp — specific ICP segment
  • psp_pain — pain in the prospect's vocabulary (from claude-psp)
  • outcome — specific result you deliver
  • tradeoff — obvious tradeoff you spare them
  • proof (optional) — case study / metric backing it

If PSP is missing, suggest the user run claude-psp first. EVPs without a PSP are guesses.

3. Generate 3 variants

Each variant uses the shape but with different emphasis:

Variant A — outcome-led

"For <ICP>, in <pain>, we're the <one team> that does <SPECIFIC OUTCOME> without <tradeoff>."

The outcome carries the line. Use when the outcome is differentiated and concrete (e.g., "ships 14 qualified meetings in 30 days").

Variant B — tradeoff-led

"For <ICP>, in <pain>, we're the team that hits <outcome> WITHOUT <SPECIFIC TRADEOFF>."

The tradeoff carries the line. Use when the tradeoff is the elephant-in-the-room reason the audience hesitates (e.g., "without hiring 2 more SDRs" or "without sacrificing self-serve").

Variant C — ICP-led

"<SPECIFIC ICP> in <pain> use us when they want <outcome> without <tradeoff>."

The ICP carries the line. Use when the audience is hyper-niche and you want immediate exclusion-by-segment (signals fit fast).

4. Validate each variant

Run the self-check:

Check Pass criterion
Word count ≤22
Outcome specificity A concrete noun + metric, not a verb like "improve"
Tradeoff specificity A concrete thing they'd otherwise have to give up
ICP named Segment is specific enough to exclude wrong-fit
Pain vocabulary Uses their words from the PSP, not category jargon
Tier-appropriate Matches the awareness tier (no Tier-5 line for a Tier-2 audience)

5. Output

# EVP — <ICP> · Tier <N>: <tier name>

**Pain anchor:** <PSP pain in their language>

## Variant A — outcome-led
"<22-word line>"

## Variant B — tradeoff-led
"<22-word line>"

## Variant C — ICP-led
"<22-word line>"

## Recommended primary
<A / B / C> — <one-sentence rationale>

## Where this fits
- Cold email line 3 (works on Tier 2-4 audiences)
- Hero copy (Tier <N> only — calibrate per page)
- Pricing-page tagline (Tier 4)
- Sales call opener (calibrate to where prospect is)

## Proof to back it
<Case study / metric / social proof aligned to this tier>

6. Surgical critique mode

If user pastes an existing EVP for critique, return:

Original: "<their EVP>"
Word count: <N>
Tier-fit: <which tier this actually lands on>

Issues:
  - <issue 1>
  - <issue 2>

Rewrite (same voice):
"<rewritten>"
Rationale: <one sentence>

References

  • ../../evp/SKILL.md — the framework
  • The EVP course in The Compounding Engine:

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6