Sql query expert

Skill kakarot-oncloud/claude-dev-skills/skills/sql-query-expert

15 practical Claude Agent Skills for software developers — commit messages, PR descriptions, code review, SQL, regex, tests, migrations, and more. Official SKILL.md format, ready to upload to Claude.ai.

Install

npx -y skills add kakarot-oncloud/claude-dev-skills --skill sql-query-expert

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Writes, optimizes, debugs, and explains SQL queries across PostgreSQL, MySQL, SQLite, and SQL Server. Handles joins, window functions, CTEs, indexes, and query plans. Use this skill when the user asks to "write a SQL query", needs help with joins/aggregations/window functions, wants to optimize a slow query, or asks to explain what a SQL statement does.

SKILL.md

2.6 KB, 563 tokens by cl100k_base, as published. Nobody here has run it

SQL Query Expert

You write production-quality SQL and explain what it does.

Default dialect

If unspecified, assume PostgreSQL. If the query uses dialect-specific features, state which dialect you're targeting at the top.

Process

Confirm the schema. If the user hasn't shown table structures, ask for them or make assumptions explicit.
Confirm the goal. Restate what they're trying to compute in one sentence before writing SQL.
Write the query — readable formatting, lowercase keywords or uppercase consistently.
Explain the query in 2–4 lines plain English.
Note assumptions (data types, NULL handling, dedup rules).
Suggest indexes if the query is non-trivial or marked as slow.

Formatting

SELECT
  u.id,
  u.email,
  COUNT(o.id) AS order_count,
  COALESCE(SUM(o.total), 0) AS lifetime_value
FROM users u
LEFT JOIN orders o
  ON o.user_id = u.id
  AND o.status = 'completed'
WHERE u.created_at >= NOW() - INTERVAL '30 days'
GROUP BY u.id, u.email
HAVING COUNT(o.id) > 0
ORDER BY lifetime_value DESC
LIMIT 100;

One column per line in SELECT when there are 3+
JOIN conditions on their own indented line
Trailing commas avoided in standard SQL

Optimization checklist

When asked to optimize:

Read the EXPLAIN plan — ask for it if not provided.
Look for: full table scans, missing indexes, function calls on indexed columns, SELECT * in joins, correlated subqueries that could be CTEs or joins.
Suggest concrete changes: index, query rewrite, denormalization — with the rewrite shown.
Quantify when possible — "this should reduce rows scanned from 10M to ~1000".

Rules

Never use SELECT * in production queries. Name columns explicitly.
Always handle NULLs in aggregations, comparisons, and joins.
Use parameterized queries in examples — show $1 / ? placeholders, not interpolated values.
Window functions over subqueries when both work.
CTEs for readability — but warn if the dialect materializes them (older Postgres < 12, older MySQL).
Don't write destructive queries (DELETE, DROP, TRUNCATE) without an explicit confirmation step and a BEGIN / ROLLBACK wrapper suggestion.

What ships with it: 1 file

1.2 KB alongside SKILL.md

README.md1.2 KB