CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/database-sharding/skills/database-sharding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-intentioned and comprehensive sharding guide with good structural elements (tables, checklists, error catalogs) but suffers from significant redundancy across sections and relies heavily on template/reference files that don't exist in the bundle. The content would benefit from deduplication and either inlining the critical template implementations or providing the actual bundle files. The workflow guidance lacks explicit validation steps for what is inherently a high-risk database operation.

Suggestions

Deduplicate content: the same errors appear in Critical Rules, Top 7 Errors, and Known Issues Prevention — consolidate into one authoritative section and reference it from others.

Add explicit validation/verification steps to the workflow (e.g., 'Run SELECT COUNT(*) per shard to verify distribution is within 20% tolerance before proceeding').

Either provide the template files (hash-router.ts, etc.) in the bundle or inline the core implementation so the code examples are actually executable rather than dependent on missing imports.

Trim the production example section — the before/after with inline comments explaining '500x faster' and CPU percentages is verbose; a compact table would suffice.

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but contains significant redundancy — the same errors and patterns are repeated across multiple sections (Critical Rules, Top 7 Errors, Known Issues Prevention, and the error catalog references). The production example section explains obvious performance improvements that Claude can infer. Tables like shard key selection criteria are useful but some content (e.g., explaining what a hotspot is) could be trimmed.

2 / 3

Actionability

Code examples are concrete and illustrative but rely on imported modules from templates (HashRouter, RangeRouter, etc.) that aren't provided in the bundle, making them not truly executable or copy-paste ready. The examples show usage patterns well but the actual implementations are deferred to missing template files. The SQL and TypeScript snippets in the error section are helpful but mix pseudocode-style comments with real code.

2 / 3

Workflow Clarity

The Quick Start provides a 3-step sequence and the Setup Checklist is comprehensive, but there are no explicit validation checkpoints or feedback loops for the sharding implementation process. For a destructive/complex operation like database sharding, the skill lacks verification steps (e.g., 'validate distribution after initial setup', 'run test queries to confirm routing'). The checklist is static rather than a workflow with error recovery.

2 / 3

Progressive Disclosure

The skill references many external files (6 reference docs, 4 templates) with a clear 'When to Load References' section, which is well-organized. However, no bundle files are actually provided, so all the deferred content is inaccessible. The main SKILL.md itself is quite long (~300 lines) with substantial inline content that overlaps with what the references supposedly contain, suggesting the split between overview and detail isn't clean.

2 / 3

Total

8

/

12

Passed

Description

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 a strong skill description that concisely covers specific capabilities, uses natural trigger terms that users would employ, and clearly delineates both what the skill does and when to use it. The description is well-structured with a clear 'Use for' clause that covers both proactive use cases (horizontal scaling, multi-tenant) and reactive troubleshooting scenarios (hotspots, rebalancing issues). It uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: database sharding, hash/range/directory strategies, horizontal scaling, multi-tenant isolation, and specific problem scenarios like wrong shard keys, hotspots, cross-shard transactions, and 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'). The 'Use for' clause serves as an explicit trigger guidance.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'sharding', 'PostgreSQL', 'MySQL', 'horizontal scaling', 'multi-tenant', 'billions of records', 'hotspots', 'cross-shard transactions', 'rebalancing', 'shard keys'. These are all terms a user dealing with database scaling would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: database sharding specifically for PostgreSQL/MySQL. The specific strategies (hash/range/directory) and problem domains (hotspots, cross-shard transactions) make it very unlikely to conflict with general database skills or other infrastructure skills.

3 / 3

Total

12

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

10

/

11

Passed

Repository
secondsky/claude-skills
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.