managing-database-sharding
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-shardingProcess 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no actual database sharding content. It reads like a project management checklist that could apply to any technical task. A skill about sharding should include specific strategies (consistent hashing, range partitioning), shard key selection guidance, concrete code examples for routing queries, and validation steps for data distribution - none of which are present.
Suggestions
Replace generic steps with sharding-specific content: shard key selection criteria, partitioning strategies (hash vs range vs directory), and when to use each approach
Add executable code examples showing shard routing logic, cross-shard query patterns, and migration scripts for splitting/rebalancing shards
Include concrete validation steps: verify even data distribution, test cross-shard joins, validate shard key cardinality
Remove boilerplate sections (Prerequisites, Error Handling) that contain only generic advice Claude already knows, and replace with sharding-specific gotchas and failure modes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no sharding-specific content - phrases like 'Review current configuration' and 'Define optimal approach based on best practices' are filler that Claude already knows. The entire document could be replaced with actual sharding guidance in a fraction of the tokens. | 1 / 3 |
Actionability | No concrete code, commands, or sharding-specific examples. Instructions like 'Execute implementation in non-production environment first' are vague platitudes. Missing: actual sharding strategies (hash-based, range-based), shard key selection criteria, specific database commands, migration scripts, or routing logic examples. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management phases rather than sharding-specific workflows. No validation checkpoints specific to sharding (e.g., verify data distribution, test cross-shard queries, validate shard key uniqueness). The workflow would apply equally to any database task. | 2 / 3 |
Progressive Disclosure | References external files in a structured way (templates, docs, examples directories), but the main content is a wall of generic text. The referenced files use placeholder paths that may not exist. The 'Overview' section appears at the end and adds nothing, and 'Examples' promises content 'in context' without delivering any. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%The description effectively communicates when to use the skill with explicit trigger phrases and establishes a clear niche around database sharding. However, it lacks specificity in describing concrete actions - it mentions 'comprehensive guidance and automation' without detailing what specific sharding operations it can perform.
Suggestions
Add specific concrete actions like 'partition tables by key', 'configure shard routing', 'rebalance data across shards', or 'set up cross-shard queries' to improve specificity.
Replace vague terms like 'comprehensive guidance and automation' with actual capabilities the skill provides.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database sharding) and mentions 'horizontal sharding strategies' and 'automation', but lacks specific concrete actions like 'partition tables', 'configure shard keys', or 'migrate data between shards'. | 2 / 3 |
Completeness | Clearly answers both what ('horizontal sharding strategies with comprehensive guidance and automation') and when ('Trigger with phrases like...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'implement sharding', 'shard database', 'distribute data'. These are realistic terms a user would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Database sharding is a clear niche with distinct triggers. Unlikely to conflict with general database skills due to specific sharding terminology like 'shard', 'distribute data', 'horizontal sharding'. | 3 / 3 |
Total | 11 / 12 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.