sql-explainer

Paste a SQL query and get a plain English explanation of what it does.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/gemma/sql-explainer/SKILL.md

Quality

Content

100%Weight 40%Scale 1-3

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

The content is a well-structured, concise, single-purpose skill: it tells Claude exactly which tool to call and what fields to produce, with no concept over-explanation and clean sectioning. The bundle is appropriately scoped as runtime artifacts rather than navigational references.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what SQL or joins are, and the parameter spec is tight; only the phrase 'No database knowledge required' is mild fluff but does not undermine efficiency.	3 / 3
Actionability	Specifies the exact tool ('run_js') with a fully typed, constrained data payload (query truncation, optional step3, tip), giving concrete copy-paste-ready guidance for an instruction-only skill.	3 / 3
Workflow Clarity	This is a single, unambiguous action (take a query, produce the structured breakdown, call run_js once) with no destructive or batch operations, so a clear single-step workflow scores 3 under the simple-skill note.	3 / 3
Progressive Disclosure	Under 50 lines with well-organized Examples and Instructions sections; the bundle files (scripts/index.html, assets/webview.html) are runtime webview scaffold rather than navigational references, and there is no nested/deep reference chain.	3 / 3
	Total	12 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 clear and distinct but minimal: it states what the skill does without explicit 'when to use' guidance and with limited trigger-term coverage. Adding a 'Use when...' clause and a few more natural phrasings would lift the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user pastes a SQL query or asks what a query does.'

Broaden trigger terms with natural variations like 'what does this query do', 'translate SQL', or 'explain this SQL'.

Consider naming a couple of concrete output actions (e.g. 'summarizes and breaks down a query step by step') to reach specificity 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('SQL query') and one concrete action ('get a plain English explanation of what it does'), but does not list multiple specific concrete actions as required for a 3.	2 / 3
Completeness	Clearly answers what the skill does, but provides no 'Use when...' or equivalent explicit trigger guidance for when Claude should invoke it, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Includes natural user terms like 'SQL query' and 'plain English explanation', but coverage is thin and missing common variations such as 'what does this query do' or 'translate SQL'.	2 / 3
Distinctiveness Conflict Risk	The SQL-to-plain-English niche is distinct and unlikely to trigger for unrelated skills; no realistic conflict with other domains.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mergisi/awesome-openclaw-agents
Path: skills/gemma/sql-explainer/SKILL.md
Commit: 05820c5

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