query-optimizer

What This Skill Does

The Query Optimizer skill is a high-performance diagnostic tool designed to pinpoint and resolve inefficiencies in database interactions. Whether you are working with raw SQL or modern ORM syntax like Prisma, this skill acts as a virtual database administrator. It parses your code to identify expensive operations, such as full table scans, non-sargable predicates, or inefficient join patterns. By analyzing your queries, it provides actionable advice, including precise 'CREATE INDEX' statements to speed up lookups and refactoring suggestions to eliminate hidden performance bottlenecks. Its standout feature is its ability to detect 'N+1' query problems within ORM code, which is a common but often overlooked culprit behind application latency. The skill essentially translates abstract performance issues into concrete, testable code fixes.

Installation

Installation is handled through the OpenClaw ecosystem. You can add this skill to your workspace by running:

clawhub install openclaw/skills/skills/lxgicstudios/query-optimizer

Ensure you have Node.js 18+ installed on your system. To enable the underlying AI-powered analysis, you must set your environment variable: export OPENAI_API_KEY=sk-.... No local database connection or complex setup is required, as the tool operates by analyzing the text of your query files or pasted SQL strings.

Use Cases

This skill is perfect for scenarios where you suspect database performance is hindering your application. Typical use cases include debugging slow API endpoints identified by your APM, refactoring legacy codebases with inefficient data access patterns, or ensuring your Prisma models are supported by optimized indices before shipping to production. It is also an excellent educational tool for junior developers learning how to write performant database queries.

Example Prompts

1. "Analyze this Prisma query to see why it takes 3 seconds to return: [code snippet]"
2. "I am getting a lot of slow query logs for this SQL command. Can you suggest an index? SELECT * FROM users WHERE status = 'active' AND last_login < '2023-01-01'"
3. "Check the following file for potential N+1 issues and suggest a more efficient way to fetch these records using Prisma: src/repositories/orderRepository.ts"

Tips & Limitations

To get the best results, always provide the database schema or table structure along with your query. The optimizer works best when it understands the existing indexing strategy and table relationships. Remember that while the tool provides excellent suggestions, you should always validate these changes using EXPLAIN ANALYZE on your specific database engine. The tool is designed for optimization, not data migration or schema design, so verify all suggested CREATE statements in a staging environment before running them against production data. Finally, avoid premature optimization; focus on queries that are actually impacting user experience or system resources.