CtrlK
BlogDocsLog inGet started
Tessl Logo

planning-disaster-recovery

Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".

53

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/devops/disaster-recovery-planner/skills/planning-disaster-recovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

The body is well-structured, concise, and free of concept over-explanation, with a clear step sequence and a useful error-handling table. Its main weakness is actionability: guidance is directional rather than executable, and destructive failover steps lack explicit validation checkpoints.

Suggestions

Add concrete, copy-paste-ready commands or script snippets for the destructive steps (e.g., the exact aws cli / Terraform commands to promote a read replica and switch Route 53).

Insert explicit validation checkpoints between failover steps (promote replica -> verify replication state -> update DNS -> verify health check -> proceed).

Reference the bundled scripts (dr_plan_generator.py, config_validator.py, setup_code_generator.py) from the body so the existing bundle is discoverable.

DimensionReasoningScore

Conciseness

The body is lean and efficient, uses a compact error-handling table, and assumes Claude's competence without explaining basic DR or cloud concepts, matching the anchor for lean content where every token earns its place.

3 / 3

Actionability

Steps name concrete technologies (RDS cross-region read replicas, DynamoDB global tables, Route 53 health checks, Terraform) but stay directional ("Design the DR strategy", "Generate Terraform") with no executable commands or artifacts, fitting the anchor for some concrete guidance that is incomplete and missing key details.

2 / 3

Workflow Clarity

The 10 steps are clearly sequenced and drills (step 9) provide a validation loop, but destructive operations like replica promotion and DNS failover lack explicit verify-before-proceeding checkpoints, so per the rubric's feedback-loop rule workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

This is a compact single-purpose skill with well-organized sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), and the scoring notes allow a 3 for simple, well-organized skills even without external file references.

3 / 3

Total

10

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 identifies a clear domain and supplies natural trigger phrases, but it is padded with vague fluff, has a grammatically broken trigger clause, and lacks concrete capability detail. It lands in the middle of the rubric across all dimensions.

Suggestions

Rewrite the opening as clean third-person voice, e.g. "Designs disaster recovery plans..." and remove the malformed "Execute use when" phrasing.

Cut vague filler ("comprehensive guidance and automation") and replace it with concrete capabilities (e.g., generates DR runbooks, Terraform for standby infrastructure, automated failover scripts).

Expand trigger terms to include common user phrasings like "restore", "failover", "RTO/RPO", and "warm standby".

DimensionReasoningScore

Specificity

Names the domain and a couple of actions ("backup automation and disaster recovery") but pads with vague fluff ("comprehensive guidance and automation") and lists no concrete capabilities, matching the anchor that names a domain and some actions without being comprehensive.

2 / 3

Completeness

It answers both what and when, but the trigger clause is malformed ("Execute use when you need to work with backup and recovery") and the what is padded with fluff, so it does not clearly meet the explicit, clean trigger standard required for a 3.

2 / 3

Trigger Term Quality

Provides three natural trigger phrases ("create backups", "automate backups", "implement disaster recovery") but misses common variations a user would say such as "restore", "failover", or "RTO/RPO", fitting the anchor with some relevant keywords but missing common variations.

2 / 3

Distinctiveness Conflict Risk

The disaster-recovery niche is somewhat specific, but "backup and recovery" is broad enough to overlap with general backup/restore skills, fitting the anchor for a somewhat specific description that could still overlap with similar skills.

2 / 3

Total

8

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.