managing-database-recovery
Process use when you need to work with database operations. This skill provides database management and optimization with comprehensive guidance and automation. Trigger with phrases like "manage database", "optimize database", or "configure database".
65
58%
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-recovery-manager/skills/managing-database-recovery/SKILL.mdQuality
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 suffers from extreme vagueness in its capability claims—'database management and optimization with comprehensive guidance and automation' is essentially buzzword padding with no concrete actions listed. While it does include trigger phrases and attempts a 'when to use' clause, the lack of specific operations and overly broad domain scope make it difficult to distinguish from other database-related skills.
Suggestions
Replace the vague 'database management and optimization' with specific concrete actions, e.g., 'Write and optimize SQL queries, create indexes, design schemas, perform migrations, and troubleshoot slow queries.'
Expand trigger terms to include natural user phrases and specific technologies, e.g., 'SQL', 'PostgreSQL', 'MySQL', 'slow query', 'schema design', 'database migration', 'indexing'.
Remove the filler phrase 'with comprehensive guidance and automation' and replace with actionable specifics about what the skill actually does differently from general coding assistance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'database management and optimization with comprehensive guidance and automation' without listing any concrete actions. No specific operations (e.g., write queries, create indexes, migrate schemas) are mentioned. | 1 / 3 |
Completeness | It attempts to answer both 'what' and 'when', but the 'what' is extremely vague ('database management and optimization') and the 'when' triggers are generic. The 'Use when' equivalent is present but the overall substance is weak. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger phrases like 'manage database', 'optimize database', and 'configure database', but these are fairly generic and miss common natural variations users would say (e.g., 'SQL query', 'schema', 'migration', 'slow query', 'indexing', specific database names like 'PostgreSQL' or 'MySQL'). | 2 / 3 |
Distinctiveness Conflict Risk | The term 'database' provides some domain specificity, but 'database operations' is broad enough to overlap with skills for SQL writing, data analysis, ORM configuration, or database migration tools. No specific database technology or operation type narrows the scope. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable database recovery skill with concrete commands, clear workflow sequencing, and good error handling coverage. Its main weaknesses are moderate verbosity (explaining concepts Claude already knows like RPO/RTO definitions) and a monolithic structure that would benefit from splitting detailed content into referenced sub-files. The skill covers both PostgreSQL and MySQL well with specific, executable guidance throughout.
Suggestions
Remove or drastically shorten the RPO/RTO definitions in step 2 — Claude already understands these concepts; just specify the targets directly.
Split detailed backup scripts, recovery runbook templates, and verification scripts into separate referenced files (e.g., RECOVERY_RUNBOOK.md, BACKUP_SCRIPTS.md) to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some unnecessary explanation that Claude would already know (e.g., defining RPO/RTO, explaining that physical backups are faster than logical for large databases). The prerequisites section lists obvious tools, and some descriptions could be tightened. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides specific, executable commands throughout: exact pg_basebackup flags, pg_dump options, mysqldump parameters, postgresql.conf settings, SQL queries for verification, and concrete S3 upload commands. Commands are copy-paste ready with real flags and paths. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced from assessment through automation and testing. It includes explicit validation checkpoints (step 7: test recovery and verify data integrity, step 8: automated verification with integrity checks) and feedback loops (monthly drills to validate RTO). The error handling table provides clear recovery paths for common failures. | 3 / 3 |
Progressive Disclosure | The content is a monolithic document with no references to separate files for detailed topics like recovery runbooks, backup scripts, or configuration templates. Given the breadth of content (PostgreSQL + MySQL, multiple backup types, automation, DR drills), this would benefit from splitting detailed scripts and runbook templates into separate referenced files. | 2 / 3 |
Total | 10 / 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
3e83543
- 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.