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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

72%

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

The body is highly actionable with executable commands for PostgreSQL, MySQL, and MongoDB, but keeps everything inline and omits explicit validation feedback loops for these destructive database operations.

Suggestions

Add explicit validation checkpoints after risky steps (e.g., verify replication is streaming with pg_stat_replication before declaring success; verify replica can connect before proceeding to failover setup).

Move the per-database setup detail and the error-handling table into reference files under references/ and link to them from the body to improve progressive disclosure.

Replace the generic auto-generated scripts/ files with actual replication setup, failover-test, and lag-monitor scripts that the body references by name.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, leading with executable commands and skipping basic concept explanations, but the ~105-line single-file treatment and prose around prerequisites/examples could still be trimmed; it falls between the tightenable (2) and lean-every-token-earns-its-place (3) anchors.	2.5 / 3
Actionability	It provides copy-paste-ready, executable commands throughout (pg_basebackup, CREATE ROLE, CHANGE REPLICATION SOURCE TO, rs.initiate, and concrete monitoring queries), matching the fully-executable anchor.	3 / 3
Workflow Clarity	The 10-step sequence is clearly ordered, but for destructive database operations it lacks explicit validate-then-proceed checkpoints and retry loops, which the rubric caps at 2.	2 / 3
Progressive Disclosure	All detail lives inline in a single monolithic body; the references/ and assets/ directories are empty (README only) and the bundled scripts are generic auto-generated templates not signaled from the body.	2 / 3
	Total	9.5 / 12 Passed

Description

90%

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 answers both what and when with natural trigger terms and a clear niche. It loses a little specificity by leaning on 'comprehensive guidance and automation' instead of enumerating concrete actions.

Suggestions

Replace 'comprehensive guidance and automation' with concrete actions (e.g., 'configure streaming/logical replication, set up read replicas, automate failover, monitor replication lag').

Tighten the awkward opening 'Process use when' to clean third-person phrasing such as 'Use when working with database scalability'.

Dimension	Reasoning	Score
Specificity	Names the domain ('database scalability') and concrete capabilities ('replication and sharding') but pads them with vague phrases like 'comprehensive guidance and automation' rather than listing multiple specific concrete actions.	2 / 3
Completeness	It explicitly answers both 'what' ('replication and sharding') and 'when' ('Use when you need to work with database scalability' plus explicit trigger phrases), satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	'Trigger with phrases like "set up replication", "implement sharding", or "scale database"' provides natural terms a user would actually say, matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The database replication/sharding niche with distinct trigger phrases is unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 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
Commit: 2cafb23

Reviewed: about 10 hours 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.