Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured with a clear sequenced workflow and explicit verification checkpoints, but it is over-long with redundancy against the description, leans on process description over concrete artifacts, and references bundle files that do not exist in the skill directory.
Suggestions
Remove or collapse the 'Scheduling' subsection (Intent signature, When to use, Expected inputs/outputs) since it duplicates the frontmatter description almost verbatim.
Create the referenced bundle files (resources/document-templates.md, anti-patterns.md, vector-db.md, iso-controls.md, checklist.md, etc.) or remove the dangling references so progressive disclosure is realized rather than promised.
Move detailed guardrails and the Required Deliverables list into the referenced template/guide files, keeping SKILL.md a lean overview with concrete `rg` commands and the high-level workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient structured lists that assume Claude's competence (it references 3NF/ACID/BASE without explaining them), but the 'Scheduling' section (Intent signature, When to use, Expected inputs/outputs) heavily duplicates the frontmatter description and could be trimmed; not 3 due to this redundancy and overall length. | 2 / 3 |
Actionability | Provides some concrete guidance (executable `rg` commands and specific guardrails like 'enforce at least 3NF by default'), but much of the body is process description ('Produce external/conceptual/internal schema documentation') rather than copy-paste-ready artifacts; not 3 because it is not consistently executable/specific. | 2 / 3 |
Workflow Clarity | Clear sequence (Entry → PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE → Exit) with an explicit VERIFY checkpoint, a failure-and-recovery section, and a 'run checklist.md before submitting' gate; not 2 because validation feedback loops are present for the risky migration operations. | 3 / 3 |
Progressive Disclosure | The References section is well-signaled and one-level deep, but no bundle files exist (no references/scripts/assets/resources directories) so every referenced resources/*.md and ../_shared/core/*.md path is absent, and large amounts of content that should live in those files (guardrails, deliverables, workflow) are inlined in SKILL.md; not 3 because the split is not actually realized on disk. | 2 / 3 |
Total | 9 / 12 Passed |