mindbox-cloud/agent-skills / plugins/skill-review/skills/skill-review
skill-review
VerifiedQuick and accessible AI reviewer for Agent Skills — for non-specialists. Checks structure, workflow, references, and links. Produces a clear report without technical jargon. Summary from Exhausted Vitaly. Use when user says "quick review", "basic skill check", "review my skill", "review for product owner", "light review", "quick check", "check my skill", "evaluate skill quality", "what's wrong with my skill", "review this skill". Don't use when: user asks for a deep/nightmare review (use skill-review-nightmare), user asks to create a new skill, to review code, user asks to review a prompt that is not a skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.0 KB |
| references/antipattern-bingo.md | markdown | 6.7 KB |
| references/checklist-lifecycle.md | markdown | 2.6 KB |
| references/checklist-links.md | markdown | 2.6 KB |
| references/checklist-references.md | markdown | 6.2 KB |
| references/checklist-structure.md | markdown | 5.8 KB |
| references/checklist-workflow.md | markdown | 14.1 KB |
| references/instruction-singlepass.md | markdown | 35.5 KB |
| references/maturity-diagnostic.md | markdown | 1.7 KB |
| references/report-template.md | markdown | 6.1 KB |
| references/subagent-base-rules.md | markdown | 2.4 KB |
references/checklist-links.md
View on GitHub# Checklist: Link Integrity
> Sub-agent Links. Checks the mechanical integrity of links within a single skill: file refs, markdown anchors, tables of contents, reachability, external URLs, stable cross-refs.
>
> Result of each check: `PASS` / `FAIL` / `WARNING` / `N/A`.
---
## LK01, LK05. Basic File Link Integrity
> **Stage: 2** | Axis: personal use
**LK01. File references.** Do all file mentions (`references/foo.md`, `scripts/bar.py`) point to files that actually exist in the skill folder?
*What we look for:* Broken file refs. Check every file path mentioned in `SKILL.md` and reference files — does the file exist at the stated path.
**LK05. Reachability and orphan files.** Are all required files actually reachable from `SKILL.md` via actual links? No orphan files or broken transitions?
*What we look for:* Mechanical integrity of the link graph. Build the graph from actual links and verify that all mentioned files resolve, and that expected files are not dangling without incoming links. This is a mechanical reachability check, not a policy assessment of topology; policy lives in RF08/RF09 in checklist-references.md.
---
## LK02–LK04, LK06–LK07. Navigation, Anchors, and Stable Cross-refs
> **Stage: 3** | Axis: team use
**LK02. Markdown anchors.** Do all internal links in the format `[text](#section-name)` point to a real heading in the same file?
*What we look for:* Broken internal anchors. Collect all `#anchor` links and verify that each has a corresponding heading in the same file.
**LK03. Cross-file anchors.** Do all links in the format `[text](file.md#section)` point to a real heading in a real file?
*What we look for:* Broken cross-file anchors. Check both the file's existence and the heading's existence within it.
**LK04. Table of contents (TOC).** If a file contains a TOC, do all its entries correspond to actual headings?
*What we look for:* Broken TOC. Compare the TOC entries with the actual headings in the file.
**LK06. External URLs.** If the skill contains http/https links — are they accessible? (Optional, if network access is available.)
*What we look for:* Dead external links. Try to check the availability of each external URL. If network access is unavailable, mark `N/A`.
**LK07. Cross-reference stability.** Do cross-references between skill files use headings/anchors (`file.md#section-name`) rather than line numbers (`file.md:42`)?
*Context:* Line numbers break on any edit. Headings and anchors are tied to content. Line numbers are only acceptable in one-off artifacts (review logs, reports). In internal cross-refs within a skill — headings only.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |