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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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 lean, well-sequenced runbook with genuine validation checkpoints and a useful error-recovery table, but it stops at describing scripts rather than shipping executable ones, and it fails to use the bundle directories for progressive disclosure. Actionability and progressive disclosure are the weakest dimensions.

Suggestions

Provide a complete, executable backup script (and restore script) rather than only describing the steps and command fragments, so guidance is copy-paste ready.

Move the error-handling table, examples, and detailed retention policy into files under references/ and link to them from the body so the bundle is actually used.

Replace the boilerplate READMEs in references/, scripts/, and assets/ with the real referenced materials, or signal clearly that they are optional.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — it never explains what tar, rsync, S3, or backups are, and each section (Overview, Prerequisites, Instructions, Error Handling) earns its place. Not 2 because there is no padded concept explanation to tighten.	3 / 3
Actionability	It gives concrete command fragments ('tar czf', 'aws s3 cp --sse aws:kms', 'flock') and specific retention values, but instructs Claude to 'Generate backup script' without providing a complete, copy-paste-ready script. Not 3 because no fully executable code is included; not 1 because specific commands and details are present.	2 / 3
Workflow Clarity	A clear 9-step sequence includes explicit validation checkpoints (checksum verification, validation query, staging restore test) and an error-handling table that provides fix-and-retry feedback loops. Not 2 because validation is explicit, not merely implied.	3 / 3
Progressive Disclosure	Sections are well organized, but the provided references/, scripts/, and assets/ directories contain only boilerplate READMEs and are never referenced from the body; content that could be split (error handling, examples, retention detail) stays inline. Not 3 because there are no well-signaled one-level-deep bundle references; not 1 because it is sectioned rather than a monolithic wall of text.	2 / 3
	Total	10 / 12 Passed

Description

82%

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, natural trigger phrases, but the opening 'Manage use when...' is grammatically broken and the capability description leans on fluff ('comprehensive guidance and automation') without concrete enumerated actions. Distinctiveness is weakened by the absence of any FairDB/database-specific framing.

Suggestions

Fix the broken opening clause so the lead verb is intact, e.g. 'Manage backup and recovery operations for FairDB instances. Use when...'.

Replace 'comprehensive guidance and automation' with concrete actions like 'generate backup scripts, configure retention, schedule backups to S3, and produce tested restore procedures'.

Add FairDB/database specificity to the description so it is clearly distinct from generic file-backup skills.

Dimension	Reasoning	Score
Specificity	It names the domain and some actions ('backup automation and disaster recovery') but does not list multiple concrete capabilities; 'comprehensive guidance and automation' is vague fluff. Not 3 because no enumerated concrete actions; not 1 because a domain and actions are named.	2 / 3
Completeness	It states what the skill does ('backup automation and disaster recovery') and explicitly when to use it ('use when you need to work with backup and recovery' plus a 'Trigger with phrases like' list). The 'Use when' clause is present, so completeness is not capped at 2.	3 / 3
Trigger Term Quality	It surfaces three natural phrases a user would actually say — 'create backups', 'automate backups', and 'implement disaster recovery' — giving good coverage. Not 2 because these are varied, natural terms rather than a single generic keyword.	3 / 3
Distinctiveness Conflict Risk	'Backup and recovery' is a moderately specific niche but the description never mentions FairDB or database-specific scope, so it could overlap with other generic backup skills. Not 3 due to lack of distinctive specificity; not 1 because it is not 'code and documents' level generic.	2 / 3
	Total	10 / 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
Commit: 3022dd3

Reviewed: 2 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.