implementing-backup-strategies
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
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/backup-strategy-implementor/skills/implementing-backup-strategies/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 guide than an actionable skill for Claude. It describes what to do at a strategic level but lacks the concrete, executable scripts, commands, and code examples that would make it truly actionable. The error handling table is a useful reference, but the core instructions need executable code blocks and validation checkpoints to be effective.
Suggestions
Add complete, executable backup script examples (e.g., a full pg_dump-to-S3 script with error handling, logging, and lock files) rather than just mentioning tool flags inline.
Include a concrete cron entry or systemd timer/service unit file that can be directly used or adapted.
Add inline validation checkpoints within the workflow, such as 'After running pg_dump, verify: `pg_restore --list backup.dump | head` to confirm the dump is valid before uploading to S3.'
Replace the natural language 'Examples' section with actual input/output pairs showing a user request and the expected generated script or configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some unnecessary verbosity. The prerequisites section lists things Claude would know to check, and the 'Examples' section provides natural language prompts rather than executable examples. The overview could be tighter. | 2 / 3 |
Actionability | Despite mentioning specific tools and flags, the skill provides no executable code—no actual backup scripts, no cron entries, no systemd unit files. The instructions are a high-level checklist of abstract steps ('Inventory all data sources', 'Classify data by RPO') rather than concrete, copy-paste-ready commands or scripts. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence and include verification (step 8) and alerting (step 9). However, there are no explicit validation checkpoints between steps, no feedback loops for error recovery during the workflow itself, and the verification step is deferred to a weekly schedule rather than being integrated into the backup process. | 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, all content is monolithic in a single file. The detailed error handling table and resources could be split out, and the 'Examples' section provides prompts rather than linking to detailed example implementations. | 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.