dba-ops-skill/dba-ops-runbook
Troubleshoot database/infra errors, compose commands/scripts, write runbook tutorials, capacity planning for DBA, SysOps, DevOps. Covers PostgreSQL, MongoDB, MySQL, ClickHouse, Apache Kafka, RabbitMQ, Linux log management, cron, logrotate. Uses MCP connectors (context7, deepwiki, ClickHouse Docs) for up-to-date official docs. Command and Script output is caveman-compressed (telegraphic prose, byte-exact code); Tutorial and Plan stay full prose. Trigger whenever the user mentions DBA, SysOps, DevOps, or infrastructure — error diagnosis, shell commands/scripts, cron expressions, log rotation, capacity estimation, migration planning, access/auth troubleshooting, or any operational database/infrastructure task. Also trigger on pasted database errors, stack traces, or log snippets. Trigger phrases: "compose a tutorial", "write a runbook", "fix this cron", "how to restore/enable", "compose a command/script", topic sizing, retention, partitions, replication, cluster planning.
83
91%
Does it follow best practices?
Impact
80%
1.12xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
task.mdevals/scenario-2/
Kafka Broker Pre-flight Verification
Problem Description
The platform team has provisioned a new Apache Kafka broker node as part of a cluster expansion. Before the broker is added to the consumer bootstrap server lists, the on-call engineer needs to confirm it is ready to accept connections.
You've been asked to check whether Kafka is listening on port 9092 on this broker, and to verify that the advertised.listeners setting in the broker's configuration file is correctly set. Misconfigurations in either are the most common cause of consumer connectivity failures after a new broker comes online — the process can appear healthy while silently rejecting remote connections.
Output Specification
Write your output to check_output.txt. The file should contain the commands to perform these two pre-flight checks on the broker host.