CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill implementing-backup-strategies
What are skills?

84

1.01x

Quality

45%

Does it follow best practices?

Impact

92%

1.01x

Average score across 9 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/devops/backup-strategy-implementor/skills/implementing-backup-strategies/SKILL.md
SKILL.md
Review
Evals

Discovery

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description identifies a clear domain (backup and recovery) and includes some trigger phrases, but fails to specify concrete capabilities. The phrase 'comprehensive guidance and automation' is vague fluff that doesn't help Claude understand what actions this skill enables or distinguish it from related infrastructure skills.

Suggestions

Replace 'comprehensive guidance and automation' with specific actions like 'Creates backup schedules, performs incremental/full backups, restores files and databases, validates backup integrity'

Expand trigger terms to include common variations: 'restore data', 'backup schedule', 'data protection', 'snapshot', 'backup verification'

Specify what systems or file types this skill handles (e.g., databases, file systems, cloud storage) to improve distinctiveness

DimensionReasoningScore

Specificity

The description uses vague language like 'comprehensive guidance and automation' without listing concrete actions. It doesn't specify what backup operations are performed (e.g., incremental backups, snapshot creation, restore procedures).

1 / 3

Completeness

Has a 'Use when' equivalent in the first line and trigger phrases, but the 'what' portion is weak - 'comprehensive guidance and automation' doesn't explain what the skill actually does beyond the domain name.

2 / 3

Trigger Term Quality

Includes some natural trigger phrases like 'create backups', 'automate backups', and 'implement disaster recovery', but misses common variations like 'restore', 'recovery plan', 'backup schedule', 'data protection', or file type mentions.

2 / 3

Distinctiveness Conflict Risk

The backup/disaster recovery domain is reasonably specific, but the vague capability description could overlap with database skills, cloud infrastructure skills, or general system administration skills.

2 / 3

Total

7

/

12

Passed

Implementation

50%

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

This skill provides solid coverage of backup strategies with good structure and error handling documentation. However, it lacks executable code examples (only command fragments), includes some verbose explanations Claude doesn't need, and could benefit from explicit validation checkpoints in the workflow. The content describes what to do rather than showing exactly how to do it.

Suggestions

Add complete, executable backup script examples (e.g., a full PostgreSQL backup script with logging, error handling, and lock files) rather than just command fragments

Add explicit validation checkpoints within the workflow, such as 'After step 4, verify backup file exists and has non-zero size before proceeding'

Remove or condense prerequisites that Claude can infer (e.g., 'sufficient storage capacity' is obvious); focus on non-obvious requirements

Consider splitting the error handling table and detailed retention policies into a separate REFERENCE.md file to keep the main skill leaner

DimensionReasoningScore

Conciseness

The content is reasonably efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what RPO/RTO means conceptually, listing obvious prerequisites). The instructions could be tighter.

2 / 3

Actionability

Provides tool names and flags (e.g., `pg_dump --format=custom`, `rsync -avz --delete`) but lacks complete, executable code examples. The instructions describe what to do rather than providing copy-paste ready scripts.

2 / 3

Workflow Clarity

Steps are listed in logical sequence and include verification (step 8), but validation checkpoints are not explicit within the workflow. Missing feedback loops for error recovery during the backup process itself.

2 / 3

Progressive Disclosure

Content is organized with clear sections, but the skill is somewhat monolithic. The detailed error handling table and extensive instructions could be split into separate reference files, with the main skill providing a concise overview.

2 / 3

Total

8

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

9

/

11

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.