analyzing-database-indexes
Process use when you need to work with database indexing. This skill provides index design and optimization with comprehensive guidance and automation. Trigger with phrases like "create indexes", "optimize indexes", or "improve query performance".
77
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/database-index-advisor/skills/analyzing-database-indexes/SKILL.mdQuality
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.
The description adequately identifies its domain and provides explicit trigger phrases, which is a strength. However, it suffers from vague capability language ('comprehensive guidance and automation') instead of listing concrete actions, and the opening 'Process use when' is awkward phrasing. The description would benefit from more specific action verbs describing what the skill actually does.
Suggestions
Replace vague phrases like 'comprehensive guidance and automation' with specific concrete actions such as 'analyze query execution plans, recommend composite indexes, generate CREATE INDEX statements, identify unused or redundant indexes'.
Fix the awkward opening 'Process use when you need to' — rewrite in third person declarative voice, e.g., 'Designs and optimizes database indexes by analyzing query patterns and recommending index strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database indexing) and mentions 'index design and optimization' but lacks specific concrete actions beyond that. 'Comprehensive guidance and automation' is vague filler rather than listing specific capabilities like 'analyze query plans, suggest composite indexes, generate CREATE INDEX statements'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (index design and optimization) and 'when' (trigger phrases like 'create indexes', 'optimize indexes', 'improve query performance'). The trigger guidance is explicit and clearly stated. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'create indexes', 'optimize indexes', 'improve query performance'. These are realistic terms a user would use when needing this skill, covering both creation and optimization scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Database indexing is a reasonably specific niche, but 'improve query performance' could overlap with general database query optimization skills that don't focus on indexing. The trigger 'optimize indexes' is distinct, but the broader performance trigger introduces some conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with concrete SQL queries and real-world examples that provide genuine value. Its main weaknesses are the monolithic structure (everything inline rather than split across files) and the lack of explicit validation checkpoints in the workflow for what are potentially impactful production database operations. The content could be tightened by removing explanations of concepts Claude already understands (index selectivity, B-tree behavior, what partial indexes are).
Suggestions
Add explicit validation checkpoints in the workflow: after creating an index, verify it exists and confirm the target query's EXPLAIN plan now uses it; include a rollback step if the index doesn't improve performance.
Trim explanatory text that Claude already knows (e.g., 'Partial indexes are smaller and faster than full indexes when the filter eliminates most rows', 'High n_distinct indicates good index selectivity') to improve conciseness.
Consider splitting the error handling table, detailed examples, and MySQL-specific guidance into separate bundle files, keeping SKILL.md as a lean overview with references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with actionable SQL queries and concrete guidance, but includes some unnecessary verbosity in explanations (e.g., explaining what high n_distinct means, what correlation means, what partial indexes are). Some sections like the examples could be tighter. The error handling table, while useful, adds significant length. | 2 / 3 |
Actionability | Excellent actionability with ready-to-execute SQL queries throughout, specific column references for system catalog views, concrete CREATE INDEX and DROP INDEX statements, and real-world examples with measurable outcomes (e.g., '2 seconds to 5ms'). The guidance is copy-paste ready for PostgreSQL environments. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced from identification through recommendation, but lacks explicit validation checkpoints and feedback loops. There's no 'verify the index was created correctly' step, no 'confirm query plan improved after index creation' checkpoint, and no error recovery loop within the workflow itself. For a process involving production database changes, this is a notable gap. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Overview, Instructions, Output, Error Handling, Examples, Resources), but it's a monolithic document with no bundle files. The detailed 10-step instructions, error handling table, and three full examples could benefit from being split into separate reference files, with the SKILL.md serving as a concise overview pointing to them. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.