[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76JS4PX4295G3ZS3XK0THZA":3,"skill-same:01M76JS4PX4295G3ZS3XK0THZA":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},"01M76JS4PX4295G3ZS3XK0THZA","psp-onboarding",null,"First-run interactive setup for the PSP skill pack. Walks the operator through brand-config.json (ICP precision, exclusion criteria, signal sources) and SOUL.md (buyer vocabulary, stories, the 11am-Tuesday moment) in ~15 minutes. Refuses to let the operator skip — generic PSP output is worse than no PSP. Loaded automatically by the main psp skill 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\u002Fpsp-onboarding\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: psp-onboarding\ndescription: First-run interactive setup for the PSP skill pack. Walks the operator through brand-config.json (ICP precision, exclusion criteria, signal sources) and SOUL.md (buyer vocabulary, stories, the 11am-Tuesday moment) in ~15 minutes. Refuses to let the operator skip — generic PSP output is worse than no PSP. Loaded automatically by the main psp skill when brand-config.json or SOUL.md is missing.\nuser-invocable: false\nallowed-tools: Read Write\n  - Grep\nlicense: MIT\n\n---\n\n# PSP Onboarding — first-run setup\n\nWalks the operator through ~15 minutes of setup that makes every\ndownstream PSP 10x more useful than generic framework prose.\n\n## Activation\n\nLoaded automatically by the `psp` orchestrator when `brand-config.json`\nor `SOUL.md` is missing from the project root.\n\nAlso user-invocable: \"Set up PSP brand config\", \"PSP onboarding\", \"Configure PSP\".\n\n## Why this exists\n\nA generic PSP that says \"Series-B SaaS feels pipeline pressure\" is\nworse than no PSP — it produces outreach that everyone else is also\nproducing. The 5-component PSP framework only generates real\ndifferentiation when paired with:\n\n- **Your ICP precision** (segment, exclusion, motion)\n- **Your buyer's actual vocabulary** (sourced from real writing, not\n  invented)\n- **Your stories** (signal-to-pain mappings you've seen succeed or\n  fail before)\n- **Your won't-chase boundaries**\n\n## Workflow\n\n### Step 0 — Detect prior state\n\nCheck for existing `brand-config.json` + `SOUL.md`. If both exist, ask:\n\"Refresh, or skip?\" If one exists, fill the gap.\n\n### Step 1 — ICP precision\n\n```\nFirst, ICP. Be specific — \"B2B SaaS\" is too broad.\n\nTell me in one batch:\n1. The 1-sentence segment (stage \u002F size \u002F motion \u002F region)\n2. The size range ($M ARR)\n3. The motion (PLG \u002F sales-led \u002F hybrid)\n4. The 3-5 exclusion criteria (who you don't sell to)\n\nIf your ICP is fuzzy, that's a finding — outreach against a fuzzy ICP\nwill be fuzzy. We can use placeholders for now and flag them for refresh\nafter 100 sends.\n```\n\nSave to `brand-config.icp`.\n\n### Step 2 — Primary PSP draft\n\n```\nNow your primary PSP. Five components:\n\n1. SIGNAL — what's a public, recent, verifiable thing your buyer does\n   that implies the pain? (job post, funding round, leadership change,\n   product launch, pricing change)\n2. PAIN — what's the felt operational reality at 11am Tuesday when\n   that signal is present? In their language, not yours.\n3. TIMING TRIGGER — which 90-day window makes the pain acute now:\n   new-exec \u002F budget-cycle \u002F obvious-failure?\n4. FELT-PAIN ROLE — who at the buyer feels it most? (Often a layer\n   below the buying authority.)\n5. VOCABULARY — 4-8 phrases the buyer uses in private about this. If\n   you don't know yet, that's step 3.\n```\n\nSave to `brand-config.psp_drafts.primary`.\n\n### Step 3 — Vocabulary mining\n\n```\nIf you don't have 4-8 buyer phrases yet, let's mine them.\n\nPoint me at any of these sources for the buyer segment:\n- 3-5 of their public LinkedIn posts\n- 1-2 podcast appearances\n- 2-3 of their hiring job posts (job posts reveal pain language verbatim)\n- 1-2 conference talks \u002F panel appearances\n- Their public AMA responses\n\nI'll extract candidate phrases — you confirm which ones land.\n```\n\nIf WebFetch is available, the skill can pull + extract directly. If\nnot, instruct the operator to paste content and run extraction.\n\n### Step 4 — Signal sources (operations)\n\n```\nWhere will you hunt these signals? (Mark all that apply.)\n\n1. LinkedIn job search (daily — manual or via Phantombuster)\n2. Crunchbase \u002F news APIs (weekly)\n3. RSS feeds for specific publications\n4. Podcast feeds for relevant shows\n5. Manual research only\n\nHow often refresh:\n- PSP refresh cadence (default: 90 days)\n- Vocabulary refresh (default: 30 days)\n- Signal freshness window (default: 14 days — older signals drop)\n```\n\nSave to `brand-config.signal_sources` + `brand-config.research_cadence`.\n\n### Step 5 — Stories (SOUL.md)\n\n```\nTell me 3-5 stories that anchor your PSP — times you saw a signal-to-pain\nmapping work or fail.\n\nEach story: 1-2 sentences, anonymized but specific. These become\ncalibration points for the construct skill.\n\nAlso:\n- Your won't-chase boundaries (topics \u002F segments you refuse)\n- The 11am-Tuesday operational moment of your buyer (paint it specific)\n```\n\nSave to `SOUL.md`.\n\n### Step 6 — Write the files\n\nWrite `brand-config.json` + `SOUL.md` at the project root. Show preview:\n\n```\n✓ brand-config.json — ICP + 1 PSP draft + signal sources + cadence\n✓ SOUL.md — 3 stories + vocabulary + 11am-Tuesday moment\n\nTry a quick test:\n> Construct a PSP for \u003Csegment>\n\nThe output will now use:\n- Your ICP precision (not generic \"B2B SaaS\")\n- Your vocabulary (not category jargon)\n- Your stories as calibration\n\nNext step: install `cmj-hub\u002Fclaude-evp` to lock the EVP that speaks\nto this PSP. Then `cmj-hub\u002Fclaude-cold-email` to ship outreach.\n```\n\n### Step 7 — Refresh cadence\n\n```\nPSPs decay. Re-run onboarding when:\n- ICP shifts (new segment \u002F segment cull)\n- Buyer vocabulary evolves\n- Quarterly minimum (90 days)\n\nRe-run: `\u002Fpsp onboarding refresh`\n```\n\n## References\n\n- `..\u002F..\u002Fbrand-config.example.json` — full template\n- `..\u002F..\u002FSOUL.md` — voice template\n- `..\u002F..\u002FAGENTS.md` — behavior rules\n- Sister skills:\n  - `psp-kickoff` — adaptive router that uses these files\n  - `psp-construct` — uses brand + SOUL for actual PSP build\n  - `psp-signal-hunt` — runs against your signal sources\n","# PSP Onboarding — first-run setup\n\nWalks the operator through ~15 minutes of setup that makes every\ndownstream PSP 10x more useful than generic framework prose.\n\n## Activation\n\nLoaded automatically by the `psp` orchestrator when `brand-config.json`\nor `SOUL.md` is missing from the project root.\n\nAlso user-invocable: \"Set up PSP brand config\", \"PSP onboarding\", \"Configure PSP\".\n\n## Why this exists\n\nA generic PSP that says \"Series-B SaaS feels pipeline pressure\" is\nworse than no PSP — it produces outreach that everyone else is also\nproducing. The 5-component PSP framework only generates real\ndifferentiation when paired with:\n\n- **Your ICP precision** (segment, exclusion, motion)\n- **Your buyer's actual vocabulary** (sourced from real writing, not\n  invented)\n- **Your stories** (signal-to-pain mappings you've seen succeed or\n  fail before)\n- **Your won't-chase boundaries**\n\n## Workflow\n\n### Step 0 — Detect prior state\n\nCheck for existing `brand-config.json` + `SOUL.md`. If both exist, ask:\n\"Refresh, or skip?\" If one exists, fill the gap.\n\n### Step 1 — ICP precision\n\n```\nFirst, ICP. Be specific — \"B2B SaaS\" is too broad.\n\nTell me in one batch:\n1. The 1-sentence segment (stage \u002F size \u002F motion \u002F region)\n2. The size range ($M ARR)\n3. The motion (PLG \u002F sales-led \u002F hybrid)\n4. The 3-5 exclusion criteria (who you don't sell to)\n\nIf your ICP is fuzzy, that's a finding — outreach against a fuzzy ICP\nwill be fuzzy. We can use placeholders for now and flag them for refresh\nafter 100 sends.\n```\n\nSave to `brand-config.icp`.\n\n### Step 2 — Primary PSP draft\n\n```\nNow your primary PSP. Five components:\n\n1. SIGNAL — what's a public, recent, verifiable thing your buyer does\n   that implies the pain? (job post, funding round, leadership change,\n   product launch, pricing change)\n2. PAIN — what's the felt operational reality at 11am Tuesday when\n   that signal is present? In their language, not yours.\n3. TIMING TRIGGER — which 90-day window makes the pain acute now:\n   new-exec \u002F budget-cycle \u002F obvious-failure?\n4. FELT-PAIN ROLE — who at the buyer feels it most? (Often a layer\n   below the buying authority.)\n5. VOCABULARY — 4-8 phrases the buyer uses in private about this. If\n   you don't know yet, that's step 3.\n```\n\nSave to `brand-config.psp_drafts.primary`.\n\n### Step 3 — Vocabulary mining\n\n```\nIf you don't have 4-8 buyer phrases yet, let's mine them.\n\nPoint me at any of these sources for the buyer segment:\n- 3-5 of their public LinkedIn posts\n- 1-2 podcast appearances\n- 2-3 of their hiring job posts (job posts reveal pain language verbatim)\n- 1-2 conference talks \u002F panel appearances\n- Their public AMA responses\n\nI'll extract candidate phrases — you confirm which ones land.\n```\n\nIf WebFetch is available, the skill can pull + extract directly. If\nnot, instruct the operator to paste content and run extraction.\n\n### Step 4 — Signal sources (operations)\n\n```\nWhere will you hunt these signals? (Mark all that apply.)\n\n1. LinkedIn job search (daily — manual or via Phantombuster)\n2. Crunchbase \u002F news APIs (weekly)\n3. RSS feeds for specific publications\n4. Podcast feeds for relevant shows\n5. Manual research only\n\nHow often refresh:\n- PSP refresh cadence (default: 90 days)\n- Vocabulary refresh (default: 30 days)\n- Signal freshness window (default: 14 days — older signals drop)\n```\n\nSave to `brand-config.signal_sources` + `brand-config.research_cadence`.\n\n### Step 5 — Stories (SOUL.md)\n\n```\nTell me 3-5 stories that anchor your PSP — times you saw a signal-to-pain\nmapping work or fail.\n\nEach story: 1-2 sentences, anonymized but specific. These become\ncalibration points for the construct skill.\n\nAlso:\n- Your won't-chase boundaries (topics \u002F segments you refuse)\n- The 11am-Tuesday operational moment of your buyer (paint it specific)\n```\n\nSave to `SOUL.md`.\n\n### Step 6 — Write the files\n\nWrite `brand-config.json` + `SOUL.md` at the project root. Show preview:\n\n```\n✓ brand-config.json — ICP + 1 PSP draft + signal sources + cadence\n✓ SOUL.md — 3 stories + vocabulary + 11am-Tuesday moment\n\nTry a quick test:\n> Construct a PSP for \u003Csegment>\n\nThe output will now use:\n- Your ICP precision (not generic \"B2B SaaS\")\n- Your vocabulary (not category jargon)\n- Your stories as calibration\n\nNext step: install `cmj-hub\u002Fclaude-evp` to lock the EVP that speaks\nto this PSP. Then `cmj-hub\u002Fclaude-cold-email` to ship outreach.\n```\n\n### Step 7 — Refresh cadence\n\n```\nPSPs decay. Re-run onboarding when:\n- ICP shifts (new segment \u002F segment cull)\n- Buyer vocabulary evolves\n- Quarterly minimum (90 days)\n\nRe-run: `\u002Fpsp onboarding refresh`\n```\n\n## References\n\n- `..\u002F..\u002Fbrand-config.example.json` — full template\n- `..\u002F..\u002FSOUL.md` — voice template\n- `..\u002F..\u002FAGENTS.md` — behavior rules\n- Sister skills:\n  - `psp-kickoff` — adaptive router that uses these files\n  - `psp-construct` — uses brand + SOUL for actual PSP build\n  - `psp-signal-hunt` — runs against your signal sources\n",{"name":5,"license":15,"description":7,"allowed-tools":24,"user-invocable":20},"Read Write - Grep","master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fpsp-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 psp-onboarding",{"tool":41,"command":42},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill psp-onboarding",{"tool":44,"command":45},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill psp-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fpsp-onboarding\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"skill-report.json","REFERENCE","参考文档",36223,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fpsp-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",[],[]]