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".
38
37%
Does it follow best practices?
Impact
—
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 vague and padded with buzzwords like 'comprehensive guidance and automation' without specifying concrete capabilities. While it includes some useful trigger phrases, it fails to articulate what specific backup and recovery actions the skill performs, making it difficult to distinguish from other infrastructure-related skills.
Suggestions
Replace vague language with specific concrete actions, e.g., 'Schedules incremental and full backups, configures retention policies, restores files from snapshots, sets up automated disaster recovery failover.'
Expand trigger terms to include common variations like 'restore data', 'backup schedule', 'snapshot', 'failover', 'data loss', 'recovery plan', and 'RPO/RTO'.
Restructure with a clear 'Use when...' clause that specifies the exact scenarios, e.g., 'Use when the user needs to set up, manage, or troubleshoot backup schedules, restore lost data, or implement disaster recovery plans.'
| 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. No specific operations (e.g., schedule incremental backups, restore from snapshots, configure retention policies) are mentioned. | 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 shallow. | 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 mention of 'backup and recovery' and 'disaster recovery' provides some domain specificity, but the description is broad enough that it could overlap with infrastructure management, DevOps, or cloud administration skills. | 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-organized outline for FairDB backup management but critically lacks executable code, concrete scripts, or copy-paste-ready examples—making it more of a planning document than an actionable skill. The workflow sequence is logical but missing validation checkpoints between critical steps. The error handling table is a strength, but the overall content reads as abstract guidance rather than concrete instruction.
Suggestions
Add complete, executable backup and restore shell scripts with actual commands (tar, aws s3 cp, flock, checksum verification) rather than describing what the scripts should contain.
Insert explicit validation checkpoints between steps—e.g., 'Verify checksum matches before uploading to S3', 'Confirm S3 upload with aws s3 ls before marking backup complete'—and add a feedback loop for failures.
Replace the Examples section (which lists user prompts) with concrete input/output examples showing actual generated script snippets or cron entries.
Remove generic resource links (crontab.guru, rsync docs) that Claude already knows, and instead provide FairDB-specific configuration templates or reference files in a bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some unnecessary verbosity. The overview restates what the description already covers, the examples section describes prompts rather than providing executable examples, and the resources section links to generic external docs Claude already knows about. The error handling table is useful but could be tighter. | 2 / 3 |
Actionability | Despite describing a technical backup workflow, the skill provides zero executable code—no actual backup script, no restore script, no cron entries, no S3 lifecycle policy JSON. The instructions are a high-level numbered list of abstract steps ('Generate backup script', 'Configure S3 upload') that describe what to do rather than showing how. This is vague direction, not concrete executable guidance. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence and the error handling table adds some recovery guidance. However, there are no explicit validation checkpoints between steps (e.g., verify backup integrity before uploading to S3, confirm S3 upload success before proceeding). Step 9 mentions testing but there's no feedback loop for earlier steps involving destructive or batch operations. | 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 Output section promises multiple deliverables that could benefit from template files or separate reference documents, but none exist. | 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
69c73e9
- 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.