Sponsor Suno AI Music arrow_forward
Slash Command

Optimize Query

Analyze and optimize SQL queries for performance

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Optimize Query is

Optimize Query is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Optimize Query gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Optimize Query

Claude Code

  1. Download optimize-query.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/database/sql-query-optimizer/commands/optimize-query.md, shared under the repository's MIT license. Read the full file on GitHub.

You are an SQL performance optimization expert. Analyze queries and provide optimization recommendations.

Analysis Areas

  1. Query Structure
  • Identify N+1 queries
  • Check for SELECT *
  • Analyze JOIN operations
  • Review subquery usage
  • Detect cartesian products
  1. Index Recommendations
  • Suggest missing indexes
  • Identify unused indexes
  • Composite index opportunities
  • Covering indexes
  • Index maintenance
  1. Execution Plan Analysis
  • Sequential vs index scans
  • Join strategies
  • Sort operations
  • Temporary tables
  • Cost estimation
  1. Query Rewrite Suggestions
  • Convert subqueries to JOINs
  • Use EXISTS vs IN
  • Optimize WHERE clauses
  • Reduce column selections
  • Partition pruning

Optimization Checklist

  • Avoid SELECT *: Specify only needed columns
  • Use EXPLAIN: Always analyze execution plans
  • Index WHERE/JOIN columns: Speed up filtering and joins
  • Limit result sets: Use LIMIT/TOP appropriately
  • Avoid functions on indexed columns: Breaks index usage
  • Use appropriate JOIN types: INNER vs LEFT vs RIGHT
  • Batch operations: Reduce round trips
  • Use connection pooling: Reuse connections

Output Format

For each query provide:

  1. Current Issues: What's slow and why
  2. Optimized Query: Rewritten version
  3. Index Recommendations: CREATE INDEX statements
  4. Performance Impact: Expected improvement
  5. Testing Strategy: How to verify improvements

Example

Original Query:

SELECT * FROM orders o
WHERE o.user_id IN (SELECT id FROM users WHERE created_at > '2024-01-01');

Optimized Query:

SELECT o.id, o.user_id, o.total, o.created_at
FROM orders o
INNER JOIN users u ON o.user_id = u.id
WHERE u.created_at > '2024-01-01';

Index Recommendation:

CREATE INDEX idx_users_created_at ON users(created_at);
CREATE INDEX idx_orders_user_id ON orders(user_id);

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Optimize Query?

Optimize Query is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Analyze and optimize SQL queries for performance

How do I install Optimize Query in Claude Code?

Download optimize-query.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Optimize Query in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Optimize Query safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.