sql-pro

Master modern SQL with cloud-native databases, OLTP/OLAP optimization, and advanced query techniques. Expert in performance tuning, data modeling, and hybrid analytical systems.

Quality

41%

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-pro/SKILL.md

The canonical home for this skill is sql-pro in rmyndharis/antigravity-skills

Quality

Content

35%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 persona/resume-style document that restates broadly known SQL domain knowledge rather than providing executable guidance. It has a sequenced workflow with some validation, but lacks concrete code, feedback loops, and any progressive-disclosure file structure.

Suggestions

Cut the 'Capabilities', 'Knowledge Base', and 'Behavioral Traits' enumerations of known products/concepts; keep only guidance Claude would not already infer.

Add concrete, executable examples (e.g. an EXPLAIN-based tuning snippet, a recursive CTE pattern, an index-strategy checklist) instead of abstract step descriptions.

Add an explicit validate->fix->retry feedback loop in the workflow, and move the long capability/product lists into a separate reference file referenced one level deep.

Dimension	Reasoning	Score
Conciseness	The ~165-line body is noticeably verbose, with padded sections ('Capabilities', 'Knowledge Base', 'Behavioral Traits') that enumerate products and concepts (Aurora, Snowflake, 'Modern SQL standards') Claude already knows rather than adding novel guidance.	2 / 5
Actionability	Guidance is high-level ('Inspect schema, statistics, and access paths', 'Optimize queries and validate with EXPLAIN') with no executable SQL, commands, or copy-paste examples; the 'Response Approach' is similarly abstract.	2 / 5
Workflow Clarity	The 'Instructions' section lists a sequenced 4-step process with some validation ('validate with EXPLAIN', 'Verify correctness and performance under load'), but there is no explicit validate->fix->retry feedback loop, which the rubric caps at 3 for database operations.	3 / 5
Progressive Disclosure	The body has clear section headers, but no bundle files exist and all content (long capability enumerations, example interactions) is inlined in one monolithic file rather than split into one-level-deep references.	3 / 5
	Total	10 / 20 Passed

Description

48%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 scopes a SQL/database specialization but reads as a persona tagline rather than trigger guidance: it states expertise areas without a 'Use when...' clause and uses imperative/second-person voice. It is distinguishable but lacks concrete actions and natural trigger phrasings.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g. 'Use when writing or optimizing SQL queries, tuning query plans, or designing OLTP/OLAP schemas').

Replace capability-area nouns with concrete actions (e.g. 'write recursive CTEs', 'analyze EXPLAIN plans', 'design star schemas') instead of 'Master modern SQL'.

Rewrite in third person ('Optimizes SQL queries...') to avoid the imperative/second-person 'Master' phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain ('modern SQL', 'cloud-native databases', 'OLTP/OLAP') and activity categories ('performance tuning', 'data modeling', 'advanced query techniques') but no concrete executable actions like 'write recursive CTEs' or 'analyze EXPLAIN plans'; the imperative 'Master modern SQL' reads as second-person voice, which lowers the score by one from a base of 3.	2 / 5
Completeness	It gives a reasonably clear 'what' (SQL expertise across cloud-native and hybrid systems) but provides no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant keywords a user might say ('SQL', 'OLTP/OLAP', 'performance tuning', 'data modeling') but misses common natural phrasings and synonyms like 'optimize this query', 'tune slow SQL', or 'write a query'.	3 / 5
Distinctiveness Conflict Risk	The SQL/database niche is fairly distinct with minimal overlap risk against unrelated skills, though it could overlap with general data-engineering or analytics skills.	4 / 5
	Total	12 / 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-pro/SKILL.md
Commit: 57c135b

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