review-depth SKILL.md skillA
review-depth from jszmajda/lid is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jszmajda/lid/review-depth@git:20261011.9779c87Pins git:20261011.9779c87 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jszmajda/lid
- Path
plugins/lid-experimental/skills/review-depth/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261011.9779c87, committed Oct 11, 2026
- First version recorded
- Sep 25, 2026
- Size
- 6,553 bytes
- Repository stars
- 112
- License
- MIT
Experimental declared review depth for linked-intent development. Use when a LID project's instruction file declares a review depth in prose (e.g. "Review depth - I review through LLD; below that, consolidate to one review") or the user asks to batch phase reviews, consolidate stops, or let go below a phase depth. Overlays the linked-intent-dev workflow — every phase still runs; interrupts consolidate. Never activates on its own judgment.
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
# Review Depth (experiment) An experimental overlay on the `linked-intent-dev` workflow: the user declares the design phases they personally review, and whether they review the tests before code; deeper phases still run in full, but their outputs consolidate into **one review** instead of stopping per phase. Per-phase stops remain LID's default — this skill changes nothing unless the user has declared a review depth. An active declaration is the user's express authorization to suspend the per-phase stop default (LID-CORE-005) below the declared depth. ## Recognizing the declaration The declaration is the **user's own prose** — in their instruction file or stated in-session. LID writes no configuration for it. Recommended shape (offer it to users who want a standing declaration): > Review depth: I review through LLD; below that, consolidate to one review. I don't need to see the tests before code. > Judgment areas: naming and API shapes; anything touching auth. …
Read the whole file at its exact version.
How to install
mdr add jszmajda/lid/review-depth@sha256:c9eb8257b2569bd9The line at the top of this page pins the label git:20261011.9779c87, 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_pbrpk4heagy6wlzo)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 25, 2026 and Oct 11, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.9779c87 latest | 2026-10-11 | 9779c87 | 6,553 B | A | view · diff |
| git:20261010.a1bb965 | 2026-10-10 | a1bb965 | 5,579 B | A | view · diff |
| git:20261001.0fc7b54 | 2026-10-01 | 0fc7b54 | 5,498 B | A | view · diff |
| git:20260929.fc18658 | 2026-09-29 | fc18658 | 5,264 B | A | view · diff |
| git:20260925.8f4b392 | 2026-09-25 | 8f4b392 | 5,228 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 (6553 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
jszmajda/lid · 112 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pbrpk4heagy6wlzo GET https://markdownregistry.com/api/v1/resolve?ref=jszmajda/lid/review-depth GET https://markdownregistry.com/api/v1/blob/c9eb8257b2569bd9a4d7e1da379b2cd0daa8d00aca18d2870f322c2299e1fa55
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.