[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SJ52GKT3YAJMB4NJDVFK7":3,"skill-same:01M77SJ52GKT3YAJMB4NJDVFK7":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SJ52GKT3YAJMB4NJDVFK7","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.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fb2b-sales-constraint-diagnosis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"b2b-sales,sales,pipeline,diagnosis,constraints","0.1.0","Marketing","B2B Sales Constraint Diagnosis","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fb2b-sales-constraint-diagnosis","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill b2b-sales-constraint-diagnosis",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill b2b-sales-constraint-diagnosis",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill b2b-sales-constraint-diagnosis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fb2b-sales-constraint-diagnosis\u002FSKILL.md",true,[],[50,59,66,74,81,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":54,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":54,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]