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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-recovery59
Quality
30%
Does it follow best practices?
Impact
77%
1.16xAverage score across 6 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/database-recovery-manager/skills/managing-database-recovery/SKILL.mdDiscovery
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 vague, buzzword-heavy language ('comprehensive guidance and automation') without specifying concrete database operations. While it attempts to provide trigger phrases, the lack of specific capabilities makes it difficult for Claude to know exactly what this skill can do versus other database-related skills.
Suggestions
Replace vague phrases like 'database management and optimization' with specific actions such as 'Create and modify tables, write SQL queries, optimize indexes, backup and restore databases'.
Expand trigger terms to include natural user language like 'SQL', 'query', 'tables', 'schema', 'PostgreSQL', 'MySQL', 'database backup'.
Restructure to follow the pattern: '[Specific actions]. Use when [explicit triggers]' rather than starting with 'Process use when'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'database management and optimization' and 'comprehensive guidance and automation' without listing concrete actions. No specific operations like 'create tables', 'run queries', or 'backup data' are mentioned. | 1 / 3 |
Completeness | Has a weak 'what' (database management and optimization) and does include trigger phrases, but the 'what' is too vague to be useful. The 'when' guidance exists via 'Trigger with phrases like...' but the capability description lacks substance. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords ('manage database', 'optimize database', 'configure database') but misses common variations users would naturally say like 'SQL', 'query', 'tables', 'schema', 'backup', or specific database names like 'PostgreSQL', 'MySQL'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'database' provides some specificity, but 'management and optimization' is broad enough to potentially conflict with skills for specific database types, data analysis, or DevOps tools. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template masquerading as database recovery guidance. It contains no database-specific content—no SQL commands, no recovery tools (pg_restore, mysqldump, RMAN), no actual recovery procedures. The content could apply to any IT task and wastes tokens on obvious advice Claude already knows.
Suggestions
Replace generic steps with actual database recovery commands (e.g., `pg_restore -d dbname backup.dump`, point-in-time recovery syntax, transaction log replay)
Add concrete examples showing recovery scenarios: corrupted table recovery, point-in-time restore, replica promotion
Remove obvious advice like 'verify credentials' and 'monitor for issues' - focus only on database-specific knowledge Claude wouldn't have
Include specific validation commands (e.g., `pg_isready`, consistency checks, data verification queries) instead of abstract 'run comprehensive tests'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts like 'verify credentials' and 'monitor for issues' that Claude already knows. No database-specific content despite being titled 'Database Recovery Manager'. | 1 / 3 |
Actionability | Entirely abstract with no concrete code, commands, or database-specific examples. Instructions like 'Execute implementation' and 'Run comprehensive tests' provide no executable guidance. No actual database recovery commands, SQL, or tool-specific instructions. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically with some validation checkpoints mentioned (Step 4). However, the workflow is generic project management rather than database recovery-specific, and lacks concrete validation commands or feedback loops for database operations. | 2 / 3 |
Progressive Disclosure | References external files in Resources section with clear paths, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths ({baseDir}) and the skill body contains content that should be in those referenced files instead. | 2 / 3 |
Total | 6 / 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 | |
- 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.