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".
38
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/disaster-recovery-planner/skills/planning-disaster-recovery/SKILL.mdQuality
Discovery
40%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 (backup and recovery) and includes some trigger phrases, but it is severely lacking in specificity about what concrete actions the skill performs. The language is padded with vague terms like 'comprehensive guidance and automation' without detailing actual capabilities such as scheduling, restoring, verifying, or managing specific backup types.
Suggestions
Replace vague phrases like 'comprehensive guidance and automation' with specific concrete actions (e.g., 'Schedule automated backups, configure retention policies, restore from snapshots, verify backup integrity').
Expand trigger terms to include common variations users would say, such as 'restore data', 'backup schedule', 'snapshot', 'data loss', 'backup strategy', and specific technologies if applicable.
Specify the scope more clearly—what types of backups (database, filesystem, cloud storage), what platforms or tools are supported—to reduce conflict risk with other potential backup-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'backup automation and disaster recovery with comprehensive guidance and automation.' It does not list specific concrete actions—there's no mention of what it actually does (e.g., schedule cron jobs, snapshot databases, restore from backups, verify backup integrity). | 1 / 3 |
Completeness | It has a weak 'what' (backup automation and disaster recovery) and does include trigger phrases serving as a 'when' clause. However, the 'what' is so vague that the completeness is undermined—it doesn't clearly explain what the skill actually does beyond the domain name. | 2 / 3 |
Trigger Term Quality | It includes some natural trigger phrases like 'create backups', 'automate backups', and 'implement disaster recovery', which users might say. However, it misses common variations like 'restore', 'snapshot', 'backup schedule', 'data recovery', 'backup strategy', or specific tools/technologies. | 2 / 3 |
Distinctiveness Conflict Risk | The domain of 'backup and recovery' is somewhat specific, but the description is so generic within that domain that it could overlap with any backup-related skill. It doesn't specify what kind of backups (database, filesystem, cloud), what platforms, or what tools, making it hard to distinguish from similar skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level planning checklist than an actionable skill for Claude. While it covers the DR planning domain comprehensively with good error handling and clear structure, it critically lacks any concrete, executable code examples—no Terraform snippets, no CLI commands, no script templates. The instructions describe what to do at an abstract level but never show how to do it, which severely limits Claude's ability to act on this guidance.
Suggestions
Add concrete, executable Terraform snippets for standby infrastructure (e.g., a minimal VPC + RDS read replica module) instead of just saying 'Generate Terraform for standby region'.
Include actual failover script examples (e.g., AWS CLI commands for promoting an RDS read replica, updating Route 53 records) to make the workflow actionable.
Add explicit validation checkpoints between steps, such as 'Verify replication status with `aws rds describe-db-instances` before proceeding to DNS configuration'.
Replace the prompt-style examples with concrete input/output pairs showing what Claude should actually produce (e.g., a sample DR runbook section or a sample Terraform module).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some unnecessary verbosity. The 'Examples' section just lists prompt phrases rather than showing concrete input/output pairs. The overview restates what the instructions already convey. Some sections like Prerequisites explain things Claude would know to check. | 2 / 3 |
Actionability | Despite listing 10 steps, the skill provides no executable code, no Terraform snippets, no actual failover scripts, and no concrete commands. Every instruction is a high-level description ('Generate Terraform for...', 'Configure database replication...') rather than actionable, copy-paste-ready guidance. The examples section lists prompts rather than showing actual outputs. | 1 / 3 |
Workflow Clarity | The 10 steps provide a reasonable sequence and the error handling table adds useful troubleshooting guidance. However, there are no explicit validation checkpoints between steps (e.g., verify replication is healthy before proceeding to DNS failover setup), and no feedback loops for error recovery within the workflow itself. | 2 / 3 |
Progressive Disclosure | The content is organized into clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) which is good structure. However, with no bundle files, the skill is a monolithic document that would benefit from splitting detailed content (e.g., Terraform modules, failover scripts, runbook templates) into separate referenced files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
69c73e9
- 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.