CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/dr-drill-runner

The full DR-drill discipline for one service: author the runbook (per-tier RTO + RPO), pre-drill checklist (data sync state, alert silencing, customer comms), drill workflow (announce, fail-over, verify, fail-back) with timestamps, the supervised run protocol (refuse without declared RTO/RPO or against production, RTO/RPO monitoring cadence, abort-on-breach), and an auditor-ready post-drill report. Backup-integrity verification (SHA-256 + signature, restore spot checks, cross-region replication, retention, key recovery) and restore-time / RTO measurement (TTF segments, PITR latency, parallel-restore tuning, trend tracking) are worked in references. Per Google Cloud DR planning guide; covers cold / warm / hot standby tier-specific patterns. Use when a scheduled or post-incident failover drill for one service is being planned, executed, or written up, or when a new tier-1 service ships without a drill defined.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

92%Weight 40%Scale 1-5

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

A well-structured, highly actionable skill body with clear sequencing, strong validation checkpoints for a destructive operation, and clean one-level-deep reference files. The only minor gap is some conceptual framing and quoted external-guide prose that could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and task-oriented with concrete templates and tables, but includes some mild over-explanation of framing concepts ('DR planning requires end-to-end recovery design...') and quoted external-guide passages that could be trimmed. It is efficient with only minor padding, so it sits above the 3-anchor but below the lean 5-anchor.

4 / 5

Actionability

Provides copy-paste-ready templates (pre-drill checklist, drill workflow, post-drill report) plus concrete executable criteria: '60 s is a workable default' monitoring cadence, 'T-30 min' replication-lag check, SHA-256 backup integrity, and explicit abort conditions. Fully actionable guidance covering common cases, matching the 5-anchor.

5 / 5

Workflow Clarity

Sequenced as Steps 1-8 plus a five-stage run protocol with explicit validation checkpoints: 'Refuse to start when' preconditions, 'abort the failover, record the breach metrics' on RTO breach, and 'verify primary health before recording fail-back complete'. This destructive operation has feedback loops and checklists, matching the 5-anchor and clearing the destructive-validation cap.

5 / 5

Progressive Disclosure

Body is an overview with detailed material split into one-level-deep, clearly signaled references: references/backup-verification.md and references/restore-time.md (both real files), linked inline at the relevant steps. Clear section headers and well-organized navigation match the 5-anchor.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A specific, complete, and distinctive description that explicitly pairs a comprehensive 'what' with concrete 'Use when' triggers. Its only soft spot is trigger-term breadth, where a few common synonyms would round out coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with full coverage: 'author the runbook (per-tier RTO + RPO)', 'pre-drill checklist (data sync state, alert silencing, customer comms)', 'drill workflow (announce, fail-over, verify, fail-back)', 'abort-on-breach', plus detailed backup-verification and restore-time sub-tasks. It is comprehensive rather than having only minor gaps, so it clears the 4-anchor.

5 / 5

Completeness

Explicitly answers both: 'what' (the full DR-drill discipline enumerated across runbook, checklist, workflow, protocol, report) and 'when' ('Use when a scheduled or post-incident failover drill ... is being planned, executed, or written up, or when a new tier-1 service ships without a drill defined'). Matches the 5-anchor's what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrasing such as 'scheduled or post-incident failover drill' and 'new tier-1 service ships without a drill defined' with keywords like drill, failover, runbook, RTO, RPO. Coverage is good but a few common synonyms (disaster recovery, game day) are missing, so it sits just below the comprehensive 5-anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (one-service supervised DR-drill with refuse-against-production guardrails) and is distinguished from the chaos-drill skill via the rehearsed-vs-unrehearsed boundary. Triggers are specific and minimal conflict risk, matching the 5-anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents