database-query-optimization — Claude Code skill: speed up SQL queries
A skill that walks your agent through slow SQL: execution plans, indexes, and where the time actually goes. Useful when the database drags.
npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a claude-codeWhat database-query-optimization does
The skill gives the agent a structured way to look at query performance. Four reference guides ship with it in the references/ directory: query analysis, indexing strategy, optimization techniques, and a checklist. There is also a minimal EXPLAIN ANALYZE example to start from.
Typical flow: you hand over a query, the agent reads the plan and points at the spots that matter. Sequential Scan versus Index Scan, planned versus actual row counts, total execution time. Then it moves on to indexes and rewriting the query itself.
It assumes a relational database with execution plans, so non-SQL stores are out of scope. Install pulls the skill from the aj-geddes/useful-ai-prompts repository via npx skills add.
What it helps with
- find the query eating database CPU
- swap a Sequential Scan for an Index Scan
- read an execution plan from EXPLAIN ANALYZE
- pick indexes for a slow JOIN
- check for a performance regression after a release
Example prompts for the agent
- read the execution plan for this query and tell me why it is slow
- which indexes should I add for this JOIN on orders?
- run EXPLAIN ANALYZE and show where planned and actual row counts diverge
How to install database-query-optimization
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a claude-code2Manually: put the files in place
~/.claude/skills/database-query-optimization/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/database-query-optimization/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a codex2Manually: put the files in place
.agents/skills/database-query-optimization/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a cursor2Manually: put the files in place
.cursor/skills/database-query-optimization/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts database-query-optimization2Manually: put the files in place
.github/skills/database-query-optimization/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/database-query-optimizationManually: put the files in place
.devin/skills/database-query-optimization/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about database-query-optimization
How do I install database-query-optimization in Claude?
Run npx skills add aj-geddes/useful-ai-prompts --skill database-query-optimization -a claude-code. The skill file then lands at ~/.claude/skills/database-query-optimization/SKILL.md.
What does database-query-optimization do?
It helps the agent work through SQL performance: execution plan analysis, index selection, optimization techniques, and a checklist of things to verify.
Which databases does this skill fit?
It leans on execution plans and indexing, which means relational databases. The same techniques do not carry over to stores without SQL.
Source text
SKILL.md · MIT
--- name: database-query-optimization description: > Improve database query performance through indexing, query optimization, and execution plan analysis. Reduce response times and database load. --- # Database Query Optimization ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Slow database queries are a common performance bottleneck. Optimization through indexing, efficient queries, and caching dramatically improves application performance. ## When to Use - Slow response times - High database CPU usage - Performance regression - New feature deployment - Regular maintenance ## Quick Start Minimal working example: ```sql -- Analyze query performance EXPLAIN ANALYZE SELECT users.id, users.name, COUNT(orders.id) as order_count FROM users LEFT JOIN orders ON users.id = orders.user_id WHERE users.created_at > '2024-01-01' GROUP BY users.id, users.name ORDER BY order_count DESC; -- Results show: -- - Seq Scan (slow) vs Index Scan (fast) -- - Rows: actual vs planned (high variance = bad) -- - Execution time (milliseconds) -- Key metrics: -- - Sequential Scan: Full table read (slow) -- - Index Scan: Uses index (fast) -- - Nested Loop: Joins with loops -- - Sort: In-memory or disk sort ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Query Analysis](references/query-analysis.md) | Query Analysis | | [Indexing Strategy](references/indexing-strategy.md) | Indexing Strategy | | [Query Optimization Techniques](references/query-optimization-techniques.md) | Query Optimization Techniques | | [Optimization Checklist](references/optimization-checklist.md) | Optimization Checklist | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
© aj-geddes · MIT · aj-geddes/useful-ai-prompts