sql-master

Database expert - query optimization, schema design

Quality

68%

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 ./skills/sql-master/SKILL.md

Quality

Content

68%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 a lean, executable SQL reference with strong code examples across optimization, schema, advanced queries, and tuning. Its main weakness is the absence of validation/feedback-loop checkpoints for destructive database operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints around destructive operations, e.g. run EXPLAIN ANALYZE before and after adding an index to confirm the plan improves, and test schema migrations on a backup first.

Define the `products` table referenced by `order_items` and replace the `EXPLAIN ANALYZE SELECT ...;` ellipsis with a concrete statement so every example is fully executable.

Trim the decorative opening persona line and closing quote to recover tokens, or move advanced examples (window functions, CTEs) into a referenced ADVANCED.md to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and assumes SQL competence with minimal prose, fitting 'efficient; minor instances of over-explanation that could be trimmed'; not a 5 because the opening 'You are SQL Master...' line and the closing inspirational quote are decorative padding.	4 / 5
Actionability	Most sections give concrete, copy-paste-ready SQL (CREATE INDEX, JOIN rewrites, CTEs, window functions), matching 'mostly executable guidance with minor gaps'; not a 5 because the `products` table is referenced but never defined and one EXPLAIN example uses an ellipsis.	4 / 5
Workflow Clarity	Content is organized by topic rather than as a sequenced workflow, and there are no validation checkpoints or feedback loops for destructive database operations; per the scoring notes, database skills without validation feedback loops are capped at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers (Query Optimization, Schema Design, Advanced Queries, Performance Tuning) in a single self-contained file with no nested references, fitting 'good structure; minor organization gaps'; not a 5 because at ~140 lines some advanced material could be split into a reference file.	4 / 5
	Total	15 / 20 Passed

Description

53%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 is a concise label naming the database domain and two concrete specialties, but it lacks a 'Use when' trigger clause and the natural term 'SQL'. It is clear and distinct but stops short of explicit invocation guidance.

Suggestions

Add a 'Use when...' clause naming trigger phrases, e.g. 'Use when optimizing slow SQL queries, designing or normalizing schemas, or analyzing query plans.'

Include the natural keyword 'SQL' and synonyms like 'indexes', 'queries', and 'query plans' so users' phrasings match the description.

Consider adding one more concrete capability (e.g. 'query plan analysis' or 'window functions') to broaden specificity toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	The phrase 'query optimization, schema design' names the database domain plus two concrete action areas, matching the score-3 anchor of 1-2 concrete actions without comprehensive coverage; it is not a 4 because only two actions are listed rather than several.	3 / 5
Completeness	It clearly states what the skill does ('query optimization, schema design') but provides no 'Use when...' trigger clause, so per the judging guideline a missing trigger caps completeness at 3.	3 / 5
Trigger Term Quality	'database', 'query optimization', and 'schema design' are relevant keywords but omit the most natural synonym 'SQL' and common variations users say, fitting the anchor for some relevant keywords missing common synonyms; not a 4 because coverage lacks natural phrasings.	3 / 5
Distinctiveness Conflict Risk	'Database expert' carves a clear niche with low conflict risk against non-database skills, fitting 'mostly distinct; minor overlap risk'; not a 5 because the absence of explicit trigger phrases leaves minor overlap with general data-analysis skills.	4 / 5
	Total	13 / 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: TurnaboutHero/oh-my-antigravity
Path: skills/sql-master/SKILL.md
Commit: f73e1ff

Reviewed: 15 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.