Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured SQL skill with strong actionability through executable examples and a clear optimization workflow with validation feedback loops. The main weaknesses are some unnecessary guidance that Claude already knows in the constraints section, and the inability to verify the referenced bundle files. Overall it serves as an effective quick-reference and workflow guide for SQL optimization tasks.
Suggestions
Trim the MUST DO/MUST NOT DO constraints to only non-obvious, project-specific rules — Claude already knows standard SQL best practices like avoiding SELECT * and preferring set-based operations.
Ensure the referenced files (references/query-patterns.md, etc.) exist in the bundle, or remove the reference table if they don't, as broken references reduce trust in the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good examples and structure, but some sections like the MUST DO/MUST NOT DO constraints include guidance Claude already knows (e.g., 'use set-based operations over row-by-row processing', 'handle NULLs explicitly'). The inline comments in SQL examples are helpful but occasionally state the obvious. | 2 / 3 |
Actionability | The skill provides fully executable SQL examples covering CTEs, window functions, EXPLAIN ANALYZE interpretation, and before/after optimization patterns. The covering index example is copy-paste ready, and the EXPLAIN output interpretation gives specific, concrete things to check. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with an explicit validation step (step 4: run EXPLAIN ANALYZE, confirm no sequential scans, iterate if sub-100ms target not met). This constitutes a proper feedback loop for the optimization process, which is the primary multi-step operation in this skill. | 3 / 3 |
Progressive Disclosure | The reference table with 'Load When' conditions is well-structured and clearly signaled, but no bundle files were provided, so the referenced files (references/query-patterns.md, etc.) cannot be verified to exist. The SKILL.md itself contains substantial inline content (examples, constraints, output templates) that could arguably be split out, though the current length is reasonable. | 2 / 3 |
Total | 10 / 12 Passed |