Content
86%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.
Excellent progressive disclosure: the body is a lean, well-organized index over 31 verified reference files, with a priority table and an explicit navigation procedure. The two weaker spots are that no executable SQL appears in the body itself (it is fully delegated to reference files) and the workflow lacks any validation or verification guidance for applying the rules.
Suggestions
Include one or two key inline snippets for the CRITICAL categories (e.g., the canonical EXPLAIN ANALYZE invocation or a covering-index example) in SKILL.md so the highest-impact guidance is immediately actionable without a file hop.
Add brief symptom-to-category mapping (e.g., 'slow query → start with query-*', 'too many connections → conn-*') so users' problems route to the right rules faster than the category-priority table alone.
Add a short validation step in 'How to Use' (e.g., re-run EXPLAIN ANALYZE before/after applying an index or schema change) since the rules target database operations where verifying the fix matters.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean index: no explanations of concepts Claude already knows, no padded prose; every element earns its place — the one-line rule directives, and the priority table which adds impact/prefix data beyond the section headers. This matches anchor 5 ('lean and efficient; every token earns its place') better than anchor 4, since the table/category-header overlap is structural navigation, not over-explanation. | 5 / 5 |
Actionability | Concrete directives ('Use cursor-based pagination instead of OFFSET', 'Add indexes on WHERE and JOIN columns') and a concrete command ('Glob the prefix (for example references/query-*.md)') give mostly actionable guidance, but all executable SQL lives one hop away in the reference files, leaving the minor gap that anchor 4 describes ('concrete code or commands with minor gaps') rather than anchor 5's copy-paste-ready code. | 4 / 5 |
Workflow Clarity | The lookup workflow is an unambiguous sequence ('Read individual files as needed; to review a whole category, Glob the prefix, then Read the files in one turn') and the priority table guides category selection, but there are no validation checkpoints or error-recovery guidance — anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') fits better than anchor 5, which demands explicit validation steps and feedback loops. | 4 / 5 |
Progressive Disclosure | A clear overview with well-signaled one-level-deep references: all 31 rule files listed in the quick reference were verified to exist in references/ with matching prefixes, and the 'How to Use' section explicitly describes each file's contents ('explanation, incorrect/correct SQL examples, EXPLAIN output, and context') plus a concrete Glob navigation pattern — matching anchor 5. | 5 / 5 |
Total | 18 / 20 Passed |