CtrlK
BlogDocsLog inGet started
Tessl Logo

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

77

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/database/database-replication-manager/skills/managing-database-replication/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

82%

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 covers the basics adequately with explicit trigger phrases and a clear domain focus on database scalability. However, it lacks depth in specifying concrete actions beyond 'replication and sharding' and uses somewhat vague language like 'comprehensive guidance and automation.' The opening sentence is awkwardly phrased ('Process use when you need to...') which reduces clarity.

Suggestions

List more specific concrete actions such as 'configure replica sets, set up read replicas, define shard keys, partition collections, migrate data across shards' to improve specificity.

Improve distinctiveness by clarifying what types of databases are supported (e.g., MongoDB, PostgreSQL) or what distinguishes this from general database performance/optimization skills.

DimensionReasoningScore

Specificity

The description names the domain (database scalability) and mentions two specific actions (replication and sharding), but doesn't list concrete sub-actions like configuring replica sets, partitioning strategies, or monitoring. It remains somewhat surface-level.

2 / 3

Completeness

The description answers both 'what' (replication and sharding with guidance and automation) and 'when' (explicit trigger phrases and a 'Use when' equivalent in the first line). Both are explicitly stated.

3 / 3

Trigger Term Quality

Includes natural trigger phrases like 'set up replication', 'implement sharding', and 'scale database' which are terms users would naturally use. These cover the main use cases well.

3 / 3

Distinctiveness Conflict Risk

While 'replication' and 'sharding' are fairly specific, the broader 'scale database' trigger could overlap with skills covering database performance tuning, indexing, or query optimization. The niche is somewhat clear but not fully distinct.

2 / 3

Total

10

/

12

Passed

Implementation

64%

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 skill covering database replication across three major systems with concrete commands and configurations. Its main weaknesses are the lack of explicit validation/verification checkpoints between critical steps (e.g., confirming replication is active after setup) and the monolithic structure that packs three database systems' worth of instructions into a single file without progressive disclosure. Some content explains concepts Claude already knows (topology descriptions, scenario narratives) that could be trimmed.

Suggestions

Add explicit validation checkpoints after each major step—e.g., after pg_basebackup, verify with 'SELECT * FROM pg_stat_replication' on primary; after MySQL replica start, verify 'SHOW REPLICA STATUS\G' shows Replica_IO_Running: Yes and Replica_SQL_Running: Yes.

Split database-specific instructions into separate files (e.g., POSTGRESQL_REPLICATION.md, MYSQL_REPLICATION.md, MONGODB_REPLICATION.md) and keep SKILL.md as a concise overview with links to each.

Trim the topology explanation section and scenario-based examples—Claude understands these concepts. Replace with a brief decision table (workload type → topology) and keep examples focused on command sequences rather than performance narratives.

DimensionReasoningScore

Conciseness

The content is fairly dense and informative, but includes some unnecessary verbosity—e.g., the scenario-based examples section with performance numbers adds bulk without being directly actionable, and some explanations (topology descriptions, what cascading replication is) could be trimmed since Claude already knows these concepts.

2 / 3

Actionability

The skill provides concrete, executable commands and SQL statements for PostgreSQL, MySQL, and MongoDB replication setup. Configuration parameters, CLI commands (pg_basebackup, CHANGE REPLICATION SOURCE TO), and monitoring queries are all copy-paste ready with specific values.

3 / 3

Workflow Clarity

Steps are clearly sequenced and numbered, covering setup through monitoring and failover. However, there are no explicit validation checkpoints between steps—e.g., after pg_basebackup there's no 'verify replica is streaming' check, and after MySQL replica setup there's no 'confirm SHOW REPLICA STATUS shows Slave_IO_Running: Yes' verification step. For these multi-step, potentially destructive database operations, feedback loops are missing.

2 / 3

Progressive Disclosure

The content is a monolithic single file covering three database systems in full detail. With no bundle files, all PostgreSQL, MySQL, and MongoDB instructions are inline when they could be split into separate reference files. The Resources section links to external docs but there's no internal file structure for navigation. However, the sections are well-organized with clear headers.

2 / 3

Total

9

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.