Content
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a persona/competency catalog rather than actionable guidance: it enumerates database knowledge Claude already has, provides no executable code or commands, and offers a vague multi-step workflow lacking the validation checkpoints that destructive database operations demand. It is organized into sections but is monolithic with content that belongs in separate reference files.
Suggestions
Replace the capability/persona catalog with concrete, executable guidance — example EXPLAIN ANALYZE output interpretation, actual index-creation DDL, and copy-pasteable profiling commands (e.g. pg_stat_statements queries).
Add explicit validation checkpoints to the workflow (e.g. benchmark before/after, confirm no regression, verify migration rollback) since database optimizations are destructive/batch operations.
Move the long capability and tool enumerations into a references/ file and keep SKILL.md as a lean overview with one-level-deep links, shedding the knowledge Claude already has.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~150-line body is a catalog enumerating database knowledge Claude already has ('B-tree, Hash, GiST, GIN, BRIN indexes', 'Write-through, write-behind, cache-aside') plus generic boilerplate ('Clarify goals, constraints, and required inputs'), fitting the 'verbose; explains concepts Claude knows; padded' anchor. | 1 / 3 |
Actionability | There is no executable code, no commands, and no concrete procedures — the 'Response Approach' is abstract ('Analyze current performance using appropriate profiling and monitoring tools'), matching the 'vague or abstract; describes rather than instructs' anchor. | 1 / 3 |
Workflow Clarity | A 9-step 'Response Approach' sequence exists, but it has no validation checkpoints or error-recovery feedback loops for destructive/batch database operations, capping it at 2 per the rubric's destructive-operation rule. | 2 / 3 |
Progressive Disclosure | Content is well-sectioned by headers, but it is a single monolithic file with a large capability catalog that should be split into references; no bundle files exist, so it is not the one-level-deep, well-signaled structure of score 3. | 2 / 3 |
Total | 6 / 12 Passed |