managing-database-replication

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-replication

Process use when you need to work with database scalability. This skill provides replication and sharding with comprehensive guidance and automation. Trigger with phrases like "set up replication", "implement sharding", or "scale database".

54%

Overall

Validation — 81%

Implementation — 20%

Activation — 82%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

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 masquerading as database replication guidance. It contains no actual replication-specific content—no mention of primary/replica setup, replication lag monitoring, failover procedures, or specific database systems (PostgreSQL, MySQL, etc.). The entire content could apply to literally any technical task, wasting tokens on obvious best practices Claude already knows.

Suggestions

Replace generic steps with specific replication commands (e.g., PostgreSQL streaming replication setup, MySQL GTID configuration, or MongoDB replica set initialization)

Add executable code examples showing actual replication configuration, such as `pg_basebackup` commands or `CHANGE MASTER TO` statements

Include specific validation commands like checking replication lag (`SELECT pg_last_wal_replay_lsn()`) or replica status queries

Remove all generic advice Claude already knows (backup data, test in staging, monitor for issues) and focus only on replication-specific knowledge

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 replication-specific content despite the title.	1 / 3
Actionability	No concrete code, commands, or database-specific instructions. Everything is abstract guidance like 'Execute implementation' and 'Verify changes work as expected' without any actual replication setup commands, configuration examples, or specific tools.	1 / 3
Workflow Clarity	Steps are clearly numbered and sequenced with a logical flow from assessment to deployment. However, validation checkpoints are vague ('run comprehensive tests') with no specific validation commands or criteria for database replication scenarios.	2 / 3
Progressive Disclosure	References external files for templates, docs, and examples which is good structure, but the main content is a wall of generic text. The referenced files use placeholder paths and the 'Examples' section is empty, promising content 'in context' rather than providing it.	2 / 3
	Total	6 / 12 Passed

Activation

82%

The description provides good trigger term coverage and completeness with explicit trigger phrases, making it clear when to use the skill. However, the specificity of capabilities is weakened by vague language like 'comprehensive guidance and automation' without detailing concrete actions. The opening phrase 'Process use when' appears to be a grammatical error that reduces clarity.

Suggestions

Replace vague 'comprehensive guidance and automation' with specific concrete actions (e.g., 'Configure master-slave replication, set up horizontal sharding, partition data across nodes')

Fix the grammatical error in 'Process use when' - should likely be 'Use when' or rephrase the opening sentence entirely

Dimension	Reasoning	Score
Specificity	Names the domain (database scalability) and mentions specific actions (replication and sharding), but lacks comprehensive detail about what concrete operations are performed beyond vague 'guidance and automation'.	2 / 3
Completeness	Clearly answers both what (replication and sharding with guidance and automation) and when (explicit trigger phrases provided). Has explicit 'Trigger with phrases like...' clause serving as the 'Use when' guidance.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases users would say: 'set up replication', 'implement sharding', 'scale database'. These are realistic terms users would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Focuses on database scalability which is somewhat specific, but 'replication' and 'sharding' could overlap with other database-related skills. The triggers help but the domain could still conflict with general database administration skills.	2 / 3
	Total	10 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

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.