fairdb-backup-manager
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill fairdb-backup-managerManage 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 provides abstract project management steps that could apply to any task, with zero executable code, no fairdb-specific commands, and no concrete backup/recovery procedures. The skill fails to teach Claude anything it doesn't already know about general software development practices.
Suggestions
Add concrete fairdb backup commands with executable examples (e.g., `fairdb backup create --target /path/to/backup`)
Include specific backup verification steps with actual validation commands and expected outputs
Remove generic prerequisites and replace with fairdb-specific requirements (connection strings, authentication methods, storage configuration)
Add concrete disaster recovery procedures with step-by-step restore commands and validation checks
| 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 'backup of critical data before making structural changes' and 'understanding of the system architecture' are obvious padding. | 1 / 3 |
Actionability | No concrete code, commands, or backup-specific examples. Everything is abstract guidance like 'Execute implementation in non-production environment first' with zero executable content for fairdb backup operations. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management steps, not backup-specific workflows. No validation commands, no specific checkpoints for backup verification, no concrete feedback loops for backup integrity checks. | 2 / 3 |
Progressive Disclosure | References external files appropriately (templates, docs, examples directories), but the main content is a wall of generic text. The referenced files use placeholder paths with no indication of actual content structure. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vague capability statements and relies on buzzwords like 'comprehensive guidance and automation' without explaining concrete actions. While it includes trigger phrases, the lack of specific operations (what types of backups, what systems, what recovery procedures) makes it difficult to distinguish from other potential backup-related skills.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'create scheduled backups, configure retention policies, restore from snapshots, verify backup integrity'
Add more natural trigger term variations users might say: 'restore data', 'backup schedule', 'recovery plan', 'rollback', 'data protection'
Specify the target systems or platforms (e.g., 'for Linux servers', 'for cloud storage', 'for databases') to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'backup automation and disaster recovery with comprehensive guidance and automation' without listing concrete actions. It doesn't specify what backup operations are supported (e.g., incremental backups, snapshot creation, restore procedures). | 1 / 3 |
Completeness | Has a 'Use when' clause and trigger phrases addressing 'when', but the 'what' is weak - 'comprehensive guidance and automation' is vague fluff that doesn't explain actual capabilities. The description doesn't clearly answer what specific actions the skill performs. | 2 / 3 |
Trigger Term Quality | Includes some natural trigger phrases like 'create backups', 'automate backups', and 'implement disaster recovery', but missing common variations users might say like 'restore', 'backup schedule', 'data recovery', 'backup files', or 'rollback'. | 2 / 3 |
Distinctiveness Conflict Risk | The backup/disaster recovery domain is somewhat specific, but 'backup and recovery' could overlap with database-specific backup skills, cloud backup tools, or system administration skills. Lacks specificity about what systems or platforms it targets. | 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.