[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBVNABX2Y87ZQZKF5WCDJD":3,"skill-same:01M6MBVNABX2Y87ZQZKF5WCDJD":82},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6MBVNABX2Y87ZQZKF5WCDJD","b2b-reach-engineering",null,"Build B2B reach systems that make a defined market aware of the company through named accounts, real buyers, controlled delivery channels, and first-touch saturation. Use when the right market may not know the company exists, outbound gets little signal, brand awareness is vague, the target market is too broad, or the team needs a concrete account list and reach plan.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-reach-engineering\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"engineering","b2b reach engineering","b2b","when","code","signal","company","account list","vague","make","touch","outbound","delivery","Market","saturation","use","sales","list","brand","marketing","plan","team","awareness","2026-11-10 10:12:30",false,"---\nname: b2b-reach-engineering\ndescription: Build B2B reach systems that make a defined market aware of the company through named accounts, real buyers, controlled delivery channels, and first-touch saturation. Use when the right market may not know the company exists, outbound gets little signal, brand awareness is vague, the target market is too broad, or the team needs a concrete account list and reach plan.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: B2B Reach Engineering\n  category: Marketing\n  tags: b2b-sales,sales,outbound,reach,account-based-marketing\n---\n\n# B2B Reach Engineering\n\nUse this skill when obscurity is the sales constraint. The goal is to turn a\nvague market into a reachable list of companies and buyers, then plan deliberate\nfirst-touch coverage before optimizing conversion.\n\n## Source Traceability\n\nPrimary source: Unf*ck Your Sales by Jakob Greenfeld, especially the \"Reach\",\n\"Diagnostics\", \"The Rejection Fallacy\", \"The TAM Fallacy\", \"The Precision\nFallacy\", \"The First-Touch Law\", and \"Engineering Reach\" sections.\n\n## Diagnostic Signals\n\nReach is likely the constraint when:\n\n- The company has a good offer but too few relevant buyers know it exists.\n- The team interprets silence as rejection before confirming actual market\n  exposure.\n- Targeting is either over-narrow and hesitant or too broad and noisy.\n- The team talks about a huge TAM but cannot name the specific companies and\n  people who must know the company.\n- Optimization is focused on subject lines, funnels, or conversion before the\n  first pass through the target market is complete.\n\n## Workflow\n\n### 1. Extract Non-Negotiables\n\nUse evidence from closed deals, serious opportunities, and competitor wins.\nIdentify the minimum criteria that must be true for a deal to be plausible.\n\nCapture:\n\n- Company type, size, geography, system, regulation, or trigger.\n- Buyer role or owner of the pain.\n- Pain intensity and ability to act.\n- Disqualifiers that make a deal unrealistic.\n\n### 2. Build The Reach List\n\nConvert the target market into named accounts:\n\n- List only companies that match the non-negotiables.\n- Name the 1-3 humans at each account who feel the pain or can act on it.\n- Keep the list concrete enough to contact and measure.\n- Treat broad TAM language as a warning sign.\n\n### 3. Choose Controlled Delivery Channels\n\nPrefer channels where delivery can be proven or closely estimated:\n\n- Cold email to named buyers.\n- Manual DMs.\n- Calls.\n- Account-based ads against the list.\n- Warm intros when available.\n\nAvoid waiting for broad brand awareness, generic posting, or black-box targeting\nwhen reach coverage is the constraint.\n\n### 4. Saturate Before Optimizing\n\nDo not judge messaging, conversion, or sales quality until every qualified buyer\non the list has had at least one real exposure.\n\nTrack:\n\n- Accounts identified.\n- Buyers identified.\n- First touches delivered.\n- Delivery or exposure rate.\n- Replies or second-step signals, as secondary metrics.\n\n## Output Format\n\n```markdown\n# B2B Reach Plan\n\n## Non-Negotiables\n- Must-have account criteria:\n- Must-have buyer criteria:\n- Disqualifiers:\n\n## Target List Plan\n| Segment | Account Criteria | Buyer Roles | Estimated Accounts | Source |\n|---------|------------------|-------------|--------------------|--------|\n\n## Channel Plan\n| Channel | Why It Controls Delivery | First-Touch Action | Coverage Metric |\n|---------|--------------------------|--------------------|-----------------|\n\n## Saturation Target\n- Accounts:\n- Buyers:\n- First-touch deadline:\n- Success signal:\n```\n\n## Quality Bar\n\n- Do not call silence rejection until exposure has been proven.\n- Do not recommend broad awareness plays when named-buyer reach is possible.\n- Do not over-segment before the first pass is complete.\n- Do not blast unqualified lists and call it reach.\n- Make coverage measurable before discussing optimization.\n","# B2B Reach Engineering\n\nUse this skill when obscurity is the sales constraint. The goal is to turn a\nvague market into a reachable list of companies and buyers, then plan deliberate\nfirst-touch coverage before optimizing conversion.\n\n## Source Traceability\n\nPrimary source: Unf*ck Your Sales by Jakob Greenfeld, especially the \"Reach\",\n\"Diagnostics\", \"The Rejection Fallacy\", \"The TAM Fallacy\", \"The Precision\nFallacy\", \"The First-Touch Law\", and \"Engineering Reach\" sections.\n\n## Diagnostic Signals\n\nReach is likely the constraint when:\n\n- The company has a good offer but too few relevant buyers know it exists.\n- The team interprets silence as rejection before confirming actual market\n  exposure.\n- Targeting is either over-narrow and hesitant or too broad and noisy.\n- The team talks about a huge TAM but cannot name the specific companies and\n  people who must know the company.\n- Optimization is focused on subject lines, funnels, or conversion before the\n  first pass through the target market is complete.\n\n## Workflow\n\n### 1. Extract Non-Negotiables\n\nUse evidence from closed deals, serious opportunities, and competitor wins.\nIdentify the minimum criteria that must be true for a deal to be plausible.\n\nCapture:\n\n- Company type, size, geography, system, regulation, or trigger.\n- Buyer role or owner of the pain.\n- Pain intensity and ability to act.\n- Disqualifiers that make a deal unrealistic.\n\n### 2. Build The Reach List\n\nConvert the target market into named accounts:\n\n- List only companies that match the non-negotiables.\n- Name the 1-3 humans at each account who feel the pain or can act on it.\n- Keep the list concrete enough to contact and measure.\n- Treat broad TAM language as a warning sign.\n\n### 3. Choose Controlled Delivery Channels\n\nPrefer channels where delivery can be proven or closely estimated:\n\n- Cold email to named buyers.\n- Manual DMs.\n- Calls.\n- Account-based ads against the list.\n- Warm intros when available.\n\nAvoid waiting for broad brand awareness, generic posting, or black-box targeting\nwhen reach coverage is the constraint.\n\n### 4. Saturate Before Optimizing\n\nDo not judge messaging, conversion, or sales quality until every qualified buyer\non the list has had at least one real exposure.\n\nTrack:\n\n- Accounts identified.\n- Buyers identified.\n- First touches delivered.\n- Delivery or exposure rate.\n- Replies or second-step signals, as secondary metrics.\n\n## Output Format\n\n```markdown\n# B2B Reach Plan\n\n## Non-Negotiables\n- Must-have account criteria:\n- Must-have buyer criteria:\n- Disqualifiers:\n\n## Target List Plan\n| Segment | Account Criteria | Buyer Roles | Estimated Accounts | Source |\n|---------|------------------|-------------|--------------------|--------|\n\n## Channel Plan\n| Channel | Why It Controls Delivery | First-Touch Action | Coverage Metric |\n|---------|--------------------------|--------------------|-----------------|\n\n## Saturation Target\n- Accounts:\n- Buyers:\n- First-touch deadline:\n- Success signal:\n```\n\n## Quality Bar\n\n- Do not call silence rejection until exposure has been proven.\n- Do not recommend broad awareness plays when named-buyer reach is possible.\n- Do not over-segment before the first pass is complete.\n- Do not blast unqualified lists and call it reach.\n- Make coverage measurable before discussing optimization.\n",{"name":5,"license":15,"metadata":52,"description":7,"compatibility":57},{"tags":53,"version":54,"category":55,"displayName":56},"b2b-sales,sales,outbound,reach,account-based-marketing","0.1.0","Marketing","B2B Reach Engineering","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-reach-engineering",490,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 02:12:02",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-reach-engineering",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-reach-engineering",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-reach-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-reach-engineering\u002FSKILL.md",true,[],[83,92,99,106,132,157],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":87,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":91},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":91},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":47},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[113,114,115,116,117,118,119,120,121,122,123,27,124,125,126,127,128,129,130,131],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":47},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[139,140,141,127,142,143,144,145,146,147,148,149,150,151,118,152,153,154,155,156],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":170,"publishedAt":47},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[163,166,167],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[159,171,172,173,174,175,176,153,177,119,178,179,180,181,27,182,183,184,185,186],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]