automating-database-backups
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'.
81
78%
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 articulates 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 a clear separation of what it does and when to use it. Minor redundancy in the trigger section ('Trigger with automating, database, backups' repeats earlier content) but overall very effective.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scheduling, compression, encryption, names specific tools (pg_dump, mysqldump, mongodump), mentions retention policies and restore procedures. Very detailed and actionable. | 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). Good coverage of natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on database backup automation. The combination of specific database tools, backup-specific terminology, and distinct trigger terms makes it unlikely to conflict with general database skills or general automation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 reasonable structure with concrete bash examples and clear references to supporting materials. However, it suffers from filler content at the bottom (vague Examples, redundant Overview, generic Prerequisites), relies on helper scripts whose existence is uncertain, and lacks explicit error recovery loops in the workflow. The MongoDB example also has a syntax issue.
Suggestions
Remove or rewrite the bottom Overview, Prerequisites, and Examples sections — they are redundant, generic, or vague filler that wastes tokens.
Add an explicit feedback loop in Step 4: specify what to do when validation fails (e.g., re-run backup, check logs, retry with different options).
Fix the MongoDB backup script — the inline comment after the line continuation backslash will cause a syntax error.
Clarify whether the helper scripts (backup_script_generator.py, etc.) are bundled with the skill or need to be created, and provide fallback inline commands if they don't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary sections (Overview at the bottom repeats the intro, Prerequisites is generic and partially wrong mentioning only PostgreSQL, Examples section is vague filler). The cron reference table and error handling table add value but the overall content could be tightened significantly. | 2 / 3 |
Actionability | The Quick Start bash scripts are concrete and executable, but the core workflow relies on helper scripts (backup_script_generator.py, backup_scheduler.py, backup_validator.py, restore_script_generator.py) that may or may not exist. The Examples section at the bottom is completely vague with no actual examples. The MongoDB backup has a syntax issue with the inline comment after a line continuation. | 2 / 3 |
Workflow Clarity | Steps 1-5 provide a clear sequence, and Step 4 includes validation. However, there's no explicit feedback loop (validate -> fix -> retry) for when validation fails, and no guidance on what to do if the backup script generation or scheduling fails. For a destructive/batch operation like database backups, the missing error recovery loop is notable. | 2 / 3 |
Progressive Disclosure | The skill has a clear quick start section, structured workflow steps, and well-signaled one-level-deep references to detailed guides in the references directory for each database type and best practices. Navigation is straightforward. | 3 / 3 |
Total | 9 / 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 | |
- Commit
4dee593
- 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.