managing-database-recovery
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-recoveryProcess 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no actual database recovery content. It reads like a fill-in-the-blank project management checklist rather than actionable technical guidance. There are no database commands, recovery procedures, specific tools (pg_restore, mysqldump, RMAN, etc.), or concrete examples that would help Claude perform database recovery tasks.
Suggestions
Replace generic steps with specific database recovery commands and procedures (e.g., point-in-time recovery, transaction log replay, backup restoration commands for specific database systems)
Add executable code examples showing actual recovery operations like `pg_restore -d mydb backup.dump` or equivalent for target database systems
Remove obvious advice Claude already knows (backup data, test in staging, monitor for issues) and focus on database-recovery-specific knowledge
Provide concrete validation commands to verify recovery success (e.g., checking row counts, running integrity checks, comparing checksums)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts Claude already knows (like 'backup critical data', 'test in staging first') and contains no database-recovery-specific information. | 1 / 3 |
Actionability | No concrete code, commands, or database-specific instructions. Every step is abstract ('Review current configuration', 'Execute implementation') with no actual recovery commands, SQL, or tool-specific guidance. | 1 / 3 |
Workflow Clarity | Steps are sequenced logically (assess, design, implement, validate, deploy) but lack any database recovery specifics. No actual validation commands or checkpoints - just generic advice like 'run comprehensive tests'. | 2 / 3 |
Progressive Disclosure | References external files (templates, docs, examples) which is good structure, but the main content is a wall of generic text. The referenced files use placeholder paths that may not exist, and the 'Examples' section is empty. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vague, buzzword-heavy language ('comprehensive guidance and automation') without specifying concrete database operations. While it includes explicit trigger phrases which is positive, the actual capabilities are poorly defined. The description would benefit significantly from listing specific actions and expanding trigger terms to include common database-related vocabulary.
Suggestions
Replace vague phrases like 'comprehensive guidance and automation' with specific actions such as 'write SQL queries, create schemas, optimize indexes, backup and restore data'
Expand trigger terms to include natural user language like 'SQL', 'query', 'tables', 'schema', 'PostgreSQL', 'MySQL', 'database backup'
Clarify the scope by specifying which database systems are supported or what types of database tasks this skill handles versus other potential database-related skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'database management and optimization' and 'comprehensive guidance and automation' without listing any concrete actions. No specific operations like 'create tables', 'write queries', or 'backup data' are mentioned. | 1 / 3 |
Completeness | Has explicit trigger phrases which partially addresses 'when', but the 'what' is extremely vague ('database management and optimization with comprehensive guidance'). The trigger guidance exists but the capability description is too weak to fully satisfy completeness. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases ('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 databases, data analysis, or DevOps tools. Lacks clear niche definition. | 2 / 3 |
Total | 7 / 12 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.