[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBWCSBT9J8ESH2E2SEJJHM":3,"skill-same:01M6MBWCSBT9J8ESH2E2SEJJHM":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},"01M6MBWCSBT9J8ESH2E2SEJJHM","b2b-trust-engineering",null,"Engineer B2B buyer trust by reducing perceived risk, stacking relevant proof, simplifying next steps, and designing sales calls to confirm confidence rather than persuade from scratch. Use when qualified buyers take calls, request proposals, start trials, or show interest but then stall, ghost, choose safer incumbents, or hesitate because proof, certainty, process, or risk reversal is weak.","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-trust-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],"engineering","b2b trust engineering","trust","b2b","show","when","request","calls","closing","next steps","relevant","next","but","code","engineer","take","proposals","choose","marketing","risk","start","2026-11-10 10:12:30",false,"---\nname: b2b-trust-engineering\ndescription: Engineer B2B buyer trust by reducing perceived risk, stacking relevant proof, simplifying next steps, and designing sales calls to confirm confidence rather than persuade from scratch. Use when qualified buyers take calls, request proposals, start trials, or show interest but then stall, ghost, choose safer incumbents, or hesitate because proof, certainty, process, or risk reversal is weak.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: B2B Trust Engineering\n  category: Marketing\n  tags: b2b-sales,sales,trust,proof,closing\n---\n\n# B2B Trust Engineering\n\nUse this skill when qualified buyers engage but do not take action. The goal is\nto make the buying decision feel safe by reducing risk, increasing relevant\nproof, and making next steps obvious.\n\n## Source Traceability\n\nPrimary source: Unf*ck Your Sales by Jakob Greenfeld, especially the \"Trust\",\n\"Diagnostics\", \"The Confidence Fallacy\", \"The Persuasion Fallacy\", \"The Best\nOption Fallacy\", \"The 7-11-4 Law\", and \"Engineering Trust\" sections.\n\n## Diagnostic Signals\n\nTrust is likely the constraint when:\n\n- Qualified buyers book calls, request proposals, or start trials but do not\n  close.\n- Prospects say the offer sounds good and then vanish.\n- The buyer appears to need the outcome but still chooses an incumbent or no\n  decision.\n- The pitch relies on confidence, vision, or ROI claims without enough proof.\n- The sales call tries to persuade instead of confirming what the buyer already\n  believes.\n\n## Trust Check\n\nReview the last 50 qualified opportunities where possible:\n\n- How many closed?\n- How many ghosted after meaningful engagement?\n- How many stalled after a proposal or trial?\n- What proof did buyers see before the call?\n- What risks, ambiguities, or next-step friction remained?\n\nIf qualified close rate is weak or ghosting is high after engagement, treat\ntrust as the likely constraint.\n\n## Workflow\n\n### 1. Lead With Relevant Proof\n\nUse proof that matches the buyer's world:\n\n- Case studies tied to the same pain.\n- Testimonials with specifics.\n- Screenshots, dashboards, or before\u002Fafter evidence.\n- Logos or references that reduce perceived risk.\n- Third-party mentions, referrals, podcasts, or credible appearances.\n\n### 2. Remove Hidden Risk\n\nAudit friction:\n\n- Can the buyer understand the offer quickly?\n- Is pricing or scope ambiguous?\n- Are next steps explicit?\n- Is implementation risk addressed?\n- Is the downside named and handled?\n\nAnything ambiguous increases risk.\n\n### 3. Build Layered Familiarity\n\nCreate trust across multiple surfaces before the call:\n\n- One-to-one outreach.\n- Case studies or proof drops.\n- Helpful content.\n- Video or Loom walkthroughs.\n- Social posts or founder presence.\n- Third-party channels where buyers can see independent signals.\n\nUse 7 hours, 11 touchpoints, and 4 platforms as an exposure target, not as a\nrigid law.\n\n### 4. Design The Call To Confirm\n\nAssume serious buyers arrive with a partial preference already formed.\n\nOn the call:\n\n- Reflect the buyer's problem clearly.\n- Map proof to their exact situation.\n- Avoid over-explaining or adding complexity.\n- Make the next step low-risk and obvious.\n- Confirm decision criteria and approval path.\n\n## Output Format\n\n```markdown\n# B2B Trust Plan\n\n## Opportunity Pattern\n- Qualified leads reviewed:\n- Close rate:\n- Ghost\u002Fstall pattern:\n- Main risk signal:\n\n## Proof Stack\n| Buyer Fear | Proof Needed | Existing Asset | Gap |\n|------------|--------------|----------------|-----|\n\n## Risk Removal\n- Offer clarity:\n- Pricing\u002Fscope:\n- Implementation:\n- Next step:\n- Approval path:\n\n## Call Design\n- Problem mirror:\n- Proof to show:\n- Risk to address:\n- Next action:\n```\n\n## Quality Bar\n\n- Do not try to close with confidence when proof is missing.\n- Do not treat buyer hesitation as a persuasion problem before checking risk.\n- Do not overload buyers with detail when simpler proof would reduce risk.\n- Do not ignore approval path, career risk, or incumbent safety.\n- Make \"yes\" feel safer before making the upside sound bigger.\n","# B2B Trust Engineering\n\nUse this skill when qualified buyers engage but do not take action. The goal is\nto make the buying decision feel safe by reducing risk, increasing relevant\nproof, and making next steps obvious.\n\n## Source Traceability\n\nPrimary source: Unf*ck Your Sales by Jakob Greenfeld, especially the \"Trust\",\n\"Diagnostics\", \"The Confidence Fallacy\", \"The Persuasion Fallacy\", \"The Best\nOption Fallacy\", \"The 7-11-4 Law\", and \"Engineering Trust\" sections.\n\n## Diagnostic Signals\n\nTrust is likely the constraint when:\n\n- Qualified buyers book calls, request proposals, or start trials but do not\n  close.\n- Prospects say the offer sounds good and then vanish.\n- The buyer appears to need the outcome but still chooses an incumbent or no\n  decision.\n- The pitch relies on confidence, vision, or ROI claims without enough proof.\n- The sales call tries to persuade instead of confirming what the buyer already\n  believes.\n\n## Trust Check\n\nReview the last 50 qualified opportunities where possible:\n\n- How many closed?\n- How many ghosted after meaningful engagement?\n- How many stalled after a proposal or trial?\n- What proof did buyers see before the call?\n- What risks, ambiguities, or next-step friction remained?\n\nIf qualified close rate is weak or ghosting is high after engagement, treat\ntrust as the likely constraint.\n\n## Workflow\n\n### 1. Lead With Relevant Proof\n\nUse proof that matches the buyer's world:\n\n- Case studies tied to the same pain.\n- Testimonials with specifics.\n- Screenshots, dashboards, or before\u002Fafter evidence.\n- Logos or references that reduce perceived risk.\n- Third-party mentions, referrals, podcasts, or credible appearances.\n\n### 2. Remove Hidden Risk\n\nAudit friction:\n\n- Can the buyer understand the offer quickly?\n- Is pricing or scope ambiguous?\n- Are next steps explicit?\n- Is implementation risk addressed?\n- Is the downside named and handled?\n\nAnything ambiguous increases risk.\n\n### 3. Build Layered Familiarity\n\nCreate trust across multiple surfaces before the call:\n\n- One-to-one outreach.\n- Case studies or proof drops.\n- Helpful content.\n- Video or Loom walkthroughs.\n- Social posts or founder presence.\n- Third-party channels where buyers can see independent signals.\n\nUse 7 hours, 11 touchpoints, and 4 platforms as an exposure target, not as a\nrigid law.\n\n### 4. Design The Call To Confirm\n\nAssume serious buyers arrive with a partial preference already formed.\n\nOn the call:\n\n- Reflect the buyer's problem clearly.\n- Map proof to their exact situation.\n- Avoid over-explaining or adding complexity.\n- Make the next step low-risk and obvious.\n- Confirm decision criteria and approval path.\n\n## Output Format\n\n```markdown\n# B2B Trust Plan\n\n## Opportunity Pattern\n- Qualified leads reviewed:\n- Close rate:\n- Ghost\u002Fstall pattern:\n- Main risk signal:\n\n## Proof Stack\n| Buyer Fear | Proof Needed | Existing Asset | Gap |\n|------------|--------------|----------------|-----|\n\n## Risk Removal\n- Offer clarity:\n- Pricing\u002Fscope:\n- Implementation:\n- Next step:\n- Approval path:\n\n## Call Design\n- Problem mirror:\n- Proof to show:\n- Risk to address:\n- Next action:\n```\n\n## Quality Bar\n\n- Do not try to close with confidence when proof is missing.\n- Do not treat buyer hesitation as a persuasion problem before checking risk.\n- Do not overload buyers with detail when simpler proof would reduce risk.\n- Do not ignore approval path, career risk, or incumbent safety.\n- Make \"yes\" feel safer before making the upside sound bigger.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":55},{"tags":51,"version":52,"category":53,"displayName":54},"b2b-sales,sales,trust,proof,closing","0.1.0","Marketing","B2B Trust Engineering","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-trust-engineering",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-trust-engineering",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-trust-engineering",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill b2b-trust-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fb2b-trust-engineering\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",[],[]]