implementing-backup-strategies
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill implementing-backup-strategiesExecute 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 backup-specific content. It reads like a fill-in-the-blank project management checklist rather than actionable guidance for implementing backup strategies. There are no concrete backup tools (rsync, restic, borgbackup), no example backup scripts, no retention policy guidance, and no disaster recovery procedures.
Suggestions
Add concrete backup tool examples with executable code (e.g., rsync commands, restic backup scripts, cron job configurations)
Include specific backup validation steps like 'verify backup integrity with checksums' and 'test restore to staging environment'
Provide example retention policies, backup schedules, and storage tier recommendations
Remove generic project management boilerplate and focus on backup-specific guidance Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no backup-specific information Claude doesn't already know - phrases like 'Review current configuration' and 'Identify specific requirements' are padding without substance. | 1 / 3 |
Actionability | No concrete code, commands, or backup-specific examples. Everything is abstract guidance like 'Execute implementation' and 'Run comprehensive tests' without any actual backup tools, scripts, or configurations. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management steps, not backup-specific workflows. No validation checkpoints specific to backup operations (e.g., verify backup integrity, test restore procedures). | 2 / 3 |
Progressive Disclosure | References external files for templates, docs, and examples, but the main content is a wall of generic text. The referenced files use placeholder paths that may not exist, and the structure doesn't help navigate backup-specific concerns. | 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.