review-for-completeness skillA
review-for-completeness is agent-read markdown (skill) from clickety-clacks/tightbeam: Hunt what is missing, not what is wrong: the behavior, edge, error path, test, or teardown the MVP of the ask must contain but does not. Use as the completeness lens on a change..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Review for completeness Hunt what is missing, not what is wrong. Absent code produces no diff line to object to; you cannot notice a missing error path by staring at the present code. A checklist is the only reliable way to find errors of omission; it forces the question "should this exist?" where the code offers nothing to react to. The checklist is how you look. The verdict is still fitness: a missing piece the ask cannot ship without is blocking; a missing piece the ask ships without is post-mvp. 1. From the ask, list what the MVP must contain: every behavior, every error path the ask implies on the path it uses, every state the feature enters in normal use. Check each against the code. An unimplemented must-have is blocking even when everything present is correct. An unimplemented facet the ask ships without goes on the post-mvp list. 2. Walk the edges the ask will hit in normal use, or cannot function without: - empty, absent, and zero-length inputs; - the first and last element; one past the end; - concurrent and repeated invocation; re-entry mid-operation; - failure of each external call the code makes: what happens when it errors, …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/review-for-completeness@git:20260903.f172d5dmdr add clickety-clacks/tightbeam/review-for-completeness@sha256:702d99a972f3a88dPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_73gnjjytno4tvmuu)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.f172d5d latest | 2026-09-03 | f172d5d | 2,507 B | A | view · diff |
| git:20260723.7608dd1 | 2026-07-23 | 7608dd1 | 2,174 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 (2507 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
clickety-clacks/tightbeam · 14 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_73gnjjytno4tvmuu GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/review-for-completeness GET https://markdownregistry.com/api/v1/blob/702d99a972f3a88dbdad3a6acbbc59be845390176dd42a049825acc49d0d6335
Your agent 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.