Content
50%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-organized, domain-expert skill whose core value lies in its 17 concrete guardrails, but it is wrapped in redundant meta-framework scaffolding, its verification steps name checks without saying how to run them, and its heavy reliance on 11+ resource files that are missing from the bundle leaves both actionability and navigation incomplete.
Suggestions
Ship the referenced resource files (or remove the references): 11 `resources/*.md` and 4 `../_shared/core/*.md` paths are cited but absent, breaking every detailed lookup.
Make the VERIFY step executable — give the actual anti-pattern/integrity check commands or inline the checklist content instead of pointing to a missing resources/checklist.md.
Trim the process scaffolding (Scenes, SSL-primitive action table, Resource scope table) and the repeated vector-DB guidance down to a single section to cut token cost without losing substance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 17 guardrails are dense and mostly earn their tokens, but the surrounding scaffolding ("Scheduling"/"Intent signature", the PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE "Scenes", and the invented "SSL primitive" action table) is process ceremony that adds no database knowledge, and key guidance is repeated across sections (vector-DB rules appear in Control-Flow, Transitions, guardrails 12–15, and Optimize). Not the 2 anchor's 'several unnecessary explanations' of known concepts, but clearly could be tightened. | 3 / 5 |
Actionability | There is some genuinely concrete guidance — the canonical `rg` discovery commands are executable, and guardrails 16–17 (expand-contract steps, measure-explain-re-measure) are specific — but most sections give abstract direction ("Model entities/aggregates, integrity, transactions...") with no worked example, SQL snippet, or template, and the files that would carry the detail (resources/query-tuning.md, resources/migration-playbook.md, etc.) are not present in the bundle. | 3 / 5 |
Workflow Clarity | The Entry → Scenes → Transitions → Failure/Recovery → Exit sequence is coherent, and a VERIFY step exists ("Run anti-pattern, integrity, consistency, and backup/recovery checks"), but the checkpoints are implicit and non-executable — no commands or procedures are given, and the self-check file (resources/checklist.md) is absent. Since this skill governs migrations on live tables, vague validation for destructive/batch operations holds it at the 3 anchor rather than 4. | 3 / 5 |
Progressive Disclosure | The References section is well-labeled with one purpose per file and one-level-deep paths, but none of the 11 referenced `resources/*.md` or `../_shared/core/*.md` files exist in the bundle, so navigation is broken, and content that belongs in those files (guardrail details, deliverable templates) is inlined in a ~185-line SKILL.md. This sits between 'minimal structure/inlined content' (2) and 'good structure with minor gaps' (4). | 3 / 5 |
Total | 12 / 20 Passed |