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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/query-performance-analyzer/skills/analyzing-query-performance/SKILL.md

Quality

Content

80%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 and token-efficient, with executable SQL and concrete thresholds throughout. Its main weaknesses are implicit (rather than explicit inline) validation checkpoints in the database workflow and bundled scripts that are never referenced from the main body.

Suggestions

Add explicit inline validation checkpoints in the workflow, e.g. after step 2: "Validate: confirm the plan ran against representative data before interpreting red flags; if EXPLAIN ANALYZE is too slow, fall back to EXPLAIN without ANALYZE (see Error Handling)."

Reference the bundled scripts from the body where relevant, e.g. in step 2 "or run `scripts/explain_plan_parser.py` to extract key metrics from the captured plan," and add a References/Resources pointer to the bundled scripts and assets directories.

Consider moving the lengthy Examples and Error Handling detail into a referenced file (e.g. references/TROUBLESHOOTING.md) to keep the main workflow focused while preserving the material one level deep.

Dimension	Reasoning	Score
Conciseness	The body is lean and technical — concrete SQL, threshold-based red flags, and targeted lists — with no padding explaining basic database or indexing concepts Claude already knows. The only mild verbosity is the narrative Examples, which still earn their place as illustrative cases.	3 / 3
Actionability	It provides copy-paste-ready executable SQL throughout (e.g. the pg_stat_statements query, EXPLAIN (ANALYZE, BUFFERS, FORMAT JSON), the cache-hit-ratio query) with specific numeric thresholds (>10,000 rows, ratio below 0.95, dead-ratio above 0.2), matching the score-3 anchor.	3 / 3
Workflow Clarity	The 10 numbered steps form a clear sequence and step 8 plus the Error Handling table provide some verification/recovery, but this is a database-operation workflow whose validation checkpoints are implicit and scattered rather than explicit inline "validate then proceed" markers. Per the rubric's feedback-loop guidance for database operations, that caps the score at 2.	2 / 3
Progressive Disclosure	The SKILL.md itself is well-organized into clear sections, but the bundled scripts (explain_plan_parser.py, index_advisor.py, query_rewriter.py) and references/assets are never referenced or linked from the body — the Resources section points only to external URLs. Useful bundled material is orphaned with no navigation signaling, matching the score-2 anchor of references present but not clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

72%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 has strong trigger terms and a distinct niche, but its capability statement is padded with buzzwords ("comprehensive guidance and automation") rather than concrete actions, leaving the "what" weakly answered. Tightening the capability clause into specific actions would lift specificity and completeness.

Suggestions

Replace "with comprehensive guidance and automation" with concrete capabilities, e.g. "Capture EXPLAIN plans, detect missing indexes and sequential scans, and rank optimization recommendations by expected impact."

Keep the explicit "Use when..." clause but ensure the capability sentence reads as a list of specific actions rather than abstract claims.

Dimension	Reasoning	Score
Specificity	The description names the domain ("query performance analysis") but the only action language is the buzzword phrase "with comprehensive guidance and automation," which lists no concrete capabilities. It is above the vague score-1 anchor but below the score-3 anchor requiring multiple specific concrete actions.	2 / 3
Completeness	The "when" is explicit ("Execute use when you need to work with query optimization" plus trigger phrases), but the "what" is only weakly answered with padded phrasing ("query performance analysis with comprehensive guidance and automation") rather than a concrete capability list. The "what" is not clearly answered, so it does not reach the score-3 anchor.	2 / 3
Trigger Term Quality	It provides natural trigger phrases a user would actually say — "optimize queries", "analyze performance", and "improve query speed" — giving good coverage of common variations, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (query optimization/performance) with distinct triggers ("optimize queries", "analyze performance", "improve query speed") unlikely to fire for unrelated skills, matching the score-3 anchor.	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
Path: plugins/database/query-performance-analyzer/skills/analyzing-query-performance/SKILL.md
Commit: 4c47e33

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.