database-sharding
Database 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.
92
92%
Does it follow best practices?
Impact
92%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
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 |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and progressive disclosure. The code examples are executable and production-ready, workflows are clear with validation steps, and references are well-organized. Minor verbosity issues exist with some redundant content (error catalog summarized twice) and obvious commentary, but overall this skill effectively teaches database sharding patterns.
Suggestions
Remove the 'Known Issues Prevention' section as it duplicates the 'Top 7 Critical Errors' content - a simple cross-reference would suffice
Trim obvious commentary like '(slow!)' and '(500x faster!)' - the metrics 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 with specific metrics (10ms vs 5000ms) is particularly useful. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints: Quick Start has numbered steps, the Complete Setup Checklist provides verification gates, and error patterns include symptom → fix sequences. The 'Before Sharding' checklist ensures validation before proceeding. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear Quick Start section, well-organized 'When to Load References' section that signals exactly when to access deeper content, and one-level-deep references to templates and reference docs. Navigation is intuitive. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.