Database

What This Skill Does

The Database skill acts as an expert-level technical advisor for architecting, maintaining, and scaling database systems. It provides deep architectural guidance on preventing common pitfalls in production environments, such as connection exhaustion, transaction deadlocks, schema migration failures, and data integrity issues. This skill helps developers and engineers navigate the complexities of relational databases like PostgreSQL and MySQL, offering actionable advice on everything from connection pooling and replication strategy to proper handling of timezones and financial data types.

Installation

Install the skill via the command line: clawhub install openclaw/skills/skills/ivangdavila/db

Use Cases

• Production Troubleshooting: Quickly identify causes for application hangs, such as connection pool starvation or long-running transactions blocking schema migrations.
• Schema Design Review: Validate table structures before deployment to ensure they account for scaling and performance, such as avoiding locking operations during migrations.
• Performance Tuning: Optimize slow query patterns, identify missing indexes, and resolve N+1 issues commonly introduced by ORM lazy loading.
• Replication Strategy: Set up read-write splitting safely and configure reliable backups with point-in-time recovery.

Example Prompts

• "I'm experiencing intermittent application hangs on my PostgreSQL instance. Can you help me check if I'm hitting connection limits and how to implement a connection proxy like PgBouncer?"
• "I need to add a non-nullable column to a table with 50 million rows without causing a full table lock. What is the safest migration strategy?"
• "We are seeing stale data on our read-only replica. How can I measure replication lag and architect my application to gracefully handle read consistency?"

Tips & Limitations

The Database skill provides architectural design patterns and debugging strategies but does not have direct access to your database instances. It cannot execute SQL queries against your infrastructure. Always treat recommendations as advisory; test all migration strategies in a staging environment that mirrors your production data volume before executing on live systems. Ensure that you have adequate monitoring tools (like Prometheus or Datadog) installed alongside this skill to capture the metrics (e.g., lock wait times, CPU spikes) that the skill will ask you to analyze.