CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/dr-drill-runner

Author and execute a single DR drill 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, standby verification, failback, and an auditor-ready post-drill report. Per Google Cloud DR planning guide; covers cold / warm / hot standby tier-specific patterns. For coordinating drills across multiple services or teams, use a multi-service drill orchestrator. 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.

79

Quality

99%

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

100%

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

A well-crafted runbook-authoring skill: lean, highly actionable templates, a clearly sequenced workflow with explicit validation and decision checkpoints, and clean one-level-deep references. No bundle files are present, but the single-file structure is appropriate and well-organized for this skill.

DimensionReasoningScore

Conciseness

Lean and efficient — it defers detail to the Google Cloud guide rather than reproducing it, and templates/tables earn their tokens; the small RTO/RPO and cold/warm/hot restatements are compact and tied to tier-specific numbers, not padded prose.

3 / 3

Actionability

Provides copy-paste-ready material: a real pre-drill checklist with checkboxes, a timestamped drill workflow, and a full example post-drill report with timeline, issues, and owners/dates, plus an anti-patterns table with fixes.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Steps 1–8; T-0 → fail-over → Verify → Fail-back → Cleanup) with explicit validation checkpoints — verification suite, actual-vs-expected RTO comparison with an abort/continue decision, and failback health verification before completion.

3 / 3

Progressive Disclosure

Self-contained and well-organized with clear sections; the only references (sister skills and the Google Cloud guide) are one level deep and clearly signaled in a References section, with no nested pointer chains.

3 / 3

Total

12

/

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.

A strong, specific description that covers concrete capabilities, natural trigger terms, an explicit when-to-use clause, and a clear distinctiveness boundary. Voice is appropriately third-person with no first/second-person phrasing.

DimensionReasoningScore

Specificity

Lists many concrete actions — '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)... post-drill report' — matching the multiple-specific-actions anchor, well above the score-2 'some actions' bar.

3 / 3

Completeness

Explicitly answers both what ('Author and execute a single DR drill') 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'), with an explicit Use-when clause rather than mere implication.

3 / 3

Trigger Term Quality

Natural DR terms a user would say — 'DR drill', 'failover drill', 'runbook', 'RTO/RPO', 'tier-1 service', 'disaster recovery' — give good coverage without relying on jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Clear single-service niche with an explicit carve-out ('For coordinating drills across multiple services or teams, use a multi-service drill orchestrator'), making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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