database-sharding
tessl i github:secondsky/claude-skills --skill database-shardingDatabase sharding for PostgreSQL/MySQL with hash/range/directory strategies. Use for horizontal scaling, multi-tenant isolation, billions of records, or encountering wrong shard keys, hotspots, cross-shard transactions, rebalancing issues.
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | 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
85%This is a strong, well-structured skill with excellent actionability and progressive disclosure. The code examples are executable and production-ready, workflows include validation checkpoints, and references are clearly signaled. Minor verbosity in duplicated content (error summaries appearing twice) and some obvious commentary slightly reduce token efficiency.
Suggestions
Remove the 'Known Issues Prevention' section as it duplicates the 'Top 7 Critical Errors' content - a simple reference to the error catalog would suffice
Trim obvious commentary like '(slow!)' and '(500x faster!)' - the numbers speak for themselves
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the error catalog is summarized twice (in Top 7 Critical Errors and Known Issues Prevention sections), and some explanations like 'Query time: 5000ms (slow!)' state the obvious. The tables and checklists are well-structured but could be tighter. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code examples, specific SQL queries, concrete configuration patterns, and copy-paste ready router implementations. The before/after production example clearly demonstrates real-world application. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints. The Quick Start provides numbered steps, the Complete Setup Checklist has verification items, and the error fixes show clear before/after patterns. The 'Before Sharding' checklist ensures validation before proceeding. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear Quick Start, well-organized sections, and explicit 'When to Load References' guidance pointing to one-level-deep reference files. The 'Load references/...' pattern clearly signals where to find detailed information. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
100%This is an excellent skill description that clearly defines its scope (database sharding), supported technologies (PostgreSQL/MySQL), specific strategies (hash/range/directory), and explicit trigger conditions covering both proactive use cases (horizontal scaling, multi-tenant) and reactive troubleshooting scenarios (hotspots, rebalancing issues). The description uses proper third-person voice and provides comprehensive trigger terms that database engineers would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: 'Database sharding', 'hash/range/directory strategies', 'horizontal scaling', 'multi-tenant isolation', 'billions of records', and specific issues like 'wrong shard keys, hotspots, cross-shard transactions, rebalancing issues'. | 3 / 3 |
Completeness | Clearly answers both what ('Database sharding for PostgreSQL/MySQL with hash/range/directory strategies') and when ('Use for horizontal scaling, multi-tenant isolation, billions of records, or encountering wrong shard keys, hotspots, cross-shard transactions, rebalancing issues'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'sharding', 'PostgreSQL', 'MySQL', 'horizontal scaling', 'multi-tenant', 'hotspots', 'cross-shard transactions', 'rebalancing'. These are terms database engineers naturally use when facing scaling challenges. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche focus on database sharding specifically for PostgreSQL/MySQL. The specific strategies (hash/range/directory) and problem domains (hotspots, cross-shard transactions) make it unlikely to conflict with general database or scaling skills. | 3 / 3 |
Total | 12 / 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.