trust-but-verify SKILL.md skillA
trust-but-verify from buildbetter-app/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add buildbetter-app/skills/trust-but-verify@git:20260604.6094087Pins git:20260604.6094087 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- buildbetter-app/skills
- Path
skills/testing/trust-but-verify/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260604.6094087, committed Jun 4, 2026
- First version recorded
- Apr 3, 2026
- Size
- 9,448 bytes
- Repository stars
- 24
- License
- a license file GitHub does not identify
Use when a feature branch has been implemented and you need to verify the UI/UX and functionality match the original plan before merging.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Trust But Verify
Verify that a feature implementation actually matches its plan by testing it in a real browser.
**Core principle:** Plans describe intent. Code describes implementation. Only the browser shows reality. This skill bridges all three — reading the plan, analyzing the diff, and verifying the result in a live browser.
## When to Use
- After completing a feature branch and before merging
- When a plan exists in `docs/plans/` for the current work
- When the diff touches frontend source files (UI changes)
- When you want confidence that the UI matches the spec
- When recommended by `superpowers:finishing-a-development-branch`
**Not for:** Backend-only changes, API-only work, or branches without a plan.
## Process
```dot
digraph trust_but_verify {
"Phase 1:\nGather Context\n(subagent)" [shape=box];
"Phase 2:\nPreflight Check\n(main)" [shape=box];
"Phase 3:\nBrowser Verification\n(main + MCP)" [shape=box];
"Phase 4:\nReport\n(subagent)" [shape=box];
"Print summary\n+ link to report" [shape=doublecircle];
"Phase 1:\nGather Context\n(subagent)" -> "Phase 2:\nPreflight Check\n(main)";
…Read the whole file at its exact version.
How to install
mdr add buildbetter-app/skills/trust-but-verify@sha256:d7078592ab9833d3The line at the top of this page pins the label git:20260604.6094087, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_32gmige24o2aiwf2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 3, 2026 and Jun 4, 2026, about one every 63 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260604.6094087 latest | 2026-06-04 | 6094087 | 9,448 B | A | view · diff |
| git:20260403.7a022e8 | 2026-04-03 | 7a022e8 | 9,170 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9448 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
buildbetter-app/skills · 24 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_32gmige24o2aiwf2 GET https://markdownregistry.com/api/v1/resolve?ref=buildbetter-app/skills/trust-but-verify GET https://markdownregistry.com/api/v1/blob/d7078592ab9833d39ccdff35bdb81c07914daf9304d51003e0b8fc758a72c4cd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from buildbetter-app/skills
Every file in buildbetter-app/skills