database-optimizer

tessl i github:jeffallan/claude-skills --skill 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.

Review Score

64%

Validation Score

12/16

Implementation Score

42%

Activation Score

83%

SKILL.md

Review

Evals

Generated

13 days ago

Warnings & errors only

Criteria	Score
metadata_version	'metadata' field is not a dictionary
license_field	'license' field is missing
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata
body_examples	No examples detected (no code fences and no 'Example' wording)

Overall Assessment

This skill provides good structural organization and clear progressive disclosure to reference materials, but critically lacks actionable content. It reads more like a job description than executable guidance—telling Claude what a database optimizer does rather than providing concrete SQL examples, EXPLAIN output patterns, or specific configuration values that would make it immediately useful.

Suggestions

Add concrete SQL examples for common operations: EXPLAIN ANALYZE syntax, CREATE INDEX patterns, and sample configuration parameters with actual values
Include example EXPLAIN output with annotations showing how to identify common bottlenecks (sequential scans, nested loops, etc.)
Add explicit validation steps to the workflow: specific queries to run before/after changes, metrics thresholds to check, and rollback procedures
Remove the role definition paragraph and 'Knowledge Reference' keyword list—these add tokens without actionable value

Dimension	Score	Reasoning
Conciseness	2/3	The skill includes some unnecessary framing ('Senior database optimizer with 10+ years of experience') and role definition that Claude doesn't need. The reference table and constraints are reasonably efficient, but the 'Knowledge Reference' section is a redundant keyword dump.
Actionability	1/3	The skill provides no concrete code, SQL examples, or executable commands. It describes what to do ('Analyze EXPLAIN plans') without showing how. No actual EXPLAIN syntax, index creation examples, or configuration snippets are provided.
Workflow Clarity	2/3	The 5-step core workflow provides a logical sequence, but lacks explicit validation checkpoints and feedback loops. For database operations (which can be destructive), there's no 'validate -> fix -> retry' pattern or specific verification steps between stages.
Progressive Disclosure	3/3	The reference table clearly signals when to load each detailed guide with one-level-deep references. The structure appropriately separates overview content from detailed PostgreSQL/MySQL-specific guidance in referenced files.

Overall Assessment

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 through analysis and tuning recommendations.'
Restructure to follow 'what it does' + 'Use when...' pattern rather than leading with triggers only.

Dimension	Score	Reasoning
Specificity	3/3	Lists multiple specific concrete actions: 'investigating slow queries', 'analyzing execution plans', 'index design', 'query rewrites', 'configuration tuning', 'partitioning strategies', 'lock contention resolution'.
Completeness	2/3	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').
Trigger Term Quality	3/3	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.
Distinctiveness Conflict Risk	3/3	Clear database performance optimization niche with distinct triggers like 'execution plans', 'index design', 'lock contention' that are unlikely to conflict with other skills.

Repository: github.com/jeffallan/claude-skills
Last updated: 13 days ago
Created: 13 days ago

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.