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 vagueness and lack of concrete actions—it says 'database management and optimization' without specifying what operations it actually performs. While it does include explicit trigger phrases, they are generic and limited. The opening 'Process use when' is grammatically awkward and the overall description reads as padded fluff rather than informative guidance.
Suggestions
Replace the vague 'database management and optimization with comprehensive guidance and automation' with specific concrete actions such as 'Write and optimize SQL queries, create indexes, design schemas, perform migrations, and configure connection pools.'
Expand trigger terms to include natural user phrases like 'SQL query', 'slow query', 'schema design', 'database migration', 'table creation', 'indexing', and specific database names (PostgreSQL, MySQL, etc.).
Fix the awkward opening 'Process use when' to a clear structure: describe what the skill does first, then add a 'Use when...' clause with explicit trigger conditions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'database management and optimization with comprehensive guidance and automation' without listing any concrete actions. There are no specific capabilities such as writing queries, creating indexes, migrating schemas, or backing up data. | 1 / 3 |
Completeness | It attempts to answer both 'what' and 'when' with trigger phrases, but the 'what' is extremely vague ('database management and optimization') and the 'when' triggers are limited. The awkward 'Process use when' phrasing weakens the 'when' clause, though trigger phrases are explicitly listed. | 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 might say such as 'SQL', 'query', 'schema', 'migration', 'index', 'table', or specific database names. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on 'database' narrows the domain somewhat, but the description is so generic within that domain that it could easily conflict with more specific database-related skills (e.g., query optimization, schema design, database migration). No clear niche is established. | 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 thorough, actionable database recovery skill with excellent workflow clarity and concrete commands. Its main weaknesses are moderate verbosity (explaining concepts like RPO/RTO that Claude knows, narrative-style examples) and a monolithic structure that would benefit from splitting detailed content into referenced files. The error handling table and validation checkpoints are strong additions.
Suggestions
Remove explanations of well-known concepts (RPO/RTO definitions, what physical vs logical backups are) and replace with terse references, e.g., 'Set RPO/RTO targets (e.g., RPO < 1h, RTO < 30min)'.
Split the error handling table, examples, and resources into separate referenced files (e.g., ERRORS.md, EXAMPLES.md) to improve progressive disclosure and reduce the main file's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity. The prerequisites section explains obvious things (e.g., 'estimate 2-3x database size'), the RPO/RTO definitions in step 2 explain concepts Claude already knows, and the examples section narrates scenarios rather than providing lean, executable snippets. However, most content is relevant and not egregiously padded. | 2 / 3 |
Actionability | The skill provides specific, executable commands throughout: pg_basebackup flags, pg_dump options, mysqldump with correct flags, postgresql.conf settings, SQL queries for verification, and aws s3 commands. The error handling table maps specific errors to concrete solutions with actual commands. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced from assessment through automation and testing. It includes explicit validation checkpoints: step 3 verifies archiving works, step 7 tests recovery on a separate server and measures actual recovery time against RTO, step 8 automates verification with integrity checks, and step 10 schedules regular drills. The feedback loop of backup → restore → verify → fix is well-established. | 3 / 3 |
Progressive Disclosure | The content is a long monolithic document (~100+ lines of dense content) with no references to supporting files. The error handling table, examples, and resources could be split into separate files. However, the document is well-organized with clear section headers (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), which partially compensates. | 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
3a2d27d
- 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.