implementing-backup-strategies

Execute 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 concise with a well-sequenced, validated workflow and a strong error table, but its actionability and progressive disclosure are undermined by referenced bundle scripts that are stubs rather than real files.

Suggestions

Add the actual backup_database.sh / restore_database.sh / validate_backup.py scripts to the scripts/ bundle instead of leaving them as TODO checkboxes, and link to them from the body.

Replace the placeholder README stubs in references/, scripts/, and assets/ with the real referenced content or remove the references if the material is not needed.

Optionally include one complete copy-paste-ready backup script example inline so the guidance is fully executable without depending on the missing bundle files.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what a backup is, uses concrete inline commands, and each section earns its place. The only mild restatement is the Overview, which stays informative rather than padded.	3 / 3
Actionability	It gives specific executable fragments (pg_dump --format=custom, tar czf, rsync -avz --delete, gpg --encrypt) and a useful error table, but the Output section promises scripts (backup_database.sh, restore_database.sh, validate_backup.py) that exist only as TODO checkboxes in a stub README rather than real, complete files.	2 / 3
Workflow Clarity	A clear 9-step sequence includes an explicit verification checkpoint (restore to a test environment and validate integrity) plus alerting, and the Error Handling table provides feedback loops for recovery, satisfying the batch-operation validation requirement.	3 / 3
Progressive Disclosure	Sections are well organized, but the body references bundled scripts that are not actually present (only placeholder READMEs with unchecked items), and there are no properly signaled one-level-deep reference links into a real bundle.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 has solid trigger terms and a distinct niche, but its capability statement is vague and circular and the grammar of the opening clause is broken. Tightening the what/when wording would lift the weaker dimensions.

Suggestions

Replace the circular "comprehensive guidance and automation" with concrete actions, e.g. "Design backup strategies, generate tar/rsync/pg_dump scripts, configure retention, and verify restores".

Fix the malformed opener "Execute use when you need to work with backup and recovery" to a clean "Use when you need to design or run backups and disaster recovery".

Drop redundant wording so the description states what it does and when to trigger it without padding.

Dimension	Reasoning	Score
Specificity	Names the backup/disaster-recovery domain and some actions, but the capability phrasing is circular and padded ("backup automation and disaster recovery with comprehensive guidance and automation"), not a list of concrete actions. It does not reach the multiple-specific-actions level.	2 / 3
Completeness	It answers both what and when and provides an explicit trigger clause, but the "what" is weakened by fluff/over-claim ("comprehensive guidance and automation") and the malformed "Execute use when" opener, so it falls short of the cleanly explicit level-3 example.	2 / 3
Trigger Term Quality	Includes natural phrases a user would say ("create backups", "automate backups", "implement disaster recovery") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Backup and disaster recovery is a clear niche with distinct trigger phrases unlikely to fire for unrelated skills.	3 / 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: 607d11b

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