ln-162-skill-reviewer
Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.
How do I install this agent skill?
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-162-skill-reviewerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The ln-162-skill-reviewer skill is a specialized development tool designed to audit AI agent skills and documentation for compliance with quality and architecture standards. It executes a comprehensive verification pipeline using a suite of local Bash and Node.js scripts provided within the skill package. The skill automates structural and intent reviews, manages execution state through a custom runtime, and leverages external CLI agents (Codex and Claude) for specialized analysis. No malicious patterns, data exfiltration, or security vulnerabilities were detected.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
1/5 files flagged
What does this agent skill do?
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
ln-162-skill-reviewer
Type: L3 Worker (standalone-capable) Category: 1XX Documentation Pipeline
Universal reviewer with two modes:
SKILLforln-*/SKILL.mdCOMMANDfor.claude/commands/*.md- repo suite for this skills repository when
repo/repo-checksis requested or the current repo isclaude-code-skills
Plan Mode behavior: Phases 1-4 and 6-7 are research. Run them fully in Plan Mode, write the report plus fix list into the plan, and apply edits only after approval.
Mode Detection
| Condition | Mode | Review Profile |
|---|---|---|
ln-*/SKILL.md files exist in CWD | SKILL | Full D1-D11 + M1-M6 |
.claude/commands/*.md files exist | COMMAND | Structural + actionability |
| Both exist | SKILL | Override with $ARGUMENTS=commands |
Input
$ARGUMENTS options:
- empty -> auto-detect mode and scope
ln-400 ln-500-> SKILL mode, specific skillsrepoorrepo-checks-> run canonical repo-specific checks after universal reviewcommands-> COMMAND mode, all.claude/commands/*.mddeploy.md run-tests.md-> COMMAND mode, specific files
When invoked by another skill, file paths may be passed directly.
SKILL Mode
Phase 1: Scope Detection
If $ARGUMENTS is provided:
- treat each token as a skill directory prefix
- glob
{prefix}*/SKILL.md
If $ARGUMENTS is empty:
- inspect git diff, staged files, and untracked files
- collect primary skill dirs
- collect affected skills referencing changed shared files
- collect dependency skills from worker tables and
Skill()invocations
Report:
Scope: {N} primary, {M} affected, {K} dependency skills.
Phase 2: Automated Verification
Run:
# Never pass a giant mixed scope in one invocation.
# Split by `ln-NXX` family or by coordinator/worker group.
bash references/scripts/run_checks.sh {batch_1 SKILL.md files}
bash references/scripts/run_checks.sh {batch_2 SKILL.md files}
Batching rules:
- keep each invocation within one
ln-NXXfamily when possible - if scope mixes coordinators and workers, split them into separate invocations
- if one family is still large, chunk it into 5-10 files per invocation
Automated failures are pre-verified. Record every one.
Phase 3: Structural Review
MANDATORY READ: Load references/structural_review.md, references/skill_contract.md, references/procedural_skill_sop_guide.md, references/mcp_applicability_matrix.md, and references/mcp_tool_preferences.md
Review every skill in scope across D1-D11.
Treat these as structural issues, not style nits:
- missing
**Type:**when role-sensitive checks depend on it - worker independence violations in L3 workers
- broken shared paths
- stale root-doc assumptions — CLAUDE.md duplicating AGENTS.md content instead of using the
@AGENTS.mdimport stub with a bounded harness delta - markdown-analysis skills missing
markdown_read_protocol.md - extraction or audit skills contradicting the shared docs-quality contract
- skills contradicting the shared skill contract
- skills that should make
hex-lineprimary but only describe built-in file tools - skills that should make
hex-graphprimary but still describe grep/manual analysis as the default path - skills that add
hex-graphorhex-linewith no real applicability per the shared matrix - wrong MCP namespaces such as
mcp__hex_graph__... - procedural skills with vague modal words, compound high-risk steps, missing point-of-use checklists, missing why for risky steps, missing executable preflight, or missing evidence
Phase 4: Intent Review
MANDATORY READ: Load references/intent_review.md
Apply M1-M6 to primary skills only. Read the git diff for each primary skill.
Phase 5: Fix
Auto-fix deterministic issues:
- wrong paths
- stale references
- duplicated wording
- worker-independence violations with exact removals
- copied docs shell sections in command files
Do not guess on ambiguous behavior.
After fixes, re-read each primary skill end-to-end and compress redundant wording without changing behavior.
Phase 6: Report
Verdict rules:
- any structural violation not auto-fixed ->
FAIL - only advisory intent concerns remain ->
PASS with CONCERNS - zero findings ->
PASS
Report format:
## Skill Coherence Review -- {PASS|PASS with CONCERNS|FAIL}
**Scope:** {reviewed skills}
**Verdict:** {verdict}
Phase 7: Volatile Numbers Cleanup
Remove stale aggregate counts from SKILL.md files. Keep only local counts intrinsic to the reviewed file.
Repo Suite Mode
Use when running inside this repository or when $ARGUMENTS includes repo / repo-checks.
Phase 1: Universal Review
Run the applicable SKILL or COMMAND mode first. Do not skip the universal review.
Phase 2: Repo-Specific Checks
Run the canonical repo suite:
node plugins/documentation-pipeline/skills/ln-162-skill-reviewer/references/scripts/repo_review_suite.mjs
Default repo suite runtime policy:
- default:
--runtime quick(implicit) runs bounded smoke coverage only - structure-only:
--runtime skip - release/CI:
--runtime full
node plugins/documentation-pipeline/skills/ln-162-skill-reviewer/references/scripts/repo_review_suite.mjs --runtime full
The suite owns R1-R27. Do not copy those checks into host-specific command files. Do not use the full runtime suite as the default interactive review gate; it is intentionally release-grade and can exceed normal review latency.
Phase 3: Combined Report
Merge the universal review verdict and repo suite verdict:
| Source | Verdict | Details |
|--------|---------|---------|
| Universal review | {PASS|PASS with CONCERNS|FAIL} | {summary} |
| Repo suite | {PASS|PASS with WARNINGS|FAIL} | {R1-R27 summary} |
| Combined | {worst verdict} | |
List all FAIL and WARN items with file paths and fix descriptions.
COMMAND Mode
MANDATORY READ: Load references/command_review_criteria.md
Phase 1: Scope Detection
- explicit file paths -> review those files
commands-> glob.claude/commands/*.md- coordinator-supplied file list -> review those files
Phase 2: Review
For each command file:
- apply all command review criteria
- verify source provenance
- verify no copied docs shell sections remain
Phase 3: Fix
Auto-fix where safe:
- missing frontmatter
- missing
allowed-tools - description too long
- missing
Last Updated - exact copied docs shell sections
Phase 4: Report
## Command Review -- {N} files
| File | Verdict | Issues |
|------|---------|--------|
Verdicts: PASS / FIXED / WARN / FAIL
Pass rate: {X}%
Rules
- Automated checks are non-negotiable.
- Read all scoped files before reporting.
- Fix deterministic issues immediately.
- Do not update versions or dates unless the user explicitly requests it.
shared/changes affect all referencing skills.- Worker independence is mandatory for L3 workers:
- no
**Coordinator:** - no
**Parent:** - no required caller declaration
- no
- Docs-model drift is a structural defect, not a preference.
- Unsupported platform APIs are prohibited outside clearly marked historical references.
Reference Files
references/structural_review.mdreferences/intent_review.mdreferences/automated_checks.mdreferences/scripts/run_checks.shreferences/scripts/run_runtime_suite.mjsreferences/scripts/repo_review_suite.mjsreferences/command_review_criteria.mdreferences/scripts/check_marketplace.mjs
Definition of Done
- Scope detected
- Automated checks executed
- D1-D11 reviewed across all scoped skills
- M1-M6 evaluated for primary skills
- Fixable findings auto-fixed
- Post-fix holistic compaction completed
- Final verdict report generated
Version: 1.0.0 Last Updated: 2026-03-26
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/levnikolaevich/claude-code-skills/ln-162-skill-reviewer">View ln-162-skill-reviewer on skillZs</a>