Internal Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or…
Experimental declared review depth for linked-intent development.
MITAuto-check passed
Install Review Depth
$ npx skills add jszmajda/lid --skill review-depth -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jszmajda/lid review-depth --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jszmajda/lid.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lid-experimental/skills/review-depth .claude/skills/review-depth && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-depth" agent skill from https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depth into .claude/skills/review-depth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-depth", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depthType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jszmajda/lid --skill review-depth -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jszmajda/lid review-depth --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jszmajda/lid.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/lid-experimental/skills/review-depth .agents/skills/review-depth && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-depth" agent skill from https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depth into .agents/skills/review-depth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-depth", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jszmajda/lid --skill review-depth -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jszmajda/lid review-depth --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jszmajda/lid.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/lid-experimental/skills/review-depth .cursor/skills/review-depth && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-depth" agent skill from https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depth into .cursor/skills/review-depth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-depth", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jszmajda/lid.git --path plugins/lid-experimental/skills/review-depth--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jszmajda/lid --skill review-depth -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jszmajda/lid review-depth --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jszmajda/lid.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/lid-experimental/skills/review-depth .gemini/skills/review-depth && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-depth" agent skill from https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depth into .gemini/skills/review-depth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-depth", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jszmajda/lid review-depthInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jszmajda/lid --skill review-depth -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jszmajda/lid.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/lid-experimental/skills/review-depth .github/skills/review-depth && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-depth" agent skill from https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depth into .github/skills/review-depth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-depth", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jszmajda/lid --skill review-depth -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jszmajda/lid review-depth --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jszmajda/lid.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/lid-experimental/skills/review-depth .opencode/skills/review-depth && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-depth" agent skill from https://github.com/jszmajda/lid/tree/main/plugins/lid-experimental/skills/review-depth into .opencode/skills/review-depth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-depth", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-depth- GitHub stars
- 107
- Token cost
- ~1.6k tokens
- SKILL.md length
- 929 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Experimental declared review depth for linked-intent development.
- Works in 5 steps: The LLD delta and spec delta. → Parked forks, read from the fork log —… → An offer to update the declared judgment… → …
- A LID projects instruction file declares a review depth in prose (e.g
- SKILL.md covers Recognizing the declaration, Entering a change, Fork protocol and The consolidated review, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review Depth is an agent skill from jszmajda/lid. 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.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Linked-Intent Development - a SDD methodology for agentic coding. The licence is MIT.
When your agent uses it
- A LID projects instruction file declares a review depth in prose (e.g
Example prompts
- “s instruction file declares a review depth in prose (e.g.”
- “/review-depth”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The LLD delta and spec delta.
- Parked forks, read from the fork log — grouped by kind, never reconstructed from memory. The user rules on each; resolutions land as…
- An offer to update the declared judgment areas when the rulings reveal a pattern ("both forks were naming calls — add naming to your…
- The failing tests, per tests-first.
- With the gate off, the code and the core workflow's Phase 6 coherence verification.
What it can do on your machine
Read from SKILL.md and the folder at commit 533ceaa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Review Depth loads about 1.6k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 929 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jszmajda/lid at commit 533ceaa, republished under its MIT licence (© jszmajda). 929 words, ~1,630 tokens.
Download SKILL.mdSave it as
.claude/skills/review-depth/SKILL.md (or your agent's skills folder).- name
- review-depth
- description
- 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.
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.
The declaration has two parts. Depth tracks the design phases — through HLD, through LLD, through EARS: phases at and above X stop per-phase as usual; the design phases below consolidate. The tests gate is whether the user reviews the failing tests before you write code. Tests always come first, failing, before any code; the gate decides only whether the user sees them then. It is on unless the user says otherwise. With it on, the consolidated review comes at the tests gate, before code. With it off, write the failing tests, go on to code without stopping, and present the consolidated review after code, with the core workflow's coherence verification. Through EARS with the gate on is the ordinary per-phase workflow. If the user turns the gate off mid-change, continue from where you are. Judgment areas name the fork kinds the user wants routed to them immediately (see below). Judgment areas start from the kinds of judgment the core linked-intent-dev skill lists under Judgment still reaches the user: every kind the user has not let go is a judgment area, with or without a declaration. Any kind that skill's references/capability-flags.md flags for your model and reasoning effort is a judgment area too, even if the user let it go, unless they said otherwise knowing the flag. No declaration means no change: full per-phase stops.
Entering a change
Declare eligibility before consolidating — never decide it silently:
This change qualifies for consolidated review: segment-local, no HLD or structural LLD work anticipated. Proceeding under your through-LLD declaration — per-phase for HLD/LLD, one consolidated review after tests (or, since you don't review tests before code, after code). OK?
Confirm the fork-log location as part of entry — create the file if it does not exist — so the first fork has somewhere to land before it arrives.
Fail-open. If the work turns out to touch the HLD, restructure an LLD, or cascade across a segment boundary, revert to per-phase stops for the remainder of the change and say so.
Show full SKILL.md (452 more words)Show less
Fork protocol
A specification fork — a spec or draft line admitting more than one reading — is a latent-intent question. Depth changes how the user reviews; it never changes who resolves a fork:
- In a declared judgment area — or plausibly in one: surface immediately, whatever the depth. Classification doubt resolves toward surfacing.
- Outside judgment areas: park it — write it to the fork log at detection, before routing around it. Never resolve it silently. Entry shape: the spec line, the divergent readings, kind, status.
- Capability-flagged work: when a phase's work touches an area flagged for your configuration (your model name and reasoning effort; if the flag list has no row for it, or you cannot tell, treat the flag as applying), stop immediately whatever the depth, even with no fork involved. Name the area and what the user should check; resume consolidation after they rule. The exception is a user who, knowing the flag, has let that kind of judgment go.
- Dependency rule: write no tests or code against an unresolved fork's spec line; do the independent work first.
- Critical-path escape: a fork blocking all remaining work surfaces immediately.
- After the boundary: a fork discovered once the consolidated review has passed surfaces immediately — the log has already been read.
Fork log location: docs/arrows/_experiments/review-depth/<segment>/fork-log.md when docs/arrows/ exists; otherwise ask the user once and record the answer in their declaration prose. The log is externalized state — retention must never depend on holding forks in working memory across the change.
The consolidated review
At the tests gate (or, with the gate off, after code), present one review containing:
- The LLD delta and spec delta.
- Parked forks, read from the fork log — grouped by kind, never reconstructed from memory. The user rules on each; resolutions land as narrowing edits or new atomic spec lines (per the core Phase 4 rule).
- An offer to update the declared judgment areas when the rulings reveal a pattern ("both forks were naming calls — add naming to your judgment areas?"). The judgment map is living.
- The failing tests, per tests-first.
- With the gate off, the code and the core workflow's Phase 6 coherence verification.
With the gate on, proceed to code after the review, with the core workflow's normal Phase 6 coherence verification. With the gate off, work on a forked spec line waits for this review.
Standing rules
- Every phase runs; only the interrupt count collapses. The consolidated review must preserve per-phase edge detection — if it can't (too much accumulated), say so and fall back to per-phase.
- The user may override in either direction at any time (the user is always right — with warning).
- This is an experiment (
lid-experimental). Promotion target and evidence bar live indocs/intent/lid-experimental/review-depth/review-depth-design.md.
© jszmajda, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/lid-experimental/skills/review-depth of jszmajda/lid.
Open the folder on GitHubat commit 533ceaa
Compare with similar skills
Review Depth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review Depth this skilljszmajda/lid | 107 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Internal Linksthedaviddias/Front-End-Checklist | 74k | — | ~770 | Automated safety check: Pass | MIT | |
| External Linksthedaviddias/Front-End-Checklist | 74k | — | ~773 | Automated safety check: Pass | MIT | |
| Invalid Linksthedaviddias/Front-End-Checklist | 74k | — | ~806 | Automated safety check: Pass | MIT | |
| Intent Requirements IntakeYeachan-Heo/oh-my-claudecode | 40k | — | ~1.5k | Automated safety check: Pass | MIT | |
| SEO Aeo Internal Linkingsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
External Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes…
Invalid Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links…
Intent Requirements Intake
Yeachan-Heo/oh-my-claudecode
Turns a pasted chat log or spoken problem report from support or ops staff into a reviewed five-section intent.md through numbered batches of questions.
SEO Aeo Internal Linking
sickn33/agentic-awesome-skills
Maps internal link opportunities between pages with relevant anchor text, placement instructions, orphan-page detection, and cannibalisation checks.
Link Checker
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Check for broken links.
More from jszmajda/lid
Bidirectional Differential
jszmajda/lid
Audit coherence across an arrow of intent by running two parallel fresh Claude sessions — one reconstructs code from a single EARS, the other reconstructs the EARS from stripped code — then…
Arrow Maintenance
jszmajda/lid
Navigation and audit overlay for linked-intent development. An agent skill from jszmajda/lid.
Map Codebase
jszmajda/lid
Bootstrap LID in an existing (brownfield) codebase. An agent skill from jszmajda/lid.
Update Lid
jszmajda/lid
Configure or reconcile a project for linked-intent development (LID).
Lid Coach
jszmajda/lid
Review a project's current linked-intent-development (LID) usage against LID's own principles and produce a prioritized report of recommendations for getting more out of the methodology.
Linked Intent Dev
jszmajda/lid
Guide for linked-intent development (LID). An agent skill from jszmajda/lid.
Questions about Review Depth
What does Review Depth do?
Experimental declared review depth for linked-intent development. Review Depth is an agent skill from jszmajda/lid. Experimental declared review depth for linked-intent development.
When should I use Review Depth?
Review Depth fits situations like: A LID projects instruction file declares a review depth in prose (e.g.
How do I install Review Depth in Claude Code?
Run `npx skills add jszmajda/lid --skill review-depth -a claude-code`. Or copy the skill folder (plugins/lid-experimental/skills/review-depth in jszmajda/lid) into .claude/skills/review-depth in your project. Claude Code loads it when a task matches its description.
How do I install Review Depth in Codex?
Run `npx skills add jszmajda/lid --skill review-depth -a codex`. Or copy the skill folder (plugins/lid-experimental/skills/review-depth in jszmajda/lid) into .agents/skills/review-depth in your project. Codex loads it when a task matches its description.
Can I use Review Depth in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jszmajda/lid --skill review-depth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-depth, .gemini/skills/review-depth, .github/skills/review-depth and .opencode/skills/review-depth in your project.
What does Review Depth need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Depth is instructions for the agent only.
Does Review Depth access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Review Depth safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Review Depth use?
Review Depth is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review Depth use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Review Depth?
Skills that share tags, products or a category with Review Depth: Internal Links (thedaviddias/Front-End-Checklist, 74k stars), External Links (thedaviddias/Front-End-Checklist, 74k stars), Invalid Links (thedaviddias/Front-End-Checklist, 74k stars) and Intent Requirements Intake (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Depth?
jszmajda (a GitHub user) maintains it in jszmajda/lid, which has 107 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 11, 2026.
Source: jszmajda/lid on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.