MySQL Schema Best Practice Generator for Openclaw

This skill is primarily a static specification generator and reviewer. It does not require an external MCP service or a live MySQL connection.

1. Install or enable the skill in the OpenClaw Skills environment using your platform's standard skill installation flow.
2. Provide either a structured generate request or a review request.
3. For generation, include the database name, tables, columns, keys, indexes, relationships, optional partitions, naming rules, and collation settings.
4. For review, provide the original DDL and, when available, workload, data-size, and peak-QPS context.
5. Execute and test returned DDL in a controlled MySQL 8.0+ environment before production rollout.

Example generation payload:

cat > schema-request.json <<'JSON'
{
  "mode": "generate",
  "db_name": "app_db",
  "tables": [
    {
      "table": "users",
      "comment": "Application users",
      "columns": [
        {
          "name": "id",
          "type": "BIGINT UNSIGNED",
          "nullable": false,
          "pk": true,
          "auto_increment": true,
          "comment": "Surrogate primary key"
        },
        {
          "name": "email",
          "type": "VARCHAR",
          "length": 255,
          "nullable": false,
          "unique": true,
          "comment": "User email address"
        }
      ]
    }
  ],
  "naming": {"snake_case": true, "lowercase": true},
  "collation": {"charset": "utf8mb4", "collate": "utf8mb4_0900_ai_ci"}
}
JSON

Optional SQL formatting can use an available sql-formatter MCP server. The skill should first check capabilities, add the configured server if needed, call format_sql, and fall back to built-in formatting when the tool is unavailable.

Generation input

Review input

• mode: Must be review.
• ddl: Original MySQL DDL string.
• context: Optional workload such as OLTP, OLAP, or mixed; expected data_size; and peak qps.

Output structure

• ddl: Executable generated SQL containing database, tables, comments, indexes, constraints, and required table options.
• issues: Review findings with level, item, detail, fix, and optional example SQL.
• fixed_ddl: Corrected DDL when automatic repair is possible.
• checklist: Standards and release-validation items.
• rationale: Key design tradeoffs and decisions.
• migration_notes: Deployment and rollback guidance.
• risk_warnings: Potential data, locking, compatibility, or performance risks.

Default metadata conventions include ENGINE=InnoDB, utf8mb4, utf8mb4_0900_ai_ci, ROW_FORMAT=DYNAMIC, UTC-aware timestamp handling, created_at, updated_at, created_by, updated_by, and optional indexed deleted_at for soft deletion. Names should use lowercase snake_case with pk_, uk_, idx_, and fk_ prefixes.