Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is concise, highly actionable, and well-organized for a knowledge-style skill with no bundle files. Its main weakness is workflow clarity: guidance is principle-based rather than a clearly sequenced process with explicit validation checkpoints.
Suggestions
For destructive or batch operations (e.g. bulk loads, VACUUM, schema migrations), present an explicit ordered workflow with validate-then-proceed checkpoints rather than listing them as standalone principles.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it jumps straight into concrete guidance like 'EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)' and JSONB operators without explaining basic PostgreSQL concepts. | 3 / 3 |
Actionability | Provides fully executable SQL and commands throughout, e.g. 'CREATE INDEX ON orders (created_at) WHERE status = \'pending\'' and 'INSERT ... ON CONFLICT (key) DO UPDATE SET ...', copy-paste ready. | 3 / 3 |
Workflow Clarity | Sequencing exists implicitly ('Always analyze query plans ... before and after optimization') but validation checkpoints are scattered across principles rather than presented as a coherent multi-step workflow with explicit feedback loops. | 2 / 3 |
Progressive Disclosure | Under 50 lines with no need for external references, and content is organized into clear, well-signaled sections (Key Principles, Techniques, Common Patterns, Pitfalls) — satisfying the simple-skill allowance for a top score. | 3 / 3 |
Total | 11 / 12 Passed |