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".
48
37%
Does it follow best practices?
Impact
Pending
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.
This description suffers from vagueness and lack of concrete actions. While it identifies the backup/recovery domain and includes some trigger phrases, it reads as generic filler rather than a precise capability description. The phrase 'comprehensive guidance and automation' is buzzword-heavy without substance.
Suggestions
Replace vague language with specific concrete actions, e.g., 'Creates scheduled backup scripts, configures incremental/full backup strategies, sets up automated restore procedures for databases and file systems.'
Expand trigger terms to include common variations like 'restore data', 'backup schedule', 'snapshot', 'rollback', 'data loss prevention', and specific technologies if applicable.
Specify the scope more clearly (e.g., which systems, platforms, or backup tools) to reduce overlap with other infrastructure or DevOps skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'comprehensive guidance and automation' and 'work with backup and recovery' without listing any concrete actions. It doesn't specify what kinds of backups, what systems, or what specific operations are performed. | 1 / 3 |
Completeness | It has a weak 'what' (backup automation and disaster recovery) and does include trigger phrases serving as a 'when' clause, but the 'what' is too vague to be truly useful. The trigger phrases partially compensate but the overall guidance is thin. | 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', 'rollback', or specific backup targets. | 2 / 3 |
Distinctiveness Conflict Risk | The backup and disaster recovery domain is somewhat specific, but the description is so vague that it could overlap with infrastructure management, DevOps, or database administration skills. It doesn't clarify what type of backups (database, file system, cloud) or what platforms. | 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. Its greatest weakness is the complete absence of executable code—no Terraform snippets, no failover scripts, no CLI commands—despite promising all of these as outputs. The error handling table is a strength, but the skill fundamentally describes what to do rather than showing how to do it.
Suggestions
Add concrete, executable Terraform snippets for at least the standby VPC/subnet setup and a database read replica, rather than just saying 'Generate Terraform for standby region infrastructure'.
Include an actual failover script example (e.g., a bash script that promotes an RDS read replica and updates Route 53 records) to make the skill actionable.
Add explicit validation checkpoints between critical steps, such as 'Verify replication status shows 0 lag before proceeding to DNS failover configuration'.
Create bundle files for the Terraform modules, failover scripts, and DR runbook template referenced in the Output section, and link to them from the skill body.
| 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 'Resources' section with external URLs adds tokens without much actionable value for Claude. The overview restates what the instructions already convey. | 2 / 3 |
Actionability | Despite listing 10 steps, the skill provides zero executable code, no Terraform snippets, no actual failover scripts, and no concrete commands. Every instruction is descriptive ('Generate Terraform for...', 'Configure database replication...') rather than providing copy-paste ready artifacts. The examples section lists prompts rather than showing actual outputs. | 1 / 3 |
Workflow Clarity | The 10 steps are logically sequenced and the error handling table provides useful troubleshooting guidance. However, there are no explicit validation checkpoints between steps (e.g., 'verify replication is active before proceeding to DNS failover'), and the DR drill step (step 9) lacks a feedback loop for fixing discovered gaps before proceeding. | 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 detailed Terraform modules, failover scripts, and runbook templates mentioned in the Output section have nowhere to live. The skill would benefit from referencing separate files for these substantial artifacts. | 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
3a2d27d
- 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.