verify SKILL.md skillA
verify from chainlesschain/chainlesschain is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chainlesschain/chainlesschain/verify@git:20260614.c74dd9dPins git:20260614.c74dd9d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chainlesschain/chainlesschain
- Path
packages/cli/src/skills-bundled/verify/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260614.c74dd9d, committed Jun 14, 2026
- Size
- 2,346 bytes
- Repository stars
- 11
- License
- a license file GitHub does not identify
Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing — beyond just unit tests.
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 change
Goal: confirm a specific change does what it claims, by observing real behavior —
not by trusting the diff or a passing test alone. $ARGUMENTS may name the change /
PR / expected behavior to verify; if empty, infer it from the recent work or the
current diff.
## 1. State the claim precisely
Write down, in one line, what the change is supposed to do and how you'd know it
worked ("after the fix, `avg([1,2,3])` returns 2, not NaN"). If you can't state a
checkable claim, ask for one rather than guessing.
## 2. Establish the before/after when feasible
- If practical and safe, observe the BUGGY behavior first (e.g. on the base
revision, or by reverting the change in a scratch copy / `cc checkpoint`), then
the FIXED behavior — so the verification is differential, not just "it ran".
- For a pure feature add, exercising the new path is enough.
## 3. Exercise it for real
- Use the `run` skill's launch patterns to start the app and drive the exact path
the change touches (the new flag / route / screen / function) with realistic
input — including an edge case the change was meant to handle.
…Read the whole file at its exact version.
How to install
mdr add chainlesschain/chainlesschain/verify@sha256:f2df8cb5d13e8089The line at the top of this page pins the label git:20260614.c74dd9d, 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_hoyaoqkxuacx3wc3)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 14, 2026.
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 (2346 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
chainlesschain/chainlesschain · 11 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hoyaoqkxuacx3wc3 GET https://markdownregistry.com/api/v1/resolve?ref=chainlesschain/chainlesschain/verify GET https://markdownregistry.com/api/v1/blob/f2df8cb5d13e8089f57a7c244066a88a8f53f6c96f6c6c57f42c2cdf621e81b9
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 chainlesschain/chainlesschain
Every file in chainlesschain/chainlesschain