Automate database backup processes with scheduling, compression, and encryption. Supports PostgreSQL (pg_dump), MySQL (mysqldump), MongoDB (mongodump), and SQLite. Generates production-ready backup scripts with retention policies and restore procedures. Trigger: "automate database backups", "schedule backups", "create backup script", "disaster recovery". Use when working with automating database backups. Trigger with 'automating', 'database', 'backups'.
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/database-backup-automator/skills/automating-database-backups/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly communicates specific capabilities across multiple database systems, includes concrete actions (scheduling, compression, encryption, retention policies), and provides explicit trigger guidance. The description is well-structured with good coverage of natural user terms. Minor redundancy exists in the trigger section where 'automating', 'database', 'backups' are listed separately after already being covered in the trigger phrases.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scheduling, compression, encryption, names specific tools (pg_dump, mysqldump, mongodump), and mentions retention policies and restore procedures. | 3 / 3 |
Completeness | Clearly answers both 'what' (automate backup processes with scheduling, compression, encryption for multiple databases, generate scripts with retention policies) and 'when' (explicit trigger clause with 'Use when working with automating database backups' and specific trigger terms). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'automate database backups', 'schedule backups', 'create backup script', 'disaster recovery', plus specific database names (PostgreSQL, MySQL, MongoDB, SQLite) that users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche focused specifically on database backup automation with named database systems and tools. Unlikely to conflict with general database skills or general scripting skills due to the specific backup/disaster recovery focus. | 3 / 3 |
Total | 12 / 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.
The skill provides a solid foundation with concrete backup scripts for multiple databases and a structured workflow, but is undermined by references to non-existent bundle scripts/files, vague filler sections at the end (Overview, Prerequisites, Examples), and missing error recovery loops in the workflow. The Quick Start section is the strongest part, while the bottom sections appear to be boilerplate that adds no value.
Suggestions
Remove the redundant 'Overview', vague 'Prerequisites', and empty 'Examples' sections at the bottom — they add no actionable content and waste tokens.
Either include the referenced scripts (backup_script_generator.py, backup_validator.py, etc.) in the bundle or replace those workflow steps with inline executable commands.
Add an explicit feedback loop after Step 4 validation: specify what to do if validation fails, how to diagnose issues, and when to retry.
Include the referenced resource files in the bundle or remove the Resources section to avoid pointing to non-existent files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary sections like the 'Overview' at the bottom that repeats the intro, the 'Prerequisites' section that states obvious things ('Familiarity with PostgreSQL concepts'), and the 'Examples' section which is entirely vague filler. The cron reference table is arguably something Claude already knows. However, the core backup scripts and workflow steps are reasonably efficient. | 2 / 3 |
Actionability | The Quick Start backup scripts are concrete and executable, but the workflow steps reference scripts (backup_script_generator.py, backup_scheduler.py, backup_validator.py, restore_script_generator.py) that don't exist in the bundle, making them non-executable. The 'Examples' section at the bottom is completely vague with no concrete content. The error handling table provides actionable solutions though. | 2 / 3 |
Workflow Clarity | Steps 1-5 provide a clear sequence with a validation step (Step 4), but the validation depends on a non-existent script. There's no explicit feedback loop for what to do if validation fails — it just validates without specifying error recovery. For a skill involving potentially destructive backup/restore operations, the lack of a clear validate-fix-retry loop caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill references six files under Resources and four scripts, but none of these exist in the bundle (no bundle files provided). The structure attempts progressive disclosure with Quick Start → Instructions → References, but the references point to non-existent files. The 'Overview' section awkwardly appears near the bottom after all the detailed content, and the 'Examples' section is empty filler that disrupts organization. | 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.
Validation — 9 / 11 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 | 9 / 11 Passed | |
3a2d27d
Table of Contents
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.