managing-database-sharding
Process use when you need to work with database sharding. This skill provides horizontal sharding strategies with comprehensive guidance and automation. Trigger with phrases like "implement sharding", "shard database", or "distribute data".
54
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/database-sharding-manager/skills/managing-database-sharding/SKILL.mdQuality
Discovery
40%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 identifies a clear domain (database sharding) and provides some trigger phrases, but it fails to list specific concrete actions the skill performs. The language is padded with vague terms like 'comprehensive guidance and automation' without explaining what that entails. The opening 'Process use when' is grammatically awkward and the overall description lacks the specificity needed to confidently select this skill over alternatives.
Suggestions
Replace vague language like 'comprehensive guidance and automation' with specific actions such as 'configure shard keys, partition tables, set up consistent hashing, rebalance data across shards'.
Expand trigger terms to include common variations like 'horizontal scaling', 'partition data', 'shard key selection', 'database partitioning', and specific database technologies.
Fix the awkward opening ('Process use when') and restructure to clearly separate 'what it does' from 'when to use it' with an explicit 'Use when...' clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'horizontal sharding strategies with comprehensive guidance and automation' but does not list any concrete actions. There are no specific capabilities like 'partition tables', 'configure shard keys', 'rebalance shards', etc. — it's vague and abstract. | 1 / 3 |
Completeness | It has a weak 'what' (horizontal sharding strategies with guidance and automation) and does include trigger phrases that serve as a partial 'when' clause. However, the 'what' is too vague to be truly useful, and the trigger guidance is presented awkwardly rather than as a clear 'Use when...' clause. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger phrases like 'implement sharding', 'shard database', and 'distribute data', which are natural terms a user might say. However, it misses common variations like 'partition', 'horizontal scaling', 'shard key', 'data distribution', or specific database names. | 2 / 3 |
Distinctiveness Conflict Risk | Database sharding is a reasonably specific niche, but the description is vague enough ('comprehensive guidance and automation') that it could overlap with general database management or scaling skills. The trigger terms help somewhat but are not highly distinctive. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive overview of database sharding but reads more like a reference guide than an actionable skill. It covers multiple databases and strategies broadly rather than providing deep, executable guidance for any single path. The lack of complete code examples, explicit validation checkpoints for destructive migration operations, and the monolithic structure weaken its practical utility.
Suggestions
Add executable, copy-paste ready code blocks for critical steps—especially data migration scripts with transaction wrapping, verification queries, and rollback procedures rather than just describing what to do.
Add explicit validation checkpoints with concrete commands (e.g., 'Run this query to verify row counts match before proceeding to step 8') and feedback loops for error recovery during migration.
Split per-database guidance (PostgreSQL/Citus, MySQL/Vitess, MongoDB) into separate referenced files to reduce the monolithic structure and improve progressive disclosure.
Remove explanatory descriptions of sharding strategies that Claude already understands and focus on project-specific decision criteria and executable implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some unnecessary verbosity and explanatory context that Claude would already know (e.g., explaining what hash-based vs range-based sharding is, general descriptions of sharding strategies). The examples section describes scenarios narratively rather than providing executable code. Could be tightened significantly. | 2 / 3 |
Actionability | Provides some concrete SQL queries for analysis (e.g., pg_total_relation_size, distribution checks) but most steps are descriptive rather than executable. No complete migration scripts, no routing configuration examples, no actual DDL templates. Steps like 'implement the routing layer' and 'migrate existing data' lack copy-paste ready code or commands. | 2 / 3 |
Workflow Clarity | The 10-step sequence is logically ordered and covers the full sharding lifecycle. However, validation checkpoints are weak—step 7 mentions 'verify row counts match' but doesn't provide explicit validation commands or feedback loops. For a destructive operation like data migration, there's no explicit 'stop and verify before proceeding' checkpoint or rollback procedure. | 2 / 3 |
Progressive Disclosure | The content is a monolithic document with all information inline. At ~100+ lines covering three different database systems, sharding strategies, migration, monitoring, and error handling, this would benefit from splitting detailed per-database instructions, migration scripts, and monitoring queries into separate referenced files. The Resources section links to external docs but no internal file references for detailed guidance. | 2 / 3 |
Total | 8 / 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 | |
- Commit
4dee593
- 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.