What makes mysql-aiops notable?

1.4K downloads. Trust evidence available

How should mysql-aiops be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

mysql-aiops

Use this skill whenever the user needs to operate or troubleshoot a MySQL 8.x or MariaDB 10.6+ server as a DBA — a one-shot server health overview (version + flavor, connection headroom, replica role); server reads (global variables, status counters, databases, storage engines); activity (sessions/processlist, long-running queries, open InnoDB transactions, lock waits); query stats (performance_schema statement-digest top-N, EXPLAIN FORMAT=JSON); index health (unused indexes, redundant/duplicate indexes, cardinality); table health (sizes, data_free fragmentation, engine/row-format status); replication (replica IO/SQL thread state and lag, binlog/GTID status); four flagship analyses — slow-query RCA (worst digest + EXPLAIN → cited cause/action incl. full-scan and lock-time-dominant classification), InnoDB lock-wait & deadlock chain RCA (wait-for tree, root blocker, last deadlock parsed from SHOW ENGINE INNODB STATUS), replication lag RCA (thread state/error fields → cause+action), and table fragmentation analysis (data_free → OPTIMIZE candidates); and guarded writes (kill a session or query, OPTIMIZE/ANALYZE TABLE, create/drop an index, SET GLOBAL a variable, reset digest stats). Always use this skill for "mysql health check", "why is this query slow", "top queries by time", "EXPLAIN this", "table fragmentation", "which indexes are unused", "redundant index", "who is blocking whom", "deadlock", "kill the session holding the lock", "replication lag", "replica stopped", "seconds behind master/source", "OPTIMIZE this table", "create/drop an index", or "SET GLOBAL max_connections" when the context is a MySQL or MariaDB database. Do NOT use for PostgreSQL — use postgres-aiops. Do NOT use when the target is OT / industrial equipment (use industrial-aiops), a hypervisor, a storage appliance, a backup product, or a container/cluster orchestrator (negative routing hints only). Common MySQL/MariaDB DBA operations with a built-in governance harness (audit, policy, token budget, undo, risk-tiers). Behaviour is validated by a mock-based test suite; see docs/VERIFICATION.md for the live-verification checklist.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.4k

Updated

Oct 10, 2026

Version

0.10.4

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.4K downloadsadoption · observed Oct 10, 2026
Latest release: 0.10.4release · observed Sep 16, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:mysql-aiops

Install using `clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:mysql-aiops` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/zw008/mysql-aiops before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-zw008-mysql-aiops/snapshot"

Documentation

CLAWHUB

149,808 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: mysql-aiops
slug: mysql-aiops
displayName: "MySQL AIops"
summary: "Governed MySQL/MariaDB DBA ops: slow-query, lock-wait, replication & fragmentation RCA; 35 tools."
license: MIT
homepage: https://github.com/AIops-tools/MySQL-AIops
tags: [aiops, mcp, governance, mysql]
description: >
  Use this skill whenever the user needs to operate or troubleshoot a MySQL 8.x or MariaDB 10.6+ server as a DBA — a one-shot server health overview (version + flavor, connection headroom, replica role); server reads (global variables, status counters, databases, storage engines); activity (sessions/processlist, long-running queries, open InnoDB transactions, lock waits); query stats (performance_schema statement-digest top-N, EXPLAIN FORMAT=JSON); index health (unused indexes, redundant/duplicate indexes, cardinality); table health (sizes, data_free fragmentation, engine/row-format status); replication (replica IO/SQL thread state and lag, binlog/GTID status); four flagship analyses — slow-query RCA (worst digest + EXPLAIN → cited cause/action incl. full-scan and lock-time-dominant classification), InnoDB lock-wait & deadlock chain RCA (wait-for tree, root blocker, last deadlock parsed from SHOW ENGINE INNODB STATUS), replication lag RCA (thread state/error fields → cause+action), and table fragmentation analysis (data_free → OPTIMIZE candidates); and guarded writes (kill a session or query, OPTIMIZE/ANALYZE TABLE, create/drop an index, SET GLOBAL a variable, reset digest stats).
  Always use this skill for "mysql health check", "why is this query slow", "top queries by time", "EXPLAIN this", "table fragmentation", "which indexes are unused", "redundant index", "who is blocking whom", "deadlock", "kill the session holding the lock", "replication lag", "replica stopped", "seconds behind master/source", "OPTIMIZE this table", "create/drop an index", or "SET GLOBAL max_connections" when the context is a MySQL or MariaDB database.
  Do NOT use for PostgreSQL — use postgres-aiops. Do NOT use when the target is OT / industrial equipment (use industrial-aiops), a hypervisor, a storage appliance, a backup product, or a container/cluster orchestrator (negative routing hints only).
  Common MySQL/MariaDB DBA operations with a built-in governance harness (audit, policy, token budget, undo, risk-tiers). Behaviour is validated by a mock-based test suite; see docs/VERIFICATION.md for the live-verification checklist.
installer:
  kind: uv
  package: mysql-aiops
