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

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/database/database-recovery-manager/skills/managing-database-recovery/SKILL.md

Quality

Discovery

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.

The description is overly vague and relies on buzzwords like 'comprehensive guidance and automation' without specifying concrete capabilities. While it includes some trigger phrases, they are generic and don't differentiate this skill from other database-related tools. The opening phrase 'Process use when you need to' is awkwardly worded and uses second person, which violates the style guidelines.

Suggestions

Replace vague language with specific concrete actions (e.g., 'Write and optimize SQL queries, create indexes, design schemas, perform migrations, troubleshoot slow queries').

Add a proper 'Use when...' clause with explicit situational triggers (e.g., 'Use when the user asks about SQL queries, database performance, schema design, indexing, or mentions specific databases like PostgreSQL, MySQL, or SQLite').

Rewrite in third person voice ('Manages database operations...') instead of second person ('you need to') and remove filler phrases like 'comprehensive guidance and automation'.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'database management and optimization with comprehensive guidance and automation' without listing any concrete actions. No specific operations (e.g., write queries, create indexes, migrate schemas) are mentioned.	1 / 3
Completeness	It attempts to answer both 'what' and 'when' — the 'what' is vague ('database management and optimization') and the 'when' is present via trigger phrases but lacks a proper 'Use when...' clause with explicit situational triggers beyond just keyword matching.	2 / 3
Trigger Term Quality	It includes some relevant trigger phrases like 'manage database', 'optimize database', and 'configure database', but these are fairly generic and miss common natural variations users would say (e.g., 'SQL query', 'schema', 'migration', 'slow query', 'indexing', specific database names like 'PostgreSQL' or 'MySQL').	2 / 3
Distinctiveness Conflict Risk	The term 'database operations' is somewhat specific to a domain but could easily overlap with skills for SQL writing, data analysis, ETL pipelines, or ORM usage. The description doesn't carve out a clear niche within the database domain.	2 / 3
	Total	7 / 12 Passed

Implementation

70%

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

This is a comprehensive and highly actionable database recovery skill with concrete commands, clear workflow sequencing, and good validation checkpoints. Its main weaknesses are verbosity (explaining concepts Claude already knows like RPO/RTO definitions) and poor progressive disclosure—all content is crammed into a single monolithic file when it would benefit greatly from being split across focused reference documents for each database system and recovery scenario.

Suggestions

Split PostgreSQL-specific and MySQL-specific content into separate reference files (e.g., POSTGRESQL_RECOVERY.md, MYSQL_RECOVERY.md) and reference them from the main SKILL.md overview.

Remove explanations of concepts Claude already knows (RPO/RTO definitions, what physical vs logical backups are, why compression helps with storage) to reduce token usage.

Extract the error handling table and examples into a separate TROUBLESHOOTING.md or EXAMPLES.md file, keeping only a brief summary in the main skill.

Create actual backup script files (e.g., scripts/pg_backup.sh, scripts/verify_backup.sh) as bundle files rather than describing them in prose.

Dimension	Reasoning	Score
Conciseness	The content is reasonably well-structured but includes some unnecessary verbosity. Explanations like what RPO and RTO mean, and general descriptions of backup types, are concepts Claude already knows. The error handling table and examples section add bulk that could be trimmed. However, the specific commands and configurations are valuable and earn their place.	2 / 3
Actionability	The skill provides concrete, executable commands throughout: specific pg_basebackup flags, exact postgresql.conf settings, mysqldump options, aws s3 commands, and recovery procedures with real SQL and shell commands. The error handling table maps specific errors to specific solutions with actual commands.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced from assessment through automation and ongoing drills. It includes explicit validation checkpoints: verifying archiving works (step 3), testing recovery on a separate server (step 7), automated verification with integrity checks (step 8), and monthly DR drills (step 10). The PITR recovery example includes a clear feedback loop of restore-verify-swap.	3 / 3
Progressive Disclosure	The content is a monolithic wall of text with no bundle files to reference. All content—prerequisites, instructions, error handling, examples, and resources—is inline in a single file. For a skill of this complexity covering two database systems, multiple backup types, and multiple recovery scenarios, the content should be split into separate reference files (e.g., PostgreSQL-specific guide, MySQL-specific guide, recovery runbook template, backup scripts).	1 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 69c73e9

Reviewed: 4 days 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.