CtrlK
BlogDocsLog inGet started
Tessl Logo

sql-insight

Translate natural language to SQL, optimize query performance, and interpret EXPLAIN plans for SQLite and PostgreSQL. Triggered when users ask to convert questions into SQL, improve slow queries, tune indexes, analyze execution plans, or mention keywords like NL2SQL, query tuning, or full table scan.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-organized, highly actionable body: every command is executable, the script references are real, and safety mechanisms are documented. The main improvements are removing duplication between the Workflow and Quick Start sections, adding an explicit fix-and-recheck loop to the workflow, and moving the bulk reference tables into a references file.

Suggestions

Remove the duplicated command block in the Workflow section — it repeats the exact commands from Quick Start; a single-line pointer per step would suffice.

Add an explicit feedback loop to the NL→SQL workflow, e.g., "if `optimize` reports warnings, revise the SQL and re-run" and "if `explain` shows a full table scan, add or suggest an index before finalizing."

Move the 13-rule optimization table and the full output examples into a references/ file (e.g., references/rules.md) to keep SKILL.md a lean overview with well-signaled, one-level-deep references.

DimensionReasoningScore

Conciseness

The body assumes SQL knowledge and confines itself to tool-specific information (subcommands, rules, output formats), but the Workflow section repeats the exact commands already shown in Quick Start, so it sits at the efficient-with-minor-trimmable-redundancy anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Every subcommand has copy-paste-ready executable invocations with real flags and concrete inputs (e.g., `--db-path data.db schema --compact`, `explain --analyze`), plus realistic output examples — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The NL→SQL workflow is a clear numbered 4-step sequence with built-in checks (optimize, explain), but there is no explicit feedback loop (e.g., "if optimize reports issues, revise the SQL and re-check") — clear sequence with a minor validation gap rather than explicit checkpoints with error recovery.

4 / 5

Progressive Disclosure

The actual bundle is a single script whose path is used consistently and correctly, and the body is well-sectioned; however, the 13-rule optimization table and full output examples are inlined reference material in a 212-line SKILL.md with no reference files, so it matches good-structure-with-minor-organization-gaps rather than well-signaled one-level-deep references.

4 / 5

Total

17

/

20

Passed

Description

92%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.

A strong third-person description that states concrete capabilities, scopes them to SQLite and PostgreSQL, and provides an explicit trigger clause with natural keywords. The only gap is a handful of missing synonyms ("Postgres", "slow SQL") that would round out trigger coverage.

DimensionReasoningScore

Specificity

The description lists three concrete actions — "Translate natural language to SQL", "optimize query performance", and "interpret EXPLAIN plans" — scoped to SQLite and PostgreSQL, matching the comprehensive-coverage anchor; coverage is complete for the tool's capabilities, so it is not the minor-gaps anchor (4).

5 / 5

Completeness

It explicitly answers both what (first sentence) and when ("Triggered when users ask to convert questions into SQL... or mention keywords like NL2SQL, query tuning, or full table scan") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("improve slow queries", "tune indexes", "analyze execution plans", "NL2SQL", "full table scan") but a few common synonyms are missing (e.g., "Postgres", "slow SQL", "write SQL", ".sql"), fitting the good-coverage-with-gaps anchor rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche — NL-to-SQL translation, query tuning, and EXPLAIN plan interpretation for two named database engines — with distinct trigger phrases and minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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
zebbern/claude-code-guide
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.