optimizing-sql-queries

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill optimizing-sql-queries

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

41%

Overall

Validation — 81%

Implementation — 20%

Activation — 40%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill is a generic template that has been minimally customized for SQL query optimization. It contains no actual SQL-specific guidance, no query examples, no EXPLAIN plan analysis, no indexing strategies, and no concrete optimization techniques. The content could apply to virtually any technical task and fails to provide the specialized knowledge Claude would need for query optimization.

Suggestions

Add concrete SQL examples showing before/after optimization with EXPLAIN plan analysis (e.g., adding indexes, rewriting subqueries as JOINs)

Include specific query optimization techniques: index usage, query rewriting patterns, common anti-patterns to avoid

Remove generic boilerplate about credentials, backups, and stakeholder reviews - focus only on SQL-specific guidance

Add validation steps specific to query optimization: comparing execution times, analyzing query plans, measuring I/O operations

Dimension	Reasoning	Score
Conciseness	Extremely verbose with generic boilerplate that applies to any task, not SQL query optimization specifically. Explains obvious concepts like 'verify credentials' and 'monitor resource usage' that Claude already knows. Almost no SQL-specific content despite the skill name.	1 / 3
Actionability	No concrete SQL examples, no actual query optimization techniques, no executable code. Entirely abstract guidance like 'Define optimal approach based on best practices' without specifying what those practices are for query optimization.	1 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, but they're generic project management steps, not SQL query optimization workflows. No validation checkpoints specific to query performance (e.g., EXPLAIN plans, execution time comparisons).	2 / 3
Progressive Disclosure	References external files in Resources section with clear paths, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist, and the Overview/Examples sections at the end are empty placeholders.	2 / 3
	Total	6 / 12 Passed

Activation

40%

This description suffers from vague capability statements and lacks concrete actions. While it attempts to provide trigger phrases, the core functionality ('comprehensive guidance and automation') is abstract fluff. The description would benefit from specifying what type of queries, what databases, and what specific optimization actions are performed.

Suggestions

Replace vague phrases like 'comprehensive guidance and automation' with specific actions (e.g., 'Analyzes SQL execution plans, identifies missing indexes, rewrites inefficient joins')

Specify the query/database types supported (e.g., 'PostgreSQL', 'MySQL', 'SQL queries') to reduce ambiguity and conflict risk

Add more natural trigger terms users would say, such as 'slow query', 'execution plan', 'index optimization', or 'database bottleneck'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'query performance analysis with comprehensive guidance and automation' without listing concrete actions. It doesn't specify what types of queries, what analysis is performed, or what automation is provided.	1 / 3
Completeness	Has a 'Trigger with phrases like...' clause which partially addresses 'when', but the 'what' is weak and vague. The description doesn't clearly explain what concrete capabilities the skill provides beyond generic 'analysis' and 'guidance'.	2 / 3
Trigger Term Quality	Includes some relevant trigger phrases ('optimize queries', 'analyze performance', 'improve query speed') but misses common variations like 'slow query', 'SQL optimization', 'database performance', 'execution plan', or specific database types.	2 / 3
Distinctiveness Conflict Risk	The term 'query optimization' provides some specificity, but 'queries' is ambiguous (SQL? NoSQL? API queries?) and could overlap with database skills, SQL skills, or general performance tools.	2 / 3
	Total	7 / 12 Passed

Reviewed

14 days ago

Table of Contents

Validation Implementation Activation

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.