managing-database-recovery

Quick Review

This skill has a clear structure with good general workflow steps, but suffers from a critical mismatch between its name ('managing-database-recovery') and its actual content (generic 'Database Recovery Manager' template). The description is too vague—it claims to handle 'database operations', 'optimization', and 'configuration' but provides no database-specific knowledge, recovery procedures, backup strategies, or PITR details despite having recovery-focused scripts (failover.sh, pitr_restore.sh, etc.). The 5-step workflow is sound but generic and could apply to any infrastructure task. While the structure is adequate and references to scripts/templates suggest useful automation exists, a CLI agent cannot effectively invoke this skill because the description doesn't explain what specific database recovery capabilities it offers (e.g., PostgreSQL PITR, failover automation, backup validation). Novelty is moderate—database recovery automation is valuable, but without concrete task knowledge, the actual value proposition is unclear. To improve: rewrite the description to specify supported databases, recovery scenarios, and what the scripts actually do; add database-specific recovery procedures and decision trees to the instructions.