argument-hint: "[session id / table / index name or describe your DBA task]"
allowed-tools:
  - Bash
metadata: {"openclaw":{"requires":{"anyBins":["mysql-aiops","uvx"]},"optional":{"env":["MYSQL_AIOPS_CONFIG","MYSQL_AIOPS_MASTER_PASSWORD"]},"homepage":"https://github.com/AIops-tools/MySQL-AIops","emoji":"🐬","os":["macos","linux"]}}
compatibility: >
  Standalone, self-governed MySQL/MariaDB DBA operations. The governance harness (audit, policy, token/runaway budget, undo, risk-tiers) is bundled in the package — no

_meta.json

{
  "ownerId": "kn7b067awq2s97bn3d7p5qfhw5827pxc",
  "slug": "mysql-aiops",
  "version": "0.10.4",
  "publishedAt": 1789601168267
}

references/agent-guardrails.md

# Agent guardrails — running mysql-aiops with a smaller / local model

If you drive these tools with a local model (Llama, Qwen, Mistral … via Goose,
Ollama, LM Studio, or any OpenAI-compatible runtime), you will get noticeably
better results with a short system prompt. This page gives you one, and — more
importantly — tells you which guardrails you **no longer need to write**, because
the tool now enforces them itself.

The distinction matters. A guardrail in a prompt is a request. A guardrail in the
harness is a guarantee. Anything below that we could move into the harness, we did.

## What the tool now enforces — do not waste prompt budget on these

Authorization is not this tool's job — decide it via the account you connect with or the
agent's prompt, not via a switch this skill provides. See below for the account-side way to
get a read-only setup.

| You might be tempted to prompt | Why you don't need to |
|---|---|
| "Never write SQL that modifies data" | The tool exposes no arbitrary-SQL surface at all. Every statement is built from a fixed template; identifiers are validated against a strict charset and backtick-quoted, and values are always bound as query parameters. `explain_query` runs `EXPLAIN`, not your statement. |
| "Don't invent a value when a field is missing" | A NULL column comes back as `null`, never as `""`. A sleeping session's `query` is `null` (it is running nothing), not blank; MariaDB's absent `gtid_mode` is `null`, not `""`. |
| "Tell me if the output was cut off" | `top_queries`, `table_sizes`, `table_fragmentation` and `table_status` return `{"statements"/"tables": [...], "returned": N, "limit": L, "truncated": true/false}`. Truncation is measured — one extra row is requested — not guessed from a length coincidence. |
| "Make it show the number it judged on" | Every finding cites the values that tripped it — `noIndexUsedPct`, `rowsExaminedPerSent`, `lockTimePct`, `tmpDiskTables` and `calls` for a statement (the `worst` block additionally reports `meanTimeMs` and `totalTimeMs`, which no check is tripped by); `ioThreadRunning`, `sqlThreadRunning` and `secondsBehindSource` for a replica — so a claim can be checked against a figure rather than taken on the model's word. `lock_wait_rca` returns no findings at all: it gives you `roots` ordered by `blockedCount` plus `worstRootId`, which names the blocker outright. |
| "Confirm before anything destructive" | `drop_index`, `kill_query`/`kill_session` and `optimize_table` require a `--dry-run`-able preview plus double confirmation at the CLI. `drop_index` captures the index's `SHOW CREATE` definition first, so the undo token can recreate it exactly. |
| "Log what you did" | Every governed call is audited to `~/.mysql-aiops/audit.db` regardless of what the model says it did. |

## What still needs a prompt

These are model-behaviour problems the harness cannot fix from the outside.

⚠️ **Do not read priority off list position — except from `lock_wait_rca`.** `slow_query_rca`
an

references/capabilities.md

# mysql-aiops capabilities

> 35 MCP tools (26 read, 9 write); mock-validated, see `docs/VERIFICATION.md`. The
> `information_schema` / `performance_schema` queries are modelled from
> documented MySQL 8.x / MariaDB 10.6+ shapes and need live verification.
> `top_queries` / `slow_query_rca` require `performance_schema=ON`; the read
> account should have `PROCESS`, `REPLICATION CLIENT` and `SELECT` on
> `performance_schema`.

## Read tools (25)

