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".

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-recovery-manager/skills/managing-database-recovery/SKILL.md

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable recovery runbook with a clear sequenced workflow, explicit validation checkpoints, and error-recovery feedback loops. Its main gap is progressive disclosure: it ignores the bundled scripts that ship alongside it.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and operational (e.g. `pg_basebackup -D /backups/base -Ft -z -P`, `archive_command = 'test ! -f /archive/%f && cp %p /archive/%f'`) with no padding explaining basic concepts Claude already knows; RPO/RTO notes are operational specifics rather than filler, so tokens earn their place.	3 / 3
Actionability	Guidance is concrete and copy-paste ready across both engines — exact commands, config values, and S3 upload strings (e.g. `pg_dump -Fc -f database.dump dbname`, `aws s3 cp /backups/base.tar.gz s3://...`) — fully executable rather than abstract direction.	3 / 3
Workflow Clarity	Ten numbered steps form a clear sequence with explicit validation checkpoints (`SELECT * FROM pg_stat_archiver`, 'Verify data integrity by running application test suite', 'Measure actual recovery time to validate RTO') and the Error Handling table provides feedback loops for recovery failures, satisfying the database-operations feedback-loop requirement.	3 / 3
Progressive Disclosure	Sections are well-organized, but the body never references the bundled scripts that actually exist (validate_backup.sh, pitr_restore.sh, failover.sh, test_recovery.sh documented in scripts/README.md); content that could be delegated to those scripts is inline, so existing bundle files are not signaled.	2 / 3
	Total	11 / 12 Passed

Description

40%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description includes explicit trigger guidance but describes capabilities in vague, buzzword-heavy terms with generic verbs, and its trigger phrases are misaligned with the skill's actual recovery/backup purpose. The second-person phrasing further weakens specificity.

Suggestions

Replace generic verbs and fluff with concrete recovery-specific actions, e.g. 'Plan and execute PostgreSQL/MySQL backups, point-in-time recovery (PITR), WAL archiving, and disaster recovery verification.'

Align trigger phrases with the skill's actual purpose by adding natural terms users would say for recovery: 'backup database', 'restore database', 'point-in-time recovery', 'PITR', 'WAL archive', 'disaster recovery'.

Rewrite in third person and drop 'comprehensive guidance and automation' filler so the 'what' clearly states the skill's capabilities.

Dimension	Reasoning	Score
Specificity	Actions named are generic verbs ('manage database', 'optimize database', 'configure database') padded with fluff ('comprehensive guidance and automation'); the second-person phrasing 'when you need to work with database operations' triggers the rubric's -1 specificity penalty, dropping the base 2 to 1.	1 / 3
Completeness	Both a 'what' and an explicit 'when' ('Trigger with phrases like...') are present, but the 'what' is vague buzzword fluff ('database management and optimization with comprehensive guidance and automation') rather than a clear capability statement, so it does not clearly answer what the skill does.	2 / 3
Trigger Term Quality	'manage database', 'optimize database', 'configure database' are natural phrases a user might say, but the set is narrow, repetitive, and misaligned with the skill's actual recovery/backup focus (no 'backup', 'restore', 'recover', or 'PITR' triggers), so common variations are missing.	2 / 3
Distinctiveness Conflict Risk	'database operations' and 'database management and optimization' are a broad domain whose triggers ('manage/optimize/configure database') could overlap with general database-administration skills, so it is only somewhat specific.	2 / 3
	Total	7 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-recovery-manager/skills/managing-database-recovery/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.