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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

65%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.

A highly actionable, command-dense skill body with clear sequencing, but it is held back by omitted validation feedback loops in the setup workflow and by a monolithic structure that ignores available bundle scripts. Conciseness is good though slightly padded with known concepts.

Suggestions

Add explicit validation checkpoints to the setup workflow (e.g. after pg_basebackup, verify with `SELECT pg_is_in_recovery()`; after replica start, confirm `pg_stat_replication` shows a connected row) to create validate->fix->retry loops.

Reference the bundled scripts from the body (e.g. "See [scripts/setup_replication.py](scripts/setup_replication.py) for automated setup" and a failover link) so the bundle is discoverable and the body can be slimmed.

Trim restatements of well-known concepts (leader election, WAL accumulation) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly dense and operational with executable commands, but includes concepts Claude already knows (e.g. "MongoDB handles leader election and failover automatically", "Stale replication slots... cause WAL accumulation and can fill the disk") and a few topology restatements that could be trimmed.	2 / 3
Actionability	Provides copy-paste-ready, executable commands throughout (pg_basebackup, CREATE ROLE, rs.initiate, CHANGE REPLICATION SOURCE TO, pg_stat_replication queries), with concrete configuration values.	3 / 3
Workflow Clarity	The 10 steps are clearly sequenced and include some checks (lag monitoring, failover testing), but setup lacks explicit validate->fix->retry checkpoints; per the rubric, missing verification steps in database operations caps this at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic: bundled scripts (scripts/setup_replication.py, scripts/failover.py) exist yet are never referenced from the body, and detailed setup content that could live in those files is inline.	2 / 3
	Total	9 / 12 Passed

Description

90%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 answers both what and when with explicit, natural trigger phrases and a distinct niche, though it is marred by a grammatically broken opening ("Process use when") and vague padding. Strong on triggers and completeness, weakest on concrete capability breadth.

Suggestions

Fix the broken opening so it reads as third-person voice, e.g. "Sets up and manages database replication and sharding. Use when...", avoiding the malformed "Process use when".

Replace "comprehensive guidance and automation" with 1-2 more concrete capabilities (e.g. failover automation, lag monitoring) to raise specificity.

Add a few common trigger variations (e.g. "read replicas", "failover", "primary-replica setup") to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names a domain and two concrete actions ("replication and sharding") but pads with vague fluff ("comprehensive guidance and automation") and does not enumerate multiple specific capabilities.	2 / 3
Completeness	States both what (replication and sharding) and when ("use when you need to work with database scalability" plus an explicit "Trigger with phrases like" clause), so neither half is missing or implied.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases a user would say ("set up replication", "implement sharding", "scale database"), each on-point and idiomatic.	3 / 3
Distinctiveness Conflict Risk	Database replication/sharding is a clear niche with specific, distinctive triggers unlikely to fire for unrelated skills.	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
Path: plugins/database/database-replication-manager/skills/managing-database-replication/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.