CtrlK
BlogDocsLog inGet started
Tessl Logo

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-recovery
What are skills?

59

1.16x

Quality

30%

Does it follow best practices?

Impact

77%

1.16x

Average 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.md
SKILL.md
Review
Evals

Evaluation results

82%

Production Database Disaster Recovery Runbook

Disaster recovery runbook and workflow

Criteria
Without context
With context

/recovery entry point

0%

0%

Backup schedule tied to RPO

100%

100%

Secondary region replication

100%

100%

Failover automation steps

80%

90%

Post-failover validation

100%

100%

RPO defined in config

100%

100%

Replication target in config

100%

100%

Self-contained runbook

90%

80%

Backup retention policy

100%

100%

Recovery workflow ordering

100%

100%

Without context: $0.3184 · 1m 53s · 11 turns · 12 in / 6,366 out tokens

With context: $0.8424 · 2m 24s · 27 turns · 55 in / 8,137 out tokens

85%

5%

MySQL Point-in-Time Recovery Implementation

Point-in-time recovery configuration

Criteria
Without context
With context

/recovery initiation

0%

0%

Transaction log archiving

100%

100%

Backup frequency ≤ RPO

58%

100%

RPO in config

100%

100%

Log archiving config

100%

100%

Timestamped restore steps

100%

100%

Recovery testing mentioned

100%

100%

Any-engineer usability

100%

100%

Backup retention defined

100%

100%

Ordered restoration steps

100%

100%

Without context: $0.4557 · 2m 18s · 19 turns · 20 in / 7,935 out tokens

With context: $0.9551 · 2m 28s · 27 turns · 13,858 in / 8,589 out tokens

86%

4%

Automated Database Recovery Testing and Monitoring Integration

Recovery testing and monitoring integration

Criteria
Without context
With context

/recovery in workflow

0%

0%

Regular testing schedule

100%

100%

Backup validation step

100%

100%

Restore verification step

100%

100%

Result logging

100%

100%

Cleanup step in script

100%

100%

Auto-trigger on outage

100%

100%

Outage condition defined

100%

100%

Documentation audience

100%

100%

Placeholder values in script

50%

100%

Without context: $0.5286 · 2m 46s · 20 turns · 21 in / 9,880 out tokens

With context: $0.8659 · 3m 15s · 29 turns · 4,489 in / 11,843 out tokens

77%

67%

Database Failover Runbook for E-Commerce Platform

Failover script invocation and exit code handling

Criteria
Without context
With context

Uses failover.sh script

0%

100%

-t / --db-type flag

0%

100%

--primary-host flag

0%

100%

--secondary-host flag

0%

100%

--mode automatic

0%

0%

--check-interval flag

0%

0%

--dns-record flag

0%

100%

Exit code 3 handled

0%

100%

Exit code 4 handled

0%

100%

Least-privilege service account

100%

100%

--dry-run validation step

0%

30%

Without context: $0.2152 · 1m 29s · 11 turns · 12 in / 4,562 out tokens

With context: $0.4633 · 1m 51s · 17 turns · 8,268 in / 6,117 out tokens

32%

-8%

Automated Nightly Backup Validation Pipeline

Backup validation and recovery test automation

Criteria
Without context
With context

Uses validate_backup.sh

0%

0%

validate_backup.sh -p flag

0%

0%

validate_backup.sh -t flag

0%

0%

Uses test_recovery.sh

0%

0%

test_recovery.sh --verify-data

0%

0%

test_recovery.sh --cleanup

0%

0%

Low-traffic scheduling

100%

100%

Retry with exponential backoff

100%

25%

Version-controlled config

20%

30%

Multiple DB types supported

100%

100%

Pipeline output/result logged

100%

100%

Without context: $0.3965 · 1m 30s · 21 turns · 21 in / 5,913 out tokens

With context: $0.7507 · 2m 17s · 25 turns · 7,968 in / 8,605 out tokens

100%

Database Compression Migration for Legacy Analytics System

5-step recovery workflow and output artifacts

Criteria
Without context
With context

Step 1: Assess present

100%

100%

Step 2: Design present

100%

100%

Step 3: Implement present

100%

100%

Step 4: Validate present

100%

100%

Step 5: Deploy present

100%

100%

Non-production first

100%

100%

Rollback plan included

100%

100%

Implementation artifacts

100%

100%

Monitoring configuration

100%

100%

Runbook produced

100%

100%

Test results artifact

100%

100%

Changes/decisions documented

100%

100%

Without context: $1.0699 · 7m 20s · 23 turns · 24 in / 24,481 out tokens

With context: $1.4745 · 7m 18s · 35 turns · 4,493 in / 24,960 out tokens

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

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.