Name: sql-optimization-patterns
Rating: 48 (1 reviews)
Author: administrakt0r

sql-optimization-patterns

Transform slow database queries into lightning-fast operations through systematic optimization, proper indexing, and query plan analysis.

Quality

51%

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/AI-Agents-Safe-Coding-Skills-claude/skills/sql-optimization-patterns/SKILL.md

The canonical home for this skill is sql-optimization-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

43%Weight 40%Scale 1-5

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

The body is concise and free of padding, but it provides no executable SQL or query-plan guidance and its workflow lacks explicit validation checkpoints for database operations. The single referenced resource file is missing from the bundle, weakening progressive disclosure.

Suggestions

Add concrete, executable examples inline — at minimum an EXPLAIN plan inspection snippet and a CREATE INDEX example — rather than only abstract bullet instructions.

Replace the generic workflow bullets with a sequenced, checkpointed process (e.g., capture baseline timing → run EXPLAIN → add index → re-time → verify plan improvement) with explicit validation before applying schema changes.

Create the referenced 'resources/implementation-playbook.md' (or fix the path) so the cited resource actually exists, and link it more clearly as one-level-deep detail.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept over-explanation, but the 'Do not use' bullets are generic boilerplate ('The task is unrelated to sql optimization patterns') that could be trimmed, fitting the 'efficient; minor instances that could be trimmed' anchor rather than the lean 5.	4 / 5
Actionability	Instructions are abstract high-level hints ('Clarify goals…', 'Apply relevant best practices and validate outcomes') with no SQL, no EXPLAIN examples, and no concrete commands, matching the 'minimal concrete guidance; missing the specific steps to execute' anchor; it is not a 3 because nothing executable is provided inline.	2 / 5
Workflow Clarity	The steps are barely sequenced generic bullets with validation only implicitly mentioned, and database/index operations are batch/destructive-adjacent contexts that require explicit validation checkpoints; this fits the 'rough sequence present but many gaps; validation absent' anchor rather than a 3.	2 / 5
Progressive Disclosure	The body is short and references one file one level deep, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle and is only weakly signaled, fitting the 'some structure but references not clearly signaled' anchor; it is not a 4 because of the dangling reference and weak navigation.	3 / 5
	Total	11 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 clearly states what the skill does with several concrete actions, but omits an explicit 'when to use it' trigger clause, which caps completeness. Trigger-term coverage is decent but misses common synonyms and file/plan-specific phrases.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when a query is slow, when analyzing an EXPLAIN plan, or when resolving N+1 problems').

Broaden trigger terms with natural synonyms users actually say: 'slow query,' 'EXPLAIN plan,' 'indexes,' 'query optimization,' 'database performance.'

Reorder so the 'what' is followed immediately by the 'when,' matching the top good_overall_examples pattern.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'systematic optimization,' 'proper indexing,' and 'query plan analysis' — which matches the 'lists several specific actions; minor gaps in coverage' anchor; it is not a 5 because coverage is not exhaustive (e.g., no mention of EXPLAIN plan reading, schema redesign, or N+1 resolution).	4 / 5
Completeness	The description gives a clear 'what' but no explicit 'Use when...' trigger clause, and the rubric caps completeness at 3 when trigger guidance is missing; it is not a 4 because the 'when' is only weakly implied rather than stated.	3 / 5
Trigger Term Quality	It includes some natural terms a user would say ('slow database queries,' 'indexing') but misses common variations and synonyms such as 'slow query,' 'EXPLAIN,' 'indexes,' or 'N+1,' fitting the 'some relevant keywords but missing common variations' anchor rather than the comprehensive 4.	3 / 5
Distinctiveness Conflict Risk	The SQL-optimization niche is mostly distinct, narrowed by 'query plan analysis' and 'indexing,' with only minor overlap risk against general DB-admin skills; it is not a 5 because it lacks explicit trigger phrases that would lock in the niche.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/sql-optimization-patterns/SKILL.md
Commit: 57c135b

Reviewed: 16 hours 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.