Agent skill

B2b Trust Engineering

by hashgraph-online in hashgraph-online/awesome-codex-plugins

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.

MITAuto-check passedSales & Support

Install B2b Trust Engineering

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill b2b-trust-engineering -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins b2b-trust-engineering --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/b2b-trust-engineering .claude/skills/b2b-trust-engineering && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
b2b-trust-engineering
GitHub stars
1.2k
Token cost
~1k tokens
SKILL.md length
438 words
Files
1
Skills in repo
686
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 4 steps: Lead With Relevant Proof → Remove Hidden Risk → Build Layered Familiarity → …
  • Qualified buyers take calls
  • SKILL.md covers Source Traceability, Diagnostic Signals, Trust Check and Workflow, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

B2b Trust Engineering is an agent skill from hashgraph-online/awesome-codex-plugins. 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.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.

It sits in Sales & Support, covering Proposals and quotes. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.

When your agent uses it

  • Qualified buyers take calls
  • Request proposals
  • Show interest but then stall
  • Choose safer incumbents

Example prompts

  • “/b2b-trust-engineering”

Requirements

  • Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Lead With Relevant Proof
  2. Remove Hidden Risk
  3. Build Layered Familiarity
  4. Design The Call To Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit 78497e5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Codex, Claude Code, and other Agent Skills-compatible clients.

    From compatibility in the SKILL.md frontmatter.

Context cost

B2b Trust Engineering loads about 1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its MIT licence (© hashgraph-online). 438 words, ~1,035 tokens.

