database-optimizer
Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill database-optimizer70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger terms and specificity with comprehensive database performance terminology. However, it inverts the typical structure by focusing heavily on 'when to use' while only implying 'what it does' - the skill's core capability (database query optimization) should be stated explicitly upfront before the trigger conditions.
Suggestions
Add an explicit capability statement at the beginning, e.g., 'Optimizes database queries and improves performance.' before the 'Use when...' clause
Consider restructuring to follow the pattern: '[What it does]. Use when [triggers].' for better completeness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'investigating slow queries', 'analyzing execution plans', 'index design', 'query rewrites', 'configuration tuning', 'partitioning strategies', 'lock contention resolution'. | 3 / 3 |
Completeness | Has strong 'when' guidance with 'Use when...' and 'Invoke for...' clauses, but the 'what does this do' is only implied through the trigger scenarios rather than explicitly stated (e.g., missing a clear statement like 'Optimizes database queries and performance'). | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'slow queries', 'execution plans', 'database performance', 'index', 'query rewrites', 'partitioning', 'lock contention' - these are terms database developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on database performance optimization with distinct triggers like 'execution plans', 'index design', 'lock contention' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization with clear progressive disclosure to reference files, but critically lacks actionable content. It reads more like a job description than executable guidance - telling Claude what a database optimizer does rather than showing how to do it with concrete SQL examples, EXPLAIN output patterns, or specific commands.
Suggestions
Add concrete SQL examples for common operations: EXPLAIN ANALYZE queries, CREATE INDEX statements, pg_stat_statements queries, and configuration changes
Include example EXPLAIN output patterns showing what to look for (sequential scans, nested loops, high cost estimates) with specific remediation steps
Add validation checkpoints to the workflow: 'Run EXPLAIN ANALYZE before changes, capture baseline metrics, then compare after optimization'
Remove the role definition paragraph and knowledge reference keyword list - Claude doesn't need to be told it's a 'senior database performance engineer' or given a list of concepts it already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the role definition paragraph and verbose constraint lists. The 'Knowledge Reference' section at the end is just a keyword dump that adds little value. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. It describes what to do abstractly ('Analyze EXPLAIN plans', 'Create indexes strategically') but never shows how with actual SQL or specific commands. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence, but lacks explicit validation checkpoints and feedback loops. For database optimization involving potentially destructive changes, there's no 'validate before proceeding' pattern or error recovery guidance. | 2 / 3 |
Progressive Disclosure | The reference table provides clear, well-signaled one-level-deep references to detailed guidance files with explicit 'Load When' conditions. The structure appropriately separates overview from detailed content. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.