SQL Optimizer for Openclaw

No external package installation is required; SQL Optimizer is an agent-created Openclaw Skills capability. Provide the following context in the request for the most reliable result:

1. Identify the target database dialect and version.
2. Include the business requirement or current SQL query.
3. Provide table names, columns, data types, relationships, existing indexes, and approximate row counts.
4. Include an execution plan when diagnosing a slow query.
5. State pagination, consistency, read/write separation, and production-safety requirements.

Example request:

cat <<'REQUEST'
Database: PostgreSQL 16
Goal: List the 20 most recent paid orders for a customer.
Tables: orders(id bigint, customer_id bigint, status text, created_at timestamp)
Indexes: orders_customer_id_status_created_at_idx(customer_id, status, created_at)
Please write the query, review index usage, and explain how to validate it.
REQUEST

For validation, run the generated query in a safe environment with the target database's native plan command:

# PostgreSQL
EXPLAIN (ANALYZE, BUFFERS) <query>;

# MySQL
EXPLAIN ANALYZE <query>;

Never apply generated UPDATE, DELETE, or DDL statements directly to production without previewing affected rows, checking the execution plan, using an appropriate transaction or backup, and reviewing locking and rollback behavior.

SQL Optimizer organizes its analysis around the following logical data model:

The skill does not require or imply generated files, migrations, database connections, or persistent storage. Its primary output is a structured response containing SQL, assumptions, recommendations, and validation steps.