managing-database-partitions
Process use when you need to work with database partitioning. This skill provides table partitioning strategies with comprehensive guidance and automation. Trigger with phrases like "partition tables", "implement partitioning", or "optimize large tables".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-partitions51
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 description has strong trigger term coverage and completeness with explicit usage guidance. The main weakness is the lack of specific concrete actions - it describes the domain well but doesn't enumerate what specific partitioning operations it can perform (e.g., range vs hash partitioning, partition maintenance, migration strategies).
Suggestions
Add specific concrete actions like 'create range/hash/list partitions', 'migrate existing tables to partitioned schemas', 'analyze partition performance', or 'manage partition maintenance'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database partitioning) and mentions 'table partitioning strategies' and 'automation', but lacks specific concrete actions like 'create range partitions', 'migrate existing tables', or 'analyze partition performance'. | 2 / 3 |
Completeness | Clearly answers both what ('table partitioning strategies with comprehensive guidance and automation') and when ('Trigger with phrases like...' provides explicit trigger guidance). Has explicit 'Use when' equivalent clause. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'partition tables', 'implement partitioning', 'optimize large tables'. These are realistic terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Database partitioning is a clear niche with distinct triggers. Terms like 'partition tables' and 'implement partitioning' are specific enough to avoid conflicts with general database or optimization skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with no actual database partitioning content. It provides abstract software development lifecycle steps that could apply to any technical task, completely failing to teach Claude anything specific about partition strategies (range, list, hash), partition maintenance, or partition-specific SQL syntax. The skill wastes tokens on boilerplate while providing zero actionable partitioning guidance.
Suggestions
Add concrete SQL examples for creating partitions (e.g., CREATE TABLE with PARTITION BY RANGE/LIST/HASH syntax for PostgreSQL, MySQL, or target database)
Include specific partition maintenance commands: adding/dropping partitions, partition pruning verification, and data migration between partitions
Replace generic SDLC steps with partitioning-specific workflow: analyze table size/access patterns → choose partition strategy → implement partition scheme → validate partition pruning in query plans → monitor partition distribution
Add decision criteria for choosing partition types (range for time-series, list for categorical, hash for even distribution) with concrete examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no database partitioning-specific content - just generic software development lifecycle steps that Claude already knows. Every section could apply to literally any technical task. | 1 / 3 |
Actionability | No concrete code, SQL examples, or specific partitioning commands. Entirely abstract guidance like 'Review current configuration' and 'Define optimal approach' without any executable examples of partition creation, maintenance, or management. | 1 / 3 |
Workflow Clarity | While steps are numbered, they are generic SDLC phases with no partitioning-specific validation. Missing critical partitioning workflows like: checking partition alignment, validating partition pruning, testing partition switching, or verifying data distribution across partitions. | 1 / 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 appear to be placeholders rather than real resources, and the skill body itself lacks any substantive content to disclose progressively. | 2 / 3 |
Total | 5 / 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 — 13 / 16 Passed
Validation for skill structure
| 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 | |
- 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.