analyzing-query-performance

Execute use when you need to work with query optimization. This skill provides query performance analysis with comprehensive guidance and automation. Trigger with phrases like "optimize queries", "analyze performance", or "improve query speed".

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 clearly sequenced workflow, but it is monolithic — ignoring available bundle scripts/assets — and could be tighter and more explicit about validation checkpoints for impactful database changes.

Suggestions

Reference the bundled scripts in the workflow (e.g., 'Run scripts/explain_plan_parser.py on the captured plan') and link to assets/example_explain_plans/ instead of keeping everything inline.

Add an explicit validation gate before recommending production changes, e.g., 'Verify the improved plan on staging; only recommend indexes whose staging EXPLAIN shows a lower cost.'

Trim inferred parentheticals like '(indicates missing index)' and '(consider hash join or merge join)' to rely on Claude's existing knowledge.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable SQL throughout and no basic-concept padding, but includes inferable parentheticals ('indicates missing index', 'consider hash join or merge join', 'adding a covering index eliminates the sort') that could be trimmed.	2 / 3
Actionability	Provides copy-paste-ready, executable SQL for every analysis step (pg_stat_statements query, EXPLAIN commands, cache-hit-ratio and bloat queries) plus concrete CREATE INDEX recommendations with exact columns.	3 / 3
Workflow Clarity	Ten steps are clearly sequenced and step 8 verifies via before/after EXPLAIN on staging with an error-handling table, but there are no explicit validate-then-proceed checkpoints for impactful database changes, so per the database-operations feedback-loop guideline workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	Well-organized into clear sections, but the body is monolithic and never references the bundled scripts (explain_plan_parser.py, index_advisor.py, query_rewriter.py) or the example_explain_plans assets; content that could be split out remains inline.	2 / 3
	Total	9 / 12 Passed

Description

80%

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 both what and when with natural trigger phrases and a clear, distinct niche, but its capability statement is vague and padded with fluff ('comprehensive guidance and automation') and it uses second-person voice.

Suggestions

Replace 'comprehensive guidance and automation' with concrete actions, e.g., 'identifies missing indexes, rewrites slow queries, and recommends CREATE INDEX statements ranked by expected impact.'

Use third person and drop 'you', e.g., 'Use when working with query optimization' instead of 'Execute use when you need to work with query optimization.'

Dimension	Reasoning	Score
Specificity	Names the domain and one action ('query performance analysis') but pads it with fluff ('comprehensive guidance and automation') rather than listing concrete actions; additionally uses second person ('Execute use when you need to work with query optimization'), which per the rubric reduces specificity by one from a base of 2 to 1.	1 / 3
Completeness	Answers both what ('query performance analysis') and when with explicit triggers ('Execute use when you need to work with query optimization', 'Trigger with phrases like...'), so it is not capped at 2.	3 / 3
Trigger Term Quality	Includes natural phrases a user would actually say — 'optimize queries', 'analyze performance', and 'improve query speed' — giving good coverage of likely trigger terms.	3 / 3
Distinctiveness Conflict Risk	Centered on a clear niche — database query performance/optimization — with distinct trigger phrases 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: 6e3a65f

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.