Content
17%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a persona/role description rather than an actionable skill file. It is dominated by extensive lists of capabilities, knowledge areas, and behavioral traits that Claude already possesses, while lacking concrete code examples, specific commands, executable workflows, or validation steps. The content would need a fundamental restructuring to be useful as a skill.
Suggestions
Replace the capability/knowledge/behavioral trait lists with concrete, executable SQL examples covering the most common use cases (e.g., window functions, EXPLAIN analysis, index creation patterns).
Add specific validation steps to the workflow, such as 'Run EXPLAIN ANALYZE and verify no sequential scans on large tables' or 'Test with LIMIT before running full queries on production.'
Provide copy-paste ready code snippets for key patterns like query optimization, partitioning, and CTE usage instead of just naming the concepts.
Remove sections that describe what Claude already knows (e.g., lists of database platforms, general SQL features) and focus only on project-specific conventions, preferred patterns, or non-obvious techniques.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded. The bulk of the content is long lists of capabilities, knowledge bases, behavioral traits, and example interactions that Claude already knows. These are descriptions of what an SQL expert does, not actionable instructions. The content reads like a resume or role description rather than a skill file. | 1 / 5 |
Actionability | The Instructions section provides only four high-level steps ('Define query goals', 'Inspect schema', 'Optimize queries', 'Verify correctness') with no concrete code, commands, or executable examples. The 'Example Interactions' section lists prompts but provides no actual SQL examples, query patterns, or copy-paste ready code. | 2 / 5 |
Workflow Clarity | There is a rough 4-step sequence in Instructions and an 8-step Response Approach, but both are vague and lack specific validation checkpoints. For a skill involving query optimization and potentially destructive operations on production databases, the absence of concrete validation steps (e.g., specific EXPLAIN commands, rollback procedures) is a significant gap. | 2 / 5 |
Progressive Disclosure | The content is a monolithic wall of bullet-point lists with no references to external files and no meaningful structure beyond flat section headers. The massive capability lists should be either removed (Claude knows these) or split into reference files. There are no bundle files to support progressive disclosure. | 2 / 5 |
Total | 7 / 20 Passed |