planning-disaster-recovery
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill planning-disaster-recoveryExecute 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no disaster-recovery-specific content. It reads like a project management checklist that could apply to any IT task, lacking concrete backup commands, recovery procedures, RTO/RPO considerations, or actual disaster recovery tooling. The content wastes tokens on obvious guidance while providing nothing Claude couldn't generate from first principles.
Suggestions
Replace generic steps with specific disaster recovery procedures: backup commands (e.g., pg_dump, AWS Backup CLI), recovery verification scripts, and RTO/RPO testing workflows
Add executable code examples for common DR scenarios: database backup/restore, file system snapshots, cloud failover automation
Include concrete validation checkpoints: backup integrity verification commands, recovery time measurement, data consistency checks
Remove boilerplate prerequisites and error handling that Claude already knows; focus only on DR-specific gotchas and edge cases
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts Claude already knows (like 'verify credentials', 'test in non-production first') and contains no disaster-recovery-specific content that earns its token cost. | 1 / 3 |
Actionability | Entirely abstract and vague with no concrete code, commands, or specific examples. Instructions like 'Review current configuration' and 'Execute implementation' provide no executable guidance for actual disaster recovery tasks. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management phases rather than disaster recovery workflows. No specific validation checkpoints for backup verification, recovery testing, or RTO/RPO validation. | 2 / 3 |
Progressive Disclosure | References external files in a Resources section, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths ({baseDir}) and the 'Examples' section is empty, promising content 'in context' without delivering. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description attempts the right structure with trigger phrases but fails on specificity - it never explains what backup operations are actually supported. The phrase 'comprehensive guidance and automation' is empty fluff that provides no actionable information for skill selection.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'create incremental backups, schedule automated backup jobs, restore from snapshots, configure retention policies'
Add more trigger term variations including 'restore', 'backup schedule', 'data recovery', 'snapshot', 'backup retention', and specific targets like 'database backup' or 'file backup'
Specify what systems or data types this skill handles (databases, file systems, cloud storage, etc.) to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'comprehensive guidance and automation' without listing concrete actions. It doesn't specify what backup operations are supported (e.g., incremental backups, database dumps, file system snapshots). | 1 / 3 |
Completeness | Has a 'Use when' clause and trigger phrases addressing 'when', but the 'what' is extremely weak - 'backup automation and disaster recovery with comprehensive guidance' is too vague to understand actual capabilities. | 2 / 3 |
Trigger Term Quality | Includes some natural trigger phrases like 'create backups', 'automate backups', and 'implement disaster recovery', but misses common variations like 'restore', 'backup schedule', 'data recovery', 'snapshot', or specific backup targets. | 2 / 3 |
Distinctiveness Conflict Risk | The backup/disaster recovery domain is somewhat specific, but the vague description could overlap with database skills, cloud infrastructure skills, or general system administration skills that also handle backups. | 2 / 3 |
Total | 7 / 12 Passed |
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.