[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBW1C1FJ4BMZ7D16FRHD68":3,"skill-same:01M6MBW1C1FJ4BMZ7D16FRHD68":80},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MBW1C1FJ4BMZ7D16FRHD68","b2b-sales-constraint-diagnosis",null,"Diagnose the single B2B sales constraint currently limiting pipeline or revenue and route to the right repair workflow. Use when sales feels stuck, pipeline is weak, leads ghost, outbound is not working, conversion is unclear, or the team is debating whether to fix reach, messaging, follow-up timing, or trust.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-sales-constraint-diagnosis\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],"b2b sales constraint diagnosis","constraint","sales","diagnosis","b2b","trust","when","follow-up","leads","revenue","outbound","route","workflow","conversion","up","fix","marketing","team","pipeline","messaging","code","2026-11-10 10:12:30",false,"---\nname: b2b-sales-constraint-diagnosis\ndescription: Diagnose the single B2B sales constraint currently limiting pipeline or revenue and route to the right repair workflow. Use when sales feels stuck, pipeline is weak, leads ghost, outbound is not working, conversion is unclear, or the team is debating whether to fix reach, messaging, follow-up timing, or trust.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: B2B Sales Constraint Diagnosis\n  category: Marketing\n  tags: b2b-sales,sales,pipeline,diagnosis,constraints\n---\n\n# B2B Sales Constraint Diagnosis\n\nUse this skill to find the sales bottleneck before recommending tactics. The\ngoal is to identify the one constraint that is throttling the current sales\nsystem, then route work to the most relevant repair skill.\n\n## Source Traceability\n\nPrimary source: Unf*ck Your Sales by Jakob Greenfeld. Authoring notes used the\nsections \"Our Map, Lens, and Compass\", \"The One Sentence Sales Course\",\n\"Invert, Always Invert!\", \"The Theory of Constraints\", and \"Putting It\nTogether\".\n\n## Constraint Model\n\nDiagnose in this order:\n\n1. **Reach** - the right people do not know the company exists.\n2. **Resonance** - the right people see the company but do not connect it to a\n   painful problem, concrete outcome, and credible mechanism.\n3. **Timing** - buyers know and understand the company, but the company is not\n   present when pain becomes urgent.\n4. **Trust** - qualified buyers engage but do not feel enough certainty or risk\n   reduction to take action.\n\nOnly one constraint should be treated as primary at a time. Everything else is\nsecondary until the primary constraint is fixed or disproven.\n\n## Diagnostic Workflow\n\n1. Restate the current sales symptom and stage:\n   - No awareness or no replies.\n   - Replies but poor recall or weak understanding.\n   - Interest but no urgency or inconsistent timing.\n   - Qualified calls, proposals, or trials that stall or ghost.\n2. Check for basic evidence before diagnosing:\n   - Target segment or account list.\n   - Recent outreach or visibility activity.\n   - Message or offer being used.\n   - Lead, meeting, close, and ghosting data.\n3. Run the constraint checks:\n   - **Reach**: Have enough named buyers in the target market been reached at\n     least once?\n   - **Resonance**: Can target buyers explain what the company does, who it is\n     for, and what problem it solves?\n   - **Timing**: Has every viable buyer seen or heard from the company in the\n     last 4-6 weeks?\n   - **Trust**: Do qualified buyers close at an acceptable rate once they engage?\n4. Pick the weakest proven constraint. If evidence is missing, recommend the\n   smallest diagnostic test rather than guessing.\n5. Route next work:\n   - Reach problem: use `b2b-reach-engineering`.\n   - Resonance problem: use `b2b-resonance-audit`.\n   - Timing problem: use `b2b-timing-engine`.\n   - Trust problem: use `b2b-trust-engineering`.\n\n## Output Format\n\n```markdown\n# B2B Sales Constraint Diagnosis\n\n## Current Symptom\n- Segment:\n- Offer:\n- Sales motion:\n- Evidence reviewed:\n\n## Constraint Assessment\n| Constraint | Evidence | Pass\u002FConcern | Confidence |\n|------------|----------|--------------|------------|\n| Reach | | | |\n| Resonance | | | |\n| Timing | | | |\n| Trust | | | |\n\n## Primary Constraint\n[Name the one constraint and why it is most likely throttling growth.]\n\n## Next Diagnostic Or Repair\n- Use skill:\n- First action:\n- Success signal:\n- Do not optimize yet:\n```\n\n## Quality Bar\n\n- Do not prescribe tactics before naming the constraint.\n- Do not optimize messaging, follow-up, funnels, or close tactics if the market\n  has not actually been reached.\n- Do not diagnose rejection when the market may simply be unaware.\n- Do not work on multiple bottlenecks at once unless the user explicitly wants a\n  broad audit.\n- Treat missing evidence as a diagnostic task, not permission to guess.\n","# B2B Sales Constraint Diagnosis\n\nUse this skill to find the sales bottleneck before recommending tactics. The\ngoal is to identify the one constraint that is throttling the current sales\nsystem, then route work to the most relevant repair skill.\n\n## Source Traceability\n\nPrimary source: Unf*ck Your Sales by Jakob Greenfeld. Authoring notes used the\nsections \"Our Map, Lens, and Compass\", \"The One Sentence Sales Course\",\n\"Invert, Always Invert!\", \"The Theory of Constraints\", and \"Putting It\nTogether\".\n\n## Constraint Model\n\nDiagnose in this order:\n\n1. **Reach** - the right people do not know the company exists.\n2. **Resonance** - the right people see the company but do not connect it to a\n   painful problem, concrete outcome, and credible mechanism.\n3. **Timing** - buyers know and understand the company, but the company is not\n   present when pain becomes urgent.\n4. **Trust** - qualified buyers engage but do not feel enough certainty or risk\n   reduction to take action.\n\nOnly one constraint should be treated as primary at a time. Everything else is\nsecondary until the primary constraint is fixed or disproven.\n\n## Diagnostic Workflow\n\n1. Restate the current sales symptom and stage:\n   - No awareness or no replies.\n   - Replies but poor recall or weak understanding.\n   - Interest but no urgency or inconsistent timing.\n   - Qualified calls, proposals, or trials that stall or ghost.\n2. Check for basic evidence before diagnosing:\n   - Target segment or account list.\n   - Recent outreach or visibility activity.\n   - Message or offer being used.\n   - Lead, meeting, close, and ghosting data.\n3. Run the constraint checks:\n   - **Reach**: Have enough named buyers in the target market been reached at\n     least once?\n   - **Resonance**: Can target buyers explain what the company does, who it is\n     for, and what problem it solves?\n   - **Timing**: Has every viable buyer seen or heard from the company in the\n     last 4-6 weeks?\n   - **Trust**: Do qualified buyers close at an acceptable rate once they engage?\n4. Pick the weakest proven constraint. If evidence is missing, recommend the\n   smallest diagnostic test rather than guessing.\n5. Route next work:\n   - Reach problem: use `b2b-reach-engineering`.\n   - Resonance problem: use `b2b-resonance-audit`.\n   - Timing problem: use `b2b-timing-engine`.\n   - Trust problem: use `b2b-trust-engineering`.\n\n## Output Format\n\n```markdown\n# B2B Sales Constraint Diagnosis\n\n## Current Symptom\n- Segment:\n- Offer:\n- Sales motion:\n- Evidence reviewed:\n\n## Constraint Assessment\n| Constraint | Evidence | Pass\u002FConcern | Confidence |\n|------------|----------|--------------|------------|\n| Reach | | | |\n| Resonance | | | |\n| Timing | | | |\n| Trust | | | |\n\n## Primary Constraint\n[Name the one constraint and why it is most likely throttling growth.]\n\n## Next Diagnostic Or Repair\n- Use skill:\n- First action:\n- Success signal:\n- Do not optimize yet:\n```\n\n## Quality Bar\n\n- Do not prescribe tactics before naming the constraint.\n- Do not optimize messaging, follow-up, funnels, or close tactics if the market\n  has not actually been reached.\n- Do not diagnose rejection when the market may simply be unaware.\n- Do not work on multiple bottlenecks at once unless the user explicitly wants a\n  broad audit.\n- Treat missing evidence as a diagnostic task, not permission to guess.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":55},{"tags":51,"version":52,"category":53,"displayName":54},"b2b-sales,sales,pipeline,diagnosis,constraints","0.1.0","Marketing","B2B Sales Constraint Diagnosis","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-sales-constraint-diagnosis",491,"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 14:06:13",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-sales-constraint-diagnosis",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-sales-constraint-diagnosis",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-sales-constraint-diagnosis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-sales-constraint-diagnosis\u002FSKILL.md",true,[],[81,90,98,106,114,122],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\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":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]