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".

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/devops/fairdb-operations-kit/skills/fairdb-backup-manager/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-structured instruction skill with a clear sequenced workflow, validation checkpoints, and an error-recovery table. Its main weakness is actionability: it specifies the generic wrapping (tar/S3/cron/retention) but omits the actual FairDB dump and restore commands that the skill's name implies.

Suggestions

Add the concrete FairDB backup/dump and restore/import commands (CLI invocation and key flags) so the generated scripts are complete and executable rather than just described.

Optionally provide a minimal example backup-script template so Claude has a copy-paste-ready starting point.

Clarify the restore feedback loop inline (verify checksum -> if mismatch, re-download -> retry import) rather than only in the separate error table.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) with no padding or explanations of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It gives concrete wrapping commands and parameters (tar czf, aws s3 cp --sse aws:kms, flock, retention values, /var/log/fairdb-backup.log) but is incomplete on the FairDB-specific dump/restore commands, a key missing detail for a skill named after FairDB.	2 / 3
Workflow Clarity	The 9-step Instructions sequence is clearly ordered and includes explicit validation (checksum verification, validation query, staging restore test) with error-recovery feedback paths in the Error Handling table, satisfying the validation requirement for destructive database operations.	3 / 3
Progressive Disclosure	It is a compact (~57-line) single-file skill organized into clear sections with no need for external references; the bundle directories hold only generic template READMEs and are not referenced, so the simple-skill well-organized-sections path applies.	3 / 3
	Total	11 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 answers both what and when with explicit trigger phrases, but it is undermined by a grammatically broken opening ('Manage use when...'), second-person voice, missing 'restore' triggers, and no FairDB scoping to distinguish it from general backup skills.

Suggestions

Fix the broken opening sentence and lead with a clean third-person capability statement (e.g., 'Automates FairDB backup and recovery operations, including script generation, retention scheduling, and tested restores.').

Add 'restore'/'recover'/'recovery plan' as trigger phrases, since restore is a core user intent for a backup skill.

Mention FairDB in the description so the skill is clearly distinguishable from generic backup skills.

Dimension	Reasoning	Score
Specificity	It names the domain and some actions ('backup automation and disaster recovery', 'create backups', 'automate backups', 'implement disaster recovery') but not comprehensive distinct actions, which is a base of 2; the description uses second person ('Manage use when you need to work with backup and recovery.'), which per the rubric guidelines reduces specificity by 1.	1 / 3
Completeness	It explicitly answers both what ('This skill provides backup automation and disaster recovery') and when (explicit 'Trigger with phrases like...' guidance plus a 'use when you need to work with backup and recovery' clause), so it is not capped at 2 for missing triggers.	3 / 3
Trigger Term Quality	It includes several natural trigger phrases ('create backups', 'automate backups', 'implement disaster recovery', 'backup and recovery') but misses common variations a user would say, most notably 'restore'/'recover from backup' and 'data protection'.	2 / 3
Distinctiveness Conflict Risk	The backup/recovery niche is somewhat specific with distinct triggers, but the description never mentions FairDB scoping, so it could overlap with generic backup skills and trigger for the wrong one.	2 / 3
	Total	8 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/fairdb-operations-kit/skills/fairdb-backup-manager/SKILL.md
Commit: c4eafaf

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.