Individual skill

trust-architecture

Build credibility in writing, marketing, and product flows using Mayer's ABI model, inoculation, operational transparency, and costly signaling. Use when audiences are skeptical or fatigued by hype.

skills/trust-architecture/SKILL.md

Read pinned source

Source commit 953e486421606632752c455b4ea3e8305220f2c0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
19
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Trust Architecture

Attention without trust produces bounce rates. According to the **Persuasion Knowledge Model** (Friestad & Wright 1994), modern readers and users constantly scan for signs that someone is trying to sell or manipulate them. Once they detect hype, their cognitive defenses lock shut.

Use this skill to disarm skepticism *before* or *while* deploying any hook.

## The ABI Trust Equation (Mayer, Davis & Schoorman 1995)

A person will only invest time or money when three independent perceptions are present:

1. **Ability (Can you actually solve this?)** is demonstrated through forensic specificity, working artifacts, and domain precision, never through self-praise ("industry-leading", "world-class").
2. **Benevolence (Are you on my side or just extracting value?)** is proven when you protect the user's time, wallet, or autonomy even at a short-term cost to yourself.
3. **Integrity (Do your rules stay consistent when nobody is looking?)** shows up through upfront constraints, symmetric cancellation, and zero hidden conditions.

## The 6 Invisible Trust Levers