CtrlK
BlogDocsLog inGet started
Tessl Logo

sql-optimization-patterns

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

36

Quality

34%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/sql-optimization-patterns/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

18%Scale 1-5

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

This skill is essentially a placeholder with no actionable content. It describes what SQL optimization is about but provides zero concrete guidance — no SQL examples, no EXPLAIN plan analysis steps, no indexing patterns, no optimization workflows. The entire substance is deferred to a resource file that doesn't exist in the bundle, leaving the skill non-functional.

Suggestions

Add concrete SQL examples showing common optimization patterns (e.g., replacing subqueries with JOINs, adding covering indexes, fixing N+1 queries) with before/after EXPLAIN output.

Define a clear workflow: 1) Run EXPLAIN ANALYZE on the slow query, 2) Identify bottlenecks (sequential scans, missing indexes), 3) Apply optimization, 4) Re-run EXPLAIN to validate improvement — with specific commands at each step.

Replace the generic instruction bullets ('Apply relevant best practices') with SQL-specific actionable guidance that Claude can directly execute.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns directly in the SKILL.md.

DimensionReasoningScore

Conciseness

The 'Use this skill when' and 'Do not use this skill when' sections are padded with obvious items that don't add value. The instructions section is generic boilerplate ('Clarify goals, constraints, and required inputs') rather than SQL-specific content. However, it's not excessively verbose overall.

3 / 5

Actionability

The skill provides zero concrete code, commands, SQL examples, or executable guidance. Every instruction is vague and abstract ('Apply relevant best practices and validate outcomes'). There are no actual optimization patterns, no EXPLAIN examples, no indexing strategies — everything is deferred to a resource file that doesn't exist in the bundle.

1 / 5

Workflow Clarity

There is no meaningful workflow defined. The four bullet points under Instructions are generic platitudes with no sequencing, no validation checkpoints, and no specific steps for query optimization. For a skill involving database operations, the complete absence of validation steps is a critical gap.

1 / 5

Progressive Disclosure

The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in theory. However, the bundle confirms no such file exists, making the reference a dead link. The SKILL.md itself contains essentially no substantive content, so it's not a useful overview — it's an empty shell pointing to a nonexistent resource.

2 / 5

Total

7

/

20

Passed

Description

50%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 identifies the domain of database query optimization and mentions a few relevant techniques, but relies on marketing language ('lightning-fast operations') rather than concrete trigger terms. It lacks an explicit 'Use when...' clause, which is critical for skill selection, and misses many natural keywords users would employ when seeking database performance help.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'slow query', 'SQL performance', 'query optimization', 'EXPLAIN plan', 'database is slow', or 'query takes too long'.

Replace the marketing phrase 'lightning-fast operations' with concrete actions such as 'rewrite inefficient JOINs, add covering indexes, analyze EXPLAIN output, eliminate N+1 queries, optimize subqueries'.

Include natural synonyms and technology-specific terms users might mention, such as 'SQL', 'PostgreSQL', 'MySQL', 'execution plan', 'table scan', 'index tuning'.

DimensionReasoningScore

Specificity

Names the domain (database queries) and mentions a few concrete actions (optimization, indexing, query plan analysis), but these are still somewhat high-level and not comprehensively detailed — e.g., no mention of specific techniques like covering indexes, JOIN optimization, EXPLAIN analysis, or partitioning.

3 / 5

Completeness

The 'what' is present (optimize queries through indexing and query plan analysis), but there is no explicit 'when' clause — no 'Use when...' guidance telling Claude when to select this skill. This caps the score at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes some relevant keywords like 'database queries', 'indexing', and 'query plan analysis', but misses many natural user phrases such as 'slow query', 'SQL performance', 'EXPLAIN', 'execution plan', 'N+1', 'table scan', or specific database names (PostgreSQL, MySQL). 'Lightning-fast operations' is marketing fluff, not a trigger term.

3 / 5

Distinctiveness Conflict Risk

The description is somewhat specific to database query optimization, but 'systematic optimization' and 'proper indexing' are broad enough to overlap with general database administration skills, schema design skills, or broader performance tuning skills.

3 / 5

Total

12

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.