SQL

What This Skill Does

The SQL skill empowers OpenClaw to become a sophisticated database administrator and data engineer. It provides the agent with the internal logic to handle schema design, efficient querying, migration planning, and performance tuning for major relational database engines including PostgreSQL, MySQL, SQLite, and SQL Server. Rather than just writing syntax, the skill enforces industry-standard best practices such as parameterized queries to prevent SQL injection, the proper use of transactions to ensure ACID compliance, and strategic indexing to optimize read performance. It acts as an expert consultant for translating natural language requirements into optimized relational structures.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface. Run the following command in your terminal:

clawhub install openclaw/skills/skills/ivangdavila/sql

Use Cases

• Schema Architecture: Designing normalized tables for new applications, defining relationships (one-to-many, many-to-many), and determining appropriate data types.
• Performance Auditing: Analyzing slow-running queries and identifying missing indexes or inefficient table scans.
• Data Migration: Generating SQL scripts to transform data schemas during application version upgrades.
• Operational Maintenance: Managing database backups, checking storage health, and executing bulk imports/exports safely.
• Security Hardening: Identifying potential risks like SQL injection vulnerabilities and refactoring code to use safe parameterization.

Example Prompts

1. "Analyze this schema design for a multi-tenant e-commerce app and suggest indexing strategies for the orders table to optimize search by user_id and created_at."
2. "Write a PostgreSQL migration script to safely add a non-nullable column with a default value to an existing users table with 10 million rows."
3. "Refactor this query to use EXISTS instead of IN and explain why this improves performance for large datasets."

Tips & Limitations

To get the best results, always define the database engine (e.g., MySQL vs. PostgreSQL) in your prompt, as syntax variations exist. Be mindful that while the agent can suggest complex queries, you must verify execution permissions and environment connectivity. Avoid running destructive commands like DROP TABLE in production environments without explicit confirmation. Remember that while indexing improves read speed, excessive indexes on a write-heavy table can decrease performance; always balance your design choices.