[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76GS82CKJ05EDQ0T1R50C63":3,"skill-same:01M76GS82CKJ05EDQ0T1R50C63":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M76GS82CKJ05EDQ0T1R50C63","evp-onboarding",null,"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.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fevp-onboarding\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: evp-onboarding\ndescription: 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.\nuser-invocable: false\nallowed-tools: Read Write\n  - Grep\nlicense: MIT\n\n---\n\n# EVP Onboarding — first-run setup\n\n10 minutes of setup that makes every downstream EVP differentiated\ninstead of generic.\n\n## Activation\n\nLoaded automatically by `evp` orchestrator when `brand-config.json`\nor `SOUL.md` is missing.\n\nAlso user-invocable: \"Set up EVP brand config\", \"EVP onboarding\".\n\n## Workflow\n\n### Step 1 — ICP + PSP carry-forward\n\n```\nQuick check — do you already have a PSP?\n\nIf yes (claude-psp is installed and PSP doc exists): I'll pull ICP + pain + vocabulary from there.\nIf no: Install cmj-hub\u002Fclaude-psp first. EVP without a PSP is a guess.\n```\n\n### Step 2 — Primary outreach tier\n\n```\nWhere is YOUR buyer on the Schwartz tier ladder when they meet you?\n\nMost B2B buyers live in Tiers 2-4. Pick the most common one for your outreach:\n\n  Tier 1 (unaware)         — you have to reveal the pain first\n  Tier 2 (problem-aware)   — they know the pain, no solutions evaluated\n  Tier 3 (solution-aware)  — they're comparing categories (in-house \u002F agency \u002F tool)\n  Tier 4 (product-aware)   — comparing specific vendors\n  Tier 5 (most aware)      — ready to buy\n\nIf you don't know, default to Tier 3 — most outbound campaigns target\nthat tier.\n```\n\nSave to `brand-config.primary_outreach_tier`.\n\n### Step 3 — Outcomes-I-will-claim list\n\n```\nWhat specific outcomes are you willing to claim in writing?\n\nEach outcome needs:\n1. A specific noun (not a verb — \"14 SQLs\", not \"more pipeline\")\n2. A specific timeframe (in 30 days, per month, per quarter)\n3. A proof point you can back it with\n\nExamples of GOOD outcomes:\n  \"14+ SQLs per month\"\n  \"Targeted-outbound CPM under $700\"\n  \"First positive reply within 7 days\"\n\nExamples of BAD outcomes (refuse to claim):\n  \"Better demand-gen\"\n  \"Improved efficiency\"\n  \"Best-in-class outreach\"\n\nGive me 3-5 outcomes you're willing to claim. These constrain every\ndownstream EVP variant.\n```\n\nSave to `SOUL.md` (outcomes-I-will-claim list) + `brand-config.evp_drafts.tier_3.outcome`.\n\n### Step 4 — Tradeoffs you name\n\n```\nFor each outcome, what's the obvious tradeoff you spare them from?\n\nThe EVP shape is \"\u003Coutcome> without \u003Ctradeoff>\". The tradeoff carries\nthe line — name something they'd otherwise have to give up.\n\nExamples:\n  \"without hiring 2 more SDRs\"\n  \"without breaking the PLG self-serve motion\"\n  \"without paying agency retainer rates\"\n```\n\nSave to `brand-config.evp_drafts.tier_3.tradeoff` + `SOUL.md`.\n\n### Step 5 — Proofs reservoir\n\n```\nGive me 3-5 concrete proofs you can cite. Each is anonymized but\nspecific.\n\nExamples:\n  \"Series-B SaaS hit 14 SQLs in 30 days from a PSP rewrite — case study at \u002Fcase-studies\u002FX\"\n  \"Bootstrapped agency went 2% → 11% reply rate by killing demographic targeting\"\n\nThese become the proof reservoir — EVP variants pull from here, not\nfabricated case studies.\n```\n\nSave to `SOUL.md`.\n\n### Step 6 — Competitors (for Tier 4 EVPs)\n\n```\nFor Tier 4 EVPs, you need to name competitors and your delta on a\nspecific axis.\n\nTop 2-3 competitors + the axis you beat them on:\n  1. Generic outbound agency — CPM efficiency\n  2. AI SDR vendor — reply quality vs volume\n  3. In-house SDR build — time-to-payback\n```\n\nSave to `brand-config.competitors`.\n\n### Step 7 — Voice (SOUL.md)\n\n```\nPer-tier voice settings:\n\nTier 2 (problem-aware) — tone: ?\nTier 3 (solution-aware) — tone: ?\nTier 4 (product-aware) — tone: ?\n\nWon't-write list:\n  • \u003Ce.g. industry guarantees you don't actually back>\n  • \u003Ce.g. competitor names you won't reference by full brand>\n```\n\nSave to `SOUL.md`.\n\n### Step 8 — Write the files + smoke test\n\nWrite `brand-config.json` + `SOUL.md` at project root. Show:\n\n```\n✓ brand-config.json — Tier 3 primary + 3 outcomes + 3 competitors\n✓ SOUL.md — outcomes-will-claim list + 4 proofs + tier voice\n\nTry a smoke test:\n> Generate a Tier 3 EVP for my ICP\n\nThe output will use:\n- Your outcomes-will-claim list (refuses outside it)\n- Your tradeoffs\n- Proofs from your reservoir\n```\n\n## References\n\n- `..\u002F..\u002Fbrand-config.example.json`\n- `..\u002F..\u002FSOUL.md`\n- `..\u002F..\u002FAGENTS.md`\n- Sister skills: `evp-craft`, `evp-brief`\n","# EVP Onboarding — first-run setup\n\n10 minutes of setup that makes every downstream EVP differentiated\ninstead of generic.\n\n## Activation\n\nLoaded automatically by `evp` orchestrator when `brand-config.json`\nor `SOUL.md` is missing.\n\nAlso user-invocable: \"Set up EVP brand config\", \"EVP onboarding\".\n\n## Workflow\n\n### Step 1 — ICP + PSP carry-forward\n\n```\nQuick check — do you already have a PSP?\n\nIf yes (claude-psp is installed and PSP doc exists): I'll pull ICP + pain + vocabulary from there.\nIf no: Install cmj-hub\u002Fclaude-psp first. EVP without a PSP is a guess.\n```\n\n### Step 2 — Primary outreach tier\n\n```\nWhere is YOUR buyer on the Schwartz tier ladder when they meet you?\n\nMost B2B buyers live in Tiers 2-4. Pick the most common one for your outreach:\n\n  Tier 1 (unaware)         — you have to reveal the pain first\n  Tier 2 (problem-aware)   — they know the pain, no solutions evaluated\n  Tier 3 (solution-aware)  — they're comparing categories (in-house \u002F agency \u002F tool)\n  Tier 4 (product-aware)   — comparing specific vendors\n  Tier 5 (most aware)      — ready to buy\n\nIf you don't know, default to Tier 3 — most outbound campaigns target\nthat tier.\n```\n\nSave to `brand-config.primary_outreach_tier`.\n\n### Step 3 — Outcomes-I-will-claim list\n\n```\nWhat specific outcomes are you willing to claim in writing?\n\nEach outcome needs:\n1. A specific noun (not a verb — \"14 SQLs\", not \"more pipeline\")\n2. A specific timeframe (in 30 days, per month, per quarter)\n3. A proof point you can back it with\n\nExamples of GOOD outcomes:\n  \"14+ SQLs per month\"\n  \"Targeted-outbound CPM under $700\"\n  \"First positive reply within 7 days\"\n\nExamples of BAD outcomes (refuse to claim):\n  \"Better demand-gen\"\n  \"Improved efficiency\"\n  \"Best-in-class outreach\"\n\nGive me 3-5 outcomes you're willing to claim. These constrain every\ndownstream EVP variant.\n```\n\nSave to `SOUL.md` (outcomes-I-will-claim list) + `brand-config.evp_drafts.tier_3.outcome`.\n\n### Step 4 — Tradeoffs you name\n\n```\nFor each outcome, what's the obvious tradeoff you spare them from?\n\nThe EVP shape is \"\u003Coutcome> without \u003Ctradeoff>\". The tradeoff carries\nthe line — name something they'd otherwise have to give up.\n\nExamples:\n  \"without hiring 2 more SDRs\"\n  \"without breaking the PLG self-serve motion\"\n  \"without paying agency retainer rates\"\n```\n\nSave to `brand-config.evp_drafts.tier_3.tradeoff` + `SOUL.md`.\n\n### Step 5 — Proofs reservoir\n\n```\nGive me 3-5 concrete proofs you can cite. Each is anonymized but\nspecific.\n\nExamples:\n  \"Series-B SaaS hit 14 SQLs in 30 days from a PSP rewrite — case study at \u002Fcase-studies\u002FX\"\n  \"Bootstrapped agency went 2% → 11% reply rate by killing demographic targeting\"\n\nThese become the proof reservoir — EVP variants pull from here, not\nfabricated case studies.\n```\n\nSave to `SOUL.md`.\n\n### Step 6 — Competitors (for Tier 4 EVPs)\n\n```\nFor Tier 4 EVPs, you need to name competitors and your delta on a\nspecific axis.\n\nTop 2-3 competitors + the axis you beat them on:\n  1. Generic outbound agency — CPM efficiency\n  2. AI SDR vendor — reply quality vs volume\n  3. In-house SDR build — time-to-payback\n```\n\nSave to `brand-config.competitors`.\n\n### Step 7 — Voice (SOUL.md)\n\n```\nPer-tier voice settings:\n\nTier 2 (problem-aware) — tone: ?\nTier 3 (solution-aware) — tone: ?\nTier 4 (product-aware) — tone: ?\n\nWon't-write list:\n  • \u003Ce.g. industry guarantees you don't actually back>\n  • \u003Ce.g. competitor names you won't reference by full brand>\n```\n\nSave to `SOUL.md`.\n\n### Step 8 — Write the files + smoke test\n\nWrite `brand-config.json` + `SOUL.md` at project root. Show:\n\n```\n✓ brand-config.json — Tier 3 primary + 3 outcomes + 3 competitors\n✓ SOUL.md — outcomes-will-claim list + 4 proofs + tier voice\n\nTry a smoke test:\n> Generate a Tier 3 EVP for my ICP\n\nThe output will use:\n- Your outcomes-will-claim list (refuses outside it)\n- Your tradeoffs\n- Proofs from your reservoir\n```\n\n## References\n\n- `..\u002F..\u002Fbrand-config.example.json`\n- `..\u002F..\u002FSOUL.md`\n- `..\u002F..\u002FAGENTS.md`\n- Sister skills: `evp-craft`, `evp-brief`\n",{"name":5,"license":15,"description":7,"allowed-tools":24,"user-invocable":20},"Read Write - Grep","master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fevp-onboarding",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill evp-onboarding",{"tool":41,"command":42},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill evp-onboarding",{"tool":44,"command":45},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill evp-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fevp-onboarding\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"skill-report.json","REFERENCE","参考文档",34082,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fevp-onboarding\u002Fskill-report.json",[56,64,71,78,85,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":63},"01M7DXW9N826PKXK174PVW3038","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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":63},"01M7DXVHSTWDV65475QEQ915M7","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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":63},"01M7DXV8X2D7B3VTD4HHYYHTGR","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\u002Frevnu-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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":63},"01M7DXV0DGJ1G0A60PAHC6J3C5","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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":63},"01M7DXTSPMGT9D6DSS0HP9BSTA","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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":63},"01M7DXSZHCVTRS620GC3S97JZV","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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]