| Tool | Source | Returns |
|------|--------|---------|
| `overview` | several reads (resilient) | version, flavor, uptimeDays, readOnly, role, connections{}, sessionsByCommand, longestQuery, mostFragmentedTable, secondsBehindSource |
| `server_version` | `version()`, `SHOW GLOBAL STATUS/VARIABLES` | version, flavor (mysql/mariadb), uptimeSeconds/Days, readOnly, superReadOnly, dataDirectory |
| `show_variables` | `SHOW GLOBAL VARIABLES` | name, value (optional LIKE filter) |
| `show_status` | `SHOW GLOBAL STATUS` | name, value (optional LIKE filter) |
| `list_databases` | `information_schema.tables` | name, tableCount, data/index/totalBytes, totalPretty |
| `list_engines` | `SHOW ENGINES` | engine, support, isDefault, transactions |
| `connection_stats` | `SHOW GLOBAL STATUS/VARIABLES` | maxConnections, threadsConnected/Running, maxUsedConnections, abortedConnects, usedPct |
| `list_sessions` | `information_schema.processlist` | total, byCommand, sleepingCount, sessions[] |
| `long_running_queries` | processlist | thresholdSeconds, count, queries[] (oldest first) |
| `list_transactions` | `information_schema.innodb_trx` | count, lockWaitCount, transactions[] (rowsLocked/Modified) |
| `lock_waits` | `performance_schema.data_lock_waits` (MariaDB: `information_schema.innodb_lock_waits`) | pairs[] {blockedId, blockingId, waitSeconds, queries} |
| `top_queries` | `events_statements_summary_by_digest` | statements[] (calls, total/mean ms, lockTimePct, noIndexUsedPct, rowsExaminedPerSent, tmpDiskTables) |
| `explain_query` | `EXPLAIN FORMAT=JSON` | plan (JSON; planned, not executed) |
| `unused_indexes` | `table_io_waits_summary_by_index_usage` | indexes[] with zero I/O since restart |
| `redundant_indexes` | `information_schema.statistics` | redundant[] {index, coveredBy, exactDuplicate} |
| `index_stats` | `information_schema.statistics` | indexes[] {columns, unique, cardinality} |
| `table_sizes` | `information_schema.tables` | tables[] data/index/totalBytes, engine, estRows |
| `table_fragmentation` | `information_schema.tables` | tables[] freeBytes (data_free), freePct |
| `table_status` | `information_schema.tables` | tables[] engine, rowFormat, autoIncrement, updateTime; nonInnodbTables[] |
| `replica_status` | `SHOW REPLICA STATUS` (MariaDB: `SHOW SLAVE STATUS`) | isReplica, replicas[] {ioThreadRunning, sqlThreadRunning, secondsBehindSource, lastIo/SqlError, gtid} |
| `binlog_status` | `SHOW BINARY LOGS` + variables + processlist | logBin, serverId, binlogFormat, gtidMode, binlogCount/TotalBytes, downstre

references/cli-reference.md

# mysql-aiops CLI reference

> The `information_schema` / `performance_schema` queries are modelled from documented
> MySQL 8.x / MariaDB 10.6+ shapes and are mock-validated; see `docs/VERIFICATION.md`
> for the live-run checklist.

## Setup & diagnostics

```bash
mysql-aiops init                      # interactive onboarding wizard
mysql-aiops doctor [--skip-auth]      # config + secrets + connectivity + flavor + perf-schema + replica role
mysql-aiops overview [--target <t>]   # one-shot server health snapshot
mysql-aiops mcp                       # start the MCP server (stdio transport)
```

## Secrets (encrypted store ~/.mysql-aiops/secrets.enc)

```bash
mysql-aiops secret set <target> [--value <pw>]    # store password (hidden prompt if no --value)
mysql-aiops secret list                            # names only — values never shown
mysql-aiops secret rm <target>
mysql-aiops secret migrate                         # import legacy plaintext .env (MYSQL_<T>_PASSWORD)
mysql-aiops secret rotate-password                 # re-encrypt under a new master password
```

## Read commands

```bash
mysql-aiops server version                 # version, flavor (mysql/mariadb), uptime, read_only
mysql-aiops server variables [pattern]     # SHOW GLOBAL VARIABLES (optional name filter)
mysql-aiops server status [pattern]        # SHOW GLOBAL STATUS (optional name filter)
mysql-aiops server databases               # schemas + sizes
mysql-aiops server engines                 # storage engines
mysql-aiops server connections             # headroom vs max_connections

mysql-aiops activity sessions [--no-sleeping]  # processlist + per-command counts
mysql-aiops activity long [--min-seconds 60]
mysql-aiops activity transactions          # open InnoDB transactions
mysql-aiops activity lock-waits            # wait-for edges (flavor-branched)

mysql-aiops query top [--order-by total_time] [--limit 20]   # statement digests
mysql-aiops query explain "<sql>"          # EXPLAIN FORMAT=JSON (planned, not executed)

mysql-aiops index unused                   # zero-I/O indexes since restart
mysql-aiops index redundant                # prefix-covered / duplicate indexes
mysql-aiops index stats                    # columns + cardinality

mysql-aiops table sizes
mysql-aiops table fragmentation            # data_free per table
mysql-aiops table status                   # engine / row format / update time

mysql-aiops repl status                    # replica threads + lag (flavor-branched)
mysql-aiops repl binlog                    # binlog/GTID + downstream replicas

mysql-aiops analyze slow-query [--explain "<sql>"]   # flagship RCA
mysql-aiops analyze lock-waits             # chain + last deadlock
mysql-aiops analyze replication            # lag/thread-state RCA
mysql-aiops analyze fragmentation          # OPTIMIZE candidates
```

## Write commands (governed; risk tier in parentheses)

```bash
mysql-aiops remediate kill <id> [--dry-run]                    # (high) KILL CONNECTIO

Github ReposUpdated 20h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.