CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.12x
Quality

91%

Does it follow best practices?

Impact

80%

1.12x

Average score across 2 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and workflow-clear with concrete commands and validation checkpoints, but it is a monolithic single file with no reference bundles, and the routing/connector material is somewhat redundant, costing points on conciseness and progressive disclosure.

Suggestions

Dedupe the tech→connector mapping so it appears once (either the Routing table or the Connectors section) to tighten conciseness.

Split the per-connector tool details (context7/deepwiki/ClickHouse) into a references/ file linked one level deep to improve progressive disclosure and shorten the overview.

Consider moving the per-tech routing table into a reference file, keeping SKILL.md as a concise overview that signals where detail lives.

DimensionReasoningScore

Conciseness

Mostly lean and free of explaining concepts Claude already knows, but the Routing table and Connectors section repeat the same tech→connector mapping, and at ~120 lines some passages could be tightened; not the every-token-earns-its-place level 3.

2 / 3

Actionability

Concrete executable commands and config throughout — `find /opt/kafka/logs -name '*.log.2*' -mtime +7 -delete`, `sudo ss -ltnp | grep 9092`, `listeners=PLAINTEXT://:9092` — with exact connector tool chains; copy-paste ready, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced (output-mode precedence, root-cause→search→fix diagnosis, the 5-step Explainer with probe→decision tree) with validation checkpoints and feedback loops for destructive ops (dry-run `-delete`→`-print`), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and all material lives inline in one ~120-line file; sections are well organized, but routing/connector detail that could be split out is inline with no one-level-deep references, so it sits at the some-structure-but-could-be-split level 2 rather than the split-with-navigation level 3.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, triggers-rich, complete on both what and when, and occupies a clearly distinct DBA/infra niche. It is somewhat dense/long, but every clause earns its place and there is no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Troubleshoot database/infra errors; compose commands/scripts; write runbooks/tutorials; capacity planning' — plus a named tech surface, matching the multiple-specific-actions anchor rather than the single-action level 2.

3 / 3

Completeness

Explicitly answers both what (troubleshoot/compose/write runbooks/capacity planning) and when ('Trigger on DBA/SysOps/DevOps/infra work …' plus a Phrases list), satisfying the both-what-and-when anchor; not capped at 2 because explicit trigger guidance is present.

3 / 3

Trigger Term Quality

Strong coverage of natural phrases users say: 'fix this cron', 'how to restore/enable', 'log rotation', 'pasted DB errors, stack traces', 'DBA/SysOps/DevOps' — matching the good-coverage anchor rather than the partial-coverage level 2.

3 / 3

Distinctiveness Conflict Risk

A clearly delineated DBA/infra-ops niche with a named tech list and distinct trigger phrases, making accidental triggering of unrelated skills unlikely; it is not the level-2 'works with document files' style of generic overlap.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents