[{"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",1559,"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",474,"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-11 14:40:14",{"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,97,104,130,154],{"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":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":45},"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",[],[111,112,113,114,115,116,117,118,119,120,121,29,122,123,124,125,126,127,128,129],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":45},"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",[],[137,138,139,125,140,141,142,35,143,144,145,146,147,148,116,149,150,151,152,153],"deja reflect","reflect","review","with","record","github","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":167,"publishedAt":45},"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",[160,163,164],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[156,168,169,170,171,172,173,150,174,117,175,176,177,178,29,179,180,181,182,183],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]