Content
61%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.
The content is highly actionable with strong copy-paste SQL examples, but it is a verbose monolithic reference rather than an overview pointing to deeper materials, and it lacks validation checkpoints for its batch/destructive operations. The 'Resources' section advertises bundle files that do not exist, which both misleads navigation and breaks progressive disclosure.
Suggestions
Trim or externalize the foundational exposition (EXPLAIN metric definitions, index-type primer, basic JOIN rewriting) into reference files so SKILL.md stays a lean overview of patterns; assume Claude already knows SQL fundamentals.
Add explicit validation/verification steps for batch and destructive operations — e.g. wrap batch UPDATE/DELETE in BEGIN/ROLLBACK-with-checks, run EXPLAIN ANALYZE before and after, and warn before VACUUM FULL/REINDEX on production tables.
Either ship the seven referenced bundle files (references/*, assets/*, scripts/*) or remove the broken 'Resources' links; currently every listed path points to a non-existent file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 510-line body extensively catalogs SQL syntax and concepts Claude already knows (EXPLAIN flags, index types, B-Tree vs Hash vs GIN, basic JOIN rewriting), with long inline code blocks that re-teach fundamentals; while accurate it is noticeably padded with material that does not earn its context tokens, fitting the 3-anchor 'mostly efficient but includes some unnecessary explanation'. | 3 / 5 |
Actionability | Every pattern is backed by copy-paste-ready, executable SQL (and Python) examples with bad/good/better variants — e.g. CREATE INDEX statements, EXPLAIN ANALYZE queries, cursor-pagination SQL — covering the common cases concretely, matching the 5-anchor 'fully executable; copy-paste ready'. | 5 / 5 |
Workflow Clarity | The skill is organized as a reference catalog of patterns rather than a sequenced workflow, and critically lacks validation/verification checkpoints for destructive and batch operations (batch UPDATE/DELETE, DROP/REINDEX, VACUUM FULL which 'locks table'); per the rubric's batch/destructive rule this caps workflow_clarity at 3 even though individual patterns are clear. | 3 / 5 |
Progressive Disclosure | The body inlines ~500 lines of API/syntax reference that belongs in separate files, and the 'Resources' section lists 7 bundle paths (references/postgres-optimization-guide.md, assets/index-strategy-checklist.md, scripts/analyze-slow-queries.sql, etc.) none of which actually exist in the bundle — buried, unverified references with content inlined rather than split, matching the 2-anchor. | 2 / 5 |
Total | 13 / 20 Passed |