verify-and-review SKILL.md skillA
verify-and-review from theonly1me/shadowclone is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add theonly1me/shadowclone/verify-and-review@git:20261019.61ac16ePins git:20261019.61ac16e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- theonly1me/shadowclone
- Path
.agents/skills/verify-and-review/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261019.61ac16e, committed Oct 19, 2026
- First version recorded
- Oct 9, 2026
- Size
- 4,079 bytes
- Repository stars
- 21
- License
- MIT
Use before you say that work is done, fixed, or ready for review. Also use it when the user says "make sure it works", "verify this", or "is it ready?". Runs the command or page that the user will use, and reads every count, status line, and exit code. Reviews the whole diff, and labels each claim as measured, inferred, or not verified. This catches a wrong count or a buried warning before handoff. Not for writing or proving tests (use `tests-that-catch-bugs`).
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
# Verify the Real Outcome ## Use when You are about to say that a change is done, fixed, or ready for review. A question does not need this skill. Answer it directly. ## Gates 1. Did you run what the user runs: the command, the page, or the request, on the surface that they use? A passing unit test does not show that the command works. 2. Did you read every line of the real output, including counts, totals, the final lines, and the exit code? Does each one match what happened? 3. If the command writes files, did it run in a temporary home or a copy? Did you read the files that it wrote? 4. Does each claim in your report have a label: measured, inferred, or not verified? 5. Did you read the whole diff, including new files, and remove debug output, temporary mutations, and unrelated edits? 6. Does the report list each behavior choice, such as a skip or a fallback, with its output line? ## Process 1. List what changed for the user: commands, output lines, exit codes, written files, pages, and documents. 2. Run the focused tests, then the required check of the repository. Run a broad check again only when a later change needs it. …
Read the whole file at its exact version.
How to install
mdr add theonly1me/shadowclone/verify-and-review@sha256:79d0a84dfb0916f8The line at the top of this page pins the label git:20261019.61ac16e, 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_4kwg4aer6i4yyeig)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 19, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.61ac16e latest | 2026-10-19 | 61ac16e | 4,079 B | A | view · diff |
| git:20261009.95ca1ef | 2026-10-09 | 95ca1ef | 4,030 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 (4079 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
theonly1me/shadowclone · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4kwg4aer6i4yyeig GET https://markdownregistry.com/api/v1/resolve?ref=theonly1me/shadowclone/verify-and-review GET https://markdownregistry.com/api/v1/blob/79d0a84dfb0916f8dfda93cb4bf9aacac20701e42cadae04ba755725976e376c
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 theonly1me/shadowclone
Every file in theonly1me/shadowclone