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".

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-index-advisor/skills/analyzing-database-indexes/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable SQL and well-organized sections, but it is held back by known-concept explanations, missing validation checkpoints for destructive DB operations, and a failure to reference the bundled scripts and assets that already exist.

Suggestions

Add explicit validation checkpoints to the workflow (e.g. after CREATE INDEX CONCURRENTLY, run EXPLAIN ANALYZE to confirm the index is used and performance improved before finalizing).

Reference the bundled scripts in the workflow, e.g. use analyze_indexes.py for the bulk analysis and validate_index_changes.py / rollback_index_changes.py for the create-validate-rollback loop.

Trim explanations of concepts Claude already knows (index selectivity, correlation, partial/covering index mechanics), keeping only the decision criteria that map query output to actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient SQL interleaved with decision guidance, but it explains concepts Claude already knows (e.g. "High n_distinct indicates good index selectivity", "correlation close to 1.0 suggests the column benefits from a B-tree index", partial/covering index mechanics), so it could be tightened rather than earning the lean level-3.	2 / 3
Actionability	It provides fully executable SQL queries plus copy-paste-ready CREATE INDEX / DROP INDEX statements using CONCURRENTLY, INCLUDE, and partial WHERE clauses, with specific examples matching the level-3 anchor.	3 / 3
Workflow Clarity	A clear 10-step sequence is present, but for destructive database operations (CREATE/DROP INDEX) there are no explicit validation checkpoints or feedback loops in the flow, and the bundled validate_index_changes.py is never wired in, capping it at level 2 per the database-operations feedback-loop rule.	2 / 3
Progressive Disclosure	Section organization is reasonable (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), but the actual bundle scripts and assets (analyze_indexes.py, validate_index_changes.py, rollback_index_changes.py, index_change_log.csv) are never referenced in the body, leaving relevant content unreferenced and the monolithic SQL wall inline.	2 / 3
	Total	9 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 covers what and when with index-specific triggers, but is weakened by a grammatically broken opening, vague over-claims, and a limited trigger-term set. It is functional but not exemplary.

Suggestions

Fix the malformed opening to a clean third-person action, e.g. "Analyzes database index usage and recommends optimal index configurations for PostgreSQL and MySQL."

Drop the vague "comprehensive guidance and automation" fluff and replace it with concrete actions (e.g., detect missing/unused/redundant indexes, generate CREATE/DROP statements).

Broaden trigger terms to include natural variations like "indexing", "slow queries", "add an index", and "query tuning".

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ("index design and optimization") but pads them with vague over-claims ("comprehensive guidance and automation") and a malformed opening ("Process use when you need to work with database indexing"), so it is not the multi-action, concrete list expected at level 3.	2 / 3
Completeness	It explicitly answers both what (index design and optimization for database indexing) and when via explicit trigger guidance ("Trigger with phrases like..."), satisfying the level-3 anchor for both components.	3 / 3
Trigger Term Quality	Three natural phrases are supplied ("create indexes", "optimize indexes", "improve query performance"), but coverage is limited and omits common variations such as "indexing", "slow query", or "add an index", so it falls short of the broad level-3 term set.	2 / 3
Distinctiveness Conflict Risk	The database-indexing niche is fairly clear, but the broad framing ("work with database indexing", "improve query performance") could overlap with a general database-performance or query-tuning skill, so it is not the unambiguously distinct level-3 case.	2 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-index-advisor/skills/analyzing-database-indexes/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.