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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-replication77
Quality
51%
Does it follow best practices?
Impact
79%
1.08xAverage score across 12 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/database-replication-manager/skills/managing-database-replication/SKILL.mdDiscovery
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 provides adequate trigger terms and completeness with explicit usage guidance, but suffers from vague capability descriptions ('comprehensive guidance and automation' is fluff). The opening 'Process use when' is awkward phrasing. The skill would benefit from more concrete action verbs describing what it actually does.
Suggestions
Replace vague 'comprehensive guidance and automation' with specific actions like 'configure replica sets, partition data across shards, set up failover'
Fix the awkward opening 'Process use when' to proper third-person voice like 'Configures database scalability through replication and sharding'
| 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 'guidance and automation'. | 2 / 3 |
Completeness | Explicitly answers both what (replication and sharding with guidance and automation) and when (trigger phrases clearly stated). Has explicit 'Trigger with phrases like' clause providing clear usage guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'set up replication', 'implement sharding', 'scale database'. These are realistic user requests that map well to the skill's purpose. | 3 / 3 |
Distinctiveness Conflict Risk | Focuses on database scalability which is somewhat specific, but 'database' is broad and could overlap with other database-related skills. The replication/sharding focus helps but isn't fully distinctive. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with no actual database replication content. It reads like a project management checklist that could apply to any technical task. There are no replication-specific concepts (primary/replica setup, sync modes, failover, lag monitoring), no executable commands, and no concrete examples despite claiming to help with 'replication and sharding'.
Suggestions
Add concrete, executable examples for setting up replication (e.g., PostgreSQL streaming replication commands, MySQL replica configuration)
Include specific validation commands like checking replication lag, verifying sync status, or testing failover
Remove generic advice Claude already knows (backup data, test in staging) and replace with replication-specific guidance
Add actual code examples for common sharding patterns with specific database technologies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts like 'backup critical data' and 'test in staging' that Claude already knows. No database replication-specific content despite the title. | 1 / 3 |
Actionability | Entirely abstract with no concrete code, commands, or database-specific examples. Instructions like 'Execute implementation' and 'Review current configuration' provide zero executable guidance for actual replication setup. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management phases rather than database replication workflows. No specific validation commands, no replication-specific checkpoints, no concrete verification steps. | 2 / 3 |
Progressive Disclosure | References external files in Resources section which is good structure, but the main content is a wall of generic text. The referenced files use placeholder paths and may not exist. 'Examples' section promises examples but delivers none. | 2 / 3 |
Total | 6 / 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.
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 | |
- 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.