CtrlK
BlogDocsLog inGet started
Tessl Logo

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

38

Quality

37%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/devops/fairdb-operations-kit/skills/fairdb-backup-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

This skill provides a well-structured outline for FairDB backup management but critically lacks executable code, making it more of a planning document than an actionable skill. The error handling table is a useful addition, but the absence of any actual scripts, cron entries, or configuration snippets means Claude would need to generate everything from scratch with only high-level guidance. The workflow is sequenced but missing explicit validation checkpoints between critical steps.

Suggestions

Add complete, executable backup and restore shell scripts with actual commands (fairdb dump, tar, aws s3 cp, checksum verification) rather than describing what the scripts should contain.

Include a concrete cron entry example and a sample S3 lifecycle policy JSON configuration that can be directly used or adapted.

Add explicit validation checkpoints in the workflow, e.g., 'Verify checksum matches before uploading to S3' and 'Confirm restore query returns expected row count before marking restore complete'.

Replace the natural language 'Examples' section with actual input/output examples showing a generated backup script given specific parameters.

DimensionReasoningScore

Conciseness

The content is reasonably structured but includes some unnecessary verbosity. The overview restates what the description already covers, the examples section describes use cases rather than providing executable examples, and the resources section links to generic external docs Claude already knows about. The error handling table is useful but could be tighter.

2 / 3

Actionability

Despite listing steps, the skill provides no executable code—no actual backup script, no restore script, no cron entries, no S3 lifecycle policy JSON. The instructions are high-level descriptions of what to do ('Generate backup script with lock acquisition...') rather than concrete, copy-paste-ready implementations. The 'Examples' section contains natural language prompts, not code examples.

1 / 3

Workflow Clarity

The 9-step workflow provides a reasonable sequence, and step 9 mentions testing the restore procedure. However, there are no explicit validation checkpoints between steps (e.g., verify backup integrity before uploading to S3), no feedback loops for error recovery within the workflow itself, and the validation/verification steps are mentioned only in passing rather than as explicit gates.

2 / 3

Progressive Disclosure

The content is organized into clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), which is good structure. However, with no bundle files, all content is inline in a single file. The skill would benefit from splitting detailed scripts and configurations into separate referenced files, but for a standalone skill of this length (~80 lines), the organization is adequate though not optimal.

2 / 3

Total

7

/

12

Passed

Description

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 is overly vague and padded with buzzwords like 'comprehensive guidance and automation' without specifying concrete capabilities. While it does include some useful trigger phrases, it fails to articulate what specific backup and recovery actions the skill can perform, making it difficult for Claude to confidently select it over other infrastructure-related skills.

Suggestions

Replace vague language like 'comprehensive guidance and automation' with specific concrete actions such as 'schedule incremental backups, configure retention policies, restore from snapshots, set up automated backup pipelines'.

Add a clear 'Use when...' clause specifying the conditions, e.g., 'Use when the user needs to set up, manage, or troubleshoot backup systems, restore lost data, or plan disaster recovery strategies.'

Expand trigger terms to include common variations like 'restore data', 'backup schedule', 'snapshot', 'data loss', 'recovery plan', 'backup strategy', and mention specific platforms or tools if applicable.

DimensionReasoningScore

Specificity

The description uses vague language like 'backup automation and disaster recovery with comprehensive guidance and automation.' It does not list specific concrete actions—what kind of backups? What systems? What does 'comprehensive guidance' mean? No concrete actions like 'schedule incremental backups', 'restore from snapshots', or 'configure retention policies' are mentioned.

1 / 3

Completeness

It has a weak 'what' (backup automation and disaster recovery) and does include trigger phrases which partially serve as a 'when' clause. However, the 'what' is too vague to be meaningful, and the 'when' is presented as trigger phrases rather than a clear 'Use when...' clause explaining the conditions for selection.

2 / 3

Trigger Term Quality

It includes some relevant trigger phrases like 'create backups', 'automate backups', and 'implement disaster recovery', which are natural terms users might say. However, it misses common variations like 'restore', 'snapshot', 'backup schedule', 'data recovery', 'backup strategy', or specific tools/platforms.

2 / 3

Distinctiveness Conflict Risk

The domain of 'backup and recovery' is somewhat specific and wouldn't overlap with most skills, but the description is vague enough that it could conflict with general DevOps, infrastructure, or system administration skills. It doesn't specify what kind of systems, platforms, or backup technologies are covered.

2 / 3

Total

7

/

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

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.