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
Cron safety rules: % escaping, bash -c wrapping, $ escaping, logging
% escaped in date
100%
80%
bash -c wrapper
0%
0%
$ escaped in eval
100%
60%
Full crontab line
100%
100%
Timestamped logging
0%
0%
Hardcoded log path
100%
100%
Caveman/Command style
100%
100%
No $VAR placeholders
100%
100%
Correct schedule
100%
100%
mongosh eval double-quoted
60%
0%
Check mode: Kafka port and advertised.listeners probe output
No prose preamble
0%
100%
No prose postamble
100%
100%
No mid-output explanatory lines
0%
100%
No comment lines
0%
100%
Two or more probe commands
100%
100%
Separate lines for each check
100%
100%
Port 9092 probe
100%
100%
advertised.listeners probe
100%
100%
No invented hostname as target
100%
100%