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

76%

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/backup-strategy-implementor/skills/implementing-backup-strategies/SKILL.md

Quality

Content

77%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 lean, well-sequenced workflow with concrete command fragments, explicit verification, and a useful error-handling table. Its main weaknesses are incomplete actionability (no real scripts — only placeholder checkboxes) and broken progressive disclosure (empty bundle directories, nothing linked from the body).

Suggestions

Provide the actual scripts referenced in scripts/README.md (backup_database.sh, restore_database.sh, validate_backup.py) as real, executable files and link to them from the Instructions/Output sections.

Move the detailed restore runbook and per-database examples into references/ files (e.g., RESTORE_RUNBOOK.md, DATABASE_EXAMPLES.md) and signal them from the body to deepen progressive disclosure.

Add a complete, copy-paste-ready example script with logging, lock file, and error handling to lift actionability from fragments to fully executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what tar, rsync, pg_dump, or backups are, and every section (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) earns its place with terse, actionable content.	3 / 3
Actionability	Provides concrete command fragments and flags ('pg_dump --format=custom', 'tar czf', 'rsync -avz --delete', 'gpg --encrypt', 'sha256sum'), but no complete, copy-paste-ready scripts; the promised backup/restore/validate scripts exist only as unchecked checkboxes in scripts/README.md rather than real files, leaving guidance incomplete.	2 / 3
Workflow Clarity	The Instructions form a clear 9-step sequence (inventory → classify → select strategy → generate → retention → encrypt → schedule → verify → alert) with an explicit verification step ('restore to a test environment on a weekly schedule and validate data integrity') and an Error Handling table providing cause/solution feedback loops, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	The body is well-organized into clear sections, but the bundle directories are placeholder READMEs only — references/ and assets/ are empty and scripts/README.md lists four planned scripts as unchecked checkboxes — and none of these are referenced or linked from the body, so content that should live in separate files (backup scripts, restore runbook, validation script) is promised but absent.	2 / 3
	Total	10 / 12 Passed

Description

75%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 the skill does and when to use it, with explicit triggers and a clear niche that avoids conflicts. It is weakened by a garbled opening ('Execute use when'), vague fluff, overlapping action terms, and a trigger list that omits common restore/recovery variations.

Suggestions

Fix the malformed opening and use a crisp third-person 'Use when...' clause (e.g., 'Use when designing or implementing backup and disaster-recovery strategies').

Replace the fluff phrase 'comprehensive guidance and automation' with concrete capabilities (e.g., 'design retention policies, encrypt backups, schedule and verify restores').

Add restore-side trigger terms users would actually say (e.g., 'restore from backup', 'recovery plan', 'backup strategy') to round out trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the backup/disaster-recovery domain and several actions ('backup automation and disaster recovery', 'create backups', 'automate backups', 'implement disaster recovery'), but the actions overlap and are padded with vague fluff ('comprehensive guidance and automation'), and the trigger clause uses second-person phrasing ('when you need to work'), so it falls short of the granular, distinct-action bar for a 3.	2 / 3
Completeness	Clearly answers both what ('This skill provides backup automation and disaster recovery') and when with explicit trigger guidance ('Execute use when you need to work with backup and recovery. Trigger with phrases like...'), satisfying the explicit-trigger requirement that would otherwise cap completeness at 2.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('create backups', 'automate backups', 'implement disaster recovery'), but for a skill covering both backup AND recovery it misses common restore-side variations ('restore', 'recovery plan', 'backup strategy', 'retention'), matching 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (backup automation and disaster recovery) with distinct, specific triggers unlikely to collide with other skills, matching 'clear niche with distinct triggers; unlikely to conflict'.	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
Path: plugins/devops/backup-strategy-implementor/skills/implementing-backup-strategies/SKILL.md
Commit: 0540a62

Reviewed: about 14 hours 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.