database-optimizer

What This Skill Does

The database-optimizer skill transforms your OpenClaw agent into a veteran Database Reliability Engineer. It is designed to scrutinize complex SQL and NoSQL environments, identifying performance bottlenecks that slow down production systems. This skill excels at parsing EXPLAIN ANALYZE outputs, resolving pervasive N+1 query patterns within ORM-heavy applications, and designing sophisticated indexing strategies that turn millisecond-latencies into microsecond-responses. It covers the full lifecycle of database health, from schema design and partition strategy to connection pooling and caching architecture.

Installation

You can integrate this skill into your OpenClaw environment by executing the following command in your terminal:

clawhub install openclaw/skills/skills/anton-abyzov/sw-database-optimizer

Use Cases

• Production Outages: Diagnosing sudden latency spikes in PostgreSQL or MySQL clusters by identifying blocked processes and long-running lock contention.
• Application Refactoring: Analyzing ORM logs (Django, SQLAlchemy, ActiveRecord) to eliminate N+1 database hits during batch processing operations.
• Schema Evolution: Designing partitioning strategies for massive datasets that have outgrown standard B-tree indexing capabilities.
• Cloud Optimization: Tuning specific cloud-native features like AWS Aurora storage auto-scaling or MongoDB Atlas compound index utilization.

Example Prompts

1. "Analyze this EXPLAIN ANALYZE output for my slow-running JOIN query and suggest a covering index to optimize the sequential scans."
2. "My Django application is firing 500 queries on a single page load. Help me refactor this to use select_related or prefetch_related efficiently."
3. "I have a MongoDB collection with 50 million documents. What is the best strategy for compound indexing to support both range queries on timestamps and equality checks on user_id?"

Tips & Limitations

To get the best results, always provide the agent with sanitized schema definitions and real execution plans rather than just raw code. Be aware that the optimizer is an advisory tool; always test suggested schema migrations (like index additions) on a staging instance with production-representative data volume. The skill cannot directly connect to your private database instance without the appropriate permissions and network access configured in your environment. Always verify performance gains against a baseline before deploying changes to production environments.