fairdb-backup-manager
Manage 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/fairdb-operations-kit/skills/fairdb-backup-manager/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 is overly vague and relies on buzzwords like 'comprehensive guidance and automation' without specifying concrete actions or tools. While it includes some useful trigger phrases, the lack of specific capabilities and the awkward phrasing of the 'use when' clause significantly weaken its effectiveness for skill selection among many options.
Suggestions
Replace vague language with specific concrete actions, e.g., 'Schedule incremental and full backups, configure retention policies, restore files from snapshots, set up disaster recovery failover plans.'
Add a clear 'Use when...' clause with broader trigger coverage, e.g., 'Use when the user asks about backup schedules, data restoration, snapshots, failover, replication, or disaster recovery planning.'
Remove filler phrases like 'comprehensive guidance and automation' and the awkward opening 'Manage use when you need to work with' — use third-person declarative voice instead.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage,' 'work with backup and recovery,' and 'comprehensive guidance and automation' without listing any concrete actions. There are no specific capabilities such as 'schedule incremental backups,' 'restore from snapshots,' or 'configure replication.' | 1 / 3 |
Completeness | It attempts to answer both 'what' and 'when' — the 'what' is vague ('backup automation and disaster recovery') and the 'when' is partially addressed via the trigger phrases. However, the 'Use when' guidance is embedded awkwardly ('Manage use when you need to work with backup and recovery') rather than being an explicit, clear clause. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger phrases like 'create backups,' 'automate backups,' and 'implement disaster recovery,' which are natural terms users might say. However, it misses common variations like 'restore,' 'snapshot,' 'backup schedule,' 'data recovery,' or 'failover.' | 2 / 3 |
Distinctiveness Conflict Risk | The domain of 'backup and recovery' is somewhat specific, but the description is so vague that it could overlap with infrastructure management, DevOps, database administration, or cloud management skills. The trigger terms help narrow it slightly but not enough to be clearly distinct. | 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 provides a well-structured overview of backup and recovery operations for FairDB but critically lacks any executable code examples, which is its biggest weakness. The instructions read as a high-level project plan rather than actionable guidance Claude can follow to produce concrete outputs. The error handling table adds value, but the skill would benefit enormously from actual script templates and validation checkpoints.
Suggestions
Add complete, executable backup and restore shell script examples with actual commands (tar, aws s3 cp, flock, checksum verification) rather than just describing what the scripts should do.
Include a concrete cron entry example and a sample S3 lifecycle policy JSON to match the promised outputs.
Add explicit validation checkpoints within the workflow, e.g., 'After step 3, verify checksum: `sha256sum -c backup.sha256` — only proceed if verification passes.'
Consider creating bundle files (e.g., backup_template.sh, restore_template.sh, s3_lifecycle.json) and referencing them from the SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some unnecessary verbosity. The prerequisites section explains things Claude would know (like what tar and rsync are), and the examples section describes use cases rather than providing executable examples. The error handling table is useful but could be more concise. | 2 / 3 |
Actionability | Despite describing a backup automation skill, there are zero executable code examples—no actual backup script, no restore script, no cron entry, no S3 lifecycle policy JSON. The instructions are a high-level numbered list of abstract steps ('Generate backup script', 'Configure S3 upload') without any concrete, copy-paste-ready code or commands. | 1 / 3 |
Workflow Clarity | The 9-step workflow provides a clear sequence and step 9 mentions testing the restore procedure, which is good. However, there are no explicit validation checkpoints between steps (e.g., verify backup integrity before uploading to S3, validate lock acquisition succeeded before proceeding). For a destructive/batch operation like backup and restore, the lack of inline feedback loops caps this at 2. | 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 inline in a single file. The Resources section links to external docs but there are no companion files for the detailed scripts, restore runbooks, or configuration templates that the skill promises to generate. | 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.