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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with executable SQL and a clear step sequence, but it explains index concepts Claude already knows, omits an explicit apply-and-verify feedback loop for destructive index changes, and fails to link or surface the bundled scripts and references it ships with.

Suggestions

Remove concept primers Claude already knows (selectivity, INCLUDE/leaf-page mechanics, partial-index sizing) and keep only the SQL and decision rules to tighten conciseness.

Add an explicit apply-verify loop to the workflow: after CREATE/DROP INDEX, re-run EXPLAIN (ANALYZE) to confirm the index is used; on failure run ANALYZE and re-check, with a rollback step.

Surface the bundled files in the body — link scripts/analyze_indexes.py for the analysis run and note the validate/rollback scripts and assets CSV under an Advanced section rather than leaving them unlinked.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable SQL but interspersed with concept explanations Claude already knows (e.g. "High n_distinct ... indicates good index selectivity", "INCLUDE columns are stored in the index leaf pages"), so it could be tightened; not the score-3 lean ideal.	2 / 3
Actionability	It provides fully executable, copy-paste-ready SQL commands throughout (e.g. `SELECT relname, seq_scan, ... FROM pg_stat_user_tables`, `CREATE INDEX ON orders (status, created_at)`), matching the score-3 anchor.	3 / 3
Workflow Clarity	The 10 steps are clearly sequenced and step 2 includes EXPLAIN validation, but the destructive apply phase (CREATE/DROP INDEX) lacks an explicit create-verify-rollback checkpoint loop in the workflow; per the database-operations scoring note this caps at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but never references the bundled scripts/refs (analyze_indexes.py, the references README) and keeps detailed query catalogs inline; bundle files exist but are not signaled or linked, fitting the score-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 answers both what and when with explicit, natural trigger phrases and a distinct niche, though it opens with garbled grammar ("Process use when...") and leans on fluff ("comprehensive guidance and automation"). Specificity and trigger coverage are the weakest areas.

Dimension	Reasoning	Score
Specificity	It names the domain ("database indexing") and two actions ("index design and optimization") but pads them with fluff ("comprehensive guidance and automation") rather than listing multiple concrete actions, matching the score-2 anchor.	2 / 3
Completeness	It states what the skill does ("index design and optimization") and gives an explicit "use when you need to work with database indexing" clause plus trigger phrases, answering both what and when.	3 / 3
Trigger Term Quality	Phrases like "create indexes", "optimize indexes", and "improve query performance" are natural, but coverage is thin and misses common variations (e.g. "slow queries", "add index", "database performance"), so it fits the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The niche (database indexing) with specific trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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
Commit: 607d11b

Reviewed: 5 days 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.