Download SKILL.mdSave it as .claude/skills/b2b-trust-engineering/SKILL.md (or your agent's skills folder).
name
b2b-trust-engineering
description
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.
compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
license
MIT
metadata.version
0.1.0
metadata.displayName
B2B Trust Engineering
metadata.category
Marketing
metadata.tags
b2b-sales,sales,trust,proof,closing

B2B Trust Engineering

Use this skill when qualified buyers engage but do not take action. The goal is to make the buying decision feel safe by reducing risk, increasing relevant proof, and making next steps obvious.

Source Traceability

Primary source: Unf*ck Your Sales by Jakob Greenfeld, especially the "Trust", "Diagnostics", "The Confidence Fallacy", "The Persuasion Fallacy", "The Best Option Fallacy", "The 7-11-4 Law", and "Engineering Trust" sections.

Diagnostic Signals

Trust is likely the constraint when:

  • Qualified buyers book calls, request proposals, or start trials but do not close.
  • Prospects say the offer sounds good and then vanish.
  • The buyer appears to need the outcome but still chooses an incumbent or no decision.
  • The pitch relies on confidence, vision, or ROI claims without enough proof.
  • The sales call tries to persuade instead of confirming what the buyer already believes.

Trust Check

Review the last 50 qualified opportunities where possible:

  • How many closed?
  • How many ghosted after meaningful engagement?
  • How many stalled after a proposal or trial?
  • What proof did buyers see before the call?
  • What risks, ambiguities, or next-step friction remained?

If qualified close rate is weak or ghosting is high after engagement, treat trust as the likely constraint.

Workflow

1. Lead With Relevant Proof

Use proof that matches the buyer's world:

  • Case studies tied to the same pain.
  • Testimonials with specifics.
  • Screenshots, dashboards, or before/after evidence.
  • Logos or references that reduce perceived risk.
  • Third-party mentions, referrals, podcasts, or credible appearances.
2. Remove Hidden Risk

Audit friction:

  • Can the buyer understand the offer quickly?
  • Is pricing or scope ambiguous?
  • Are next steps explicit?
  • Is implementation risk addressed?
  • Is the downside named and handled?

Anything ambiguous increases risk.

Show full SKILL.md (162 more words)Show less
3. Build Layered Familiarity

Create trust across multiple surfaces before the call:

  • One-to-one outreach.
  • Case studies or proof drops.
  • Helpful content.
  • Video or Loom walkthroughs.
  • Social posts or founder presence.
  • Third-party channels where buyers can see independent signals.

Use 7 hours, 11 touchpoints, and 4 platforms as an exposure target, not as a rigid law.

4. Design The Call To Confirm

Assume serious buyers arrive with a partial preference already formed.

On the call:

  • Reflect the buyer's problem clearly.
  • Map proof to their exact situation.
  • Avoid over-explaining or adding complexity.
  • Make the next step low-risk and obvious.
  • Confirm decision criteria and approval path.

Output Format

markdown
# B2B Trust Plan

## Opportunity Pattern
- Qualified leads reviewed:
- Close rate:
- Ghost/stall pattern:
- Main risk signal:

## Proof Stack
| Buyer Fear | Proof Needed | Existing Asset | Gap |
|------------|--------------|----------------|-----|

## Risk Removal
- Offer clarity:
- Pricing/scope:
- Implementation:
- Next step:
- Approval path:

## Call Design
- Problem mirror:
- Proof to show:
- Risk to address:
- Next action:

Quality Bar

  • Do not try to close with confidence when proof is missing.
  • Do not treat buyer hesitation as a persuasion problem before checking risk.
  • Do not overload buyers with detail when simpler proof would reduce risk.
  • Do not ignore approval path, career risk, or incumbent safety.
  • Make "yes" feel safer before making the upside sound bigger.

© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/LVTD-LLC/skills/skills/b2b-trust-engineering of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 78497e5

Compare with similar skills

B2b Trust Engineering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

B2b Trust Engineering compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
B2b Trust Engineering this skillhashgraph-online/awesome-codex-plugins1.2k—~1kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19540 repos~3.2kAutomated safety check: PassMIT
Audit Onboarding Proposalhoangnb24/repository-harness1.2k—~4kAutomated safety check: PassMIT
No Negative EchoLB623/no-negative-echo897—~965Automated safety check: PassMIT
GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude11k—~3kAutomated safety check: NotesMIT
Architectural ProposalsFritzAndFriends/SharpSite1452 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed
  • Audit Onboarding Proposal

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $audit-onboarding-proposal.

    1.2k GitHub stars~4k tokensUpdated 4 days ago
    Sales & SupportAuto-check passed
  • No Negative Echo

    LB623/no-negative-echo

    Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.

    897 GitHub stars~965 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • GEO Service Proposal Generator

    zubair-trabzada/geo-seo-claude

    Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.

    11k GitHub stars~3k tokensUpdated yesterday
    Sales & SupportAuto-check: notes
  • Architectural Proposals

    FritzAndFriends/SharpSite

    How to write comprehensive architectural proposals that drive alignment before code is written

    145 GitHub starsUsed in 2 repos~1.6k tokens
    Sales & SupportAuto-check passed
  • Task Profile

    techwolf-ai/ai-first-toolkit

    Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would…

    132 GitHub stars~3.6k tokensUpdated 9 days ago
    Sales & SupportAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 686 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.2k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.2k GitHub stars~618 tokensUpdated today
    Auto-check passed
  • Manuscript Engagement Analytics

    hashgraph-online/awesome-codex-plugins

    Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…

    1.2k GitHub stars~875 tokensUpdated today
    Auto-check passed

Categories

Questions about B2b Trust Engineering

What does B2b Trust Engineering do?

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. B2b Trust Engineering is an agent skill from hashgraph-online/awesome-codex-plugins. 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.

When should I use B2b Trust Engineering?

B2b Trust Engineering fits situations like: qualified buyers take calls; request proposals; show interest but then stall; choose safer incumbents.

How do I install B2b Trust Engineering in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill b2b-trust-engineering -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/b2b-trust-engineering in hashgraph-online/awesome-codex-plugins) into .claude/skills/b2b-trust-engineering in your project. Claude Code loads it when a task matches its description.

How do I install B2b Trust Engineering in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill b2b-trust-engineering -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/b2b-trust-engineering in hashgraph-online/awesome-codex-plugins) into .agents/skills/b2b-trust-engineering in your project. Codex loads it when a task matches its description.

Can I use B2b Trust Engineering in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill b2b-trust-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/b2b-trust-engineering, .gemini/skills/b2b-trust-engineering, .github/skills/b2b-trust-engineering and .opencode/skills/b2b-trust-engineering in your project.

What does B2b Trust Engineering need to run?

SKILL.md names no scripts, command-line tools or credentials: B2b Trust Engineering is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..

Does B2b Trust Engineering access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is B2b Trust Engineering safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does B2b Trust Engineering use?

B2b Trust Engineering is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does B2b Trust Engineering use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to B2b Trust Engineering?

Skills that share tags, products or a category with B2b Trust Engineering: Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars), No Negative Echo (LB623/no-negative-echo, 897 stars) and GEO Service Proposal Generator (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains B2b Trust Engineering?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.