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".
74
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/database-partition-manager/skills/managing-database-partitions/SKILL.mdQuality
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.
The description adequately identifies its niche (database partitioning) and provides explicit trigger phrases, making it functional for skill selection. However, it lacks specificity in the concrete actions it performs—'comprehensive guidance and automation' is vague fluff rather than listing specific capabilities like range/hash/list partitioning, partition pruning, or migration strategies. The opening phrase 'Process use when' is awkward and grammatically unclear.
Suggestions
Replace 'comprehensive guidance and automation' with specific concrete actions, e.g., 'Creates range, hash, and list partitions, migrates existing tables to partitioned schemas, and configures partition pruning.'
Fix the awkward opening 'Process use when you need to work with database partitioning' to something clearer like 'Implements database table partitioning strategies including...' to improve readability and use proper third-person voice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database partitioning) and mentions 'table partitioning strategies' and 'guidance and automation', but does not list multiple specific concrete actions like creating range partitions, hash partitions, managing partition maintenance, etc. | 2 / 3 |
Completeness | Explicitly answers both 'what' (provides table partitioning strategies with guidance and automation) and 'when' (trigger phrases like 'partition tables', 'implement partitioning', 'optimize large tables'). The 'Use when' equivalent is present via 'Process use when you need to work with database partitioning' and the trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'partition tables', 'implement partitioning', 'optimize large tables', and 'database partitioning'. These cover common variations of how users would phrase partitioning requests. | 3 / 3 |
Distinctiveness Conflict Risk | Database partitioning is a clear, specific niche. The trigger terms ('partition tables', 'implement partitioning') are distinct and unlikely to conflict with other skills like general database optimization or table creation. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of database partitioning across PostgreSQL and MySQL with a well-structured workflow and useful error handling table. However, it falls short on actionability by providing fragmented SQL snippets rather than complete, executable scripts, and the workflow lacks explicit rollback/recovery steps for destructive operations like data migration and table renames. The content is moderately concise but could be tightened by removing explanatory prose Claude already knows and replacing narrative examples with executable code blocks.
Suggestions
Replace inline SQL fragments with complete, executable script blocks for each major operation (partition creation, data migration, maintenance) that can be copy-pasted and adapted.
Add explicit rollback and error recovery steps to the migration workflow (step 6), such as what to do if row counts don't match or if the atomic rename fails.
Split PostgreSQL-specific and MySQL-specific guidance into separate referenced files to reduce the monolithic nature and improve progressive disclosure.
Convert the narrative examples section into concrete code examples with actual DDL statements rather than prose descriptions of outcomes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elaboration. The prerequisites section explains basic concepts Claude would know (what psql is, what permissions are needed). The examples section uses narrative descriptions rather than concise code examples. Several inline SQL snippets could be more tightly formatted. | 2 / 3 |
Actionability | Provides some concrete SQL commands inline (CREATE TABLE, ALTER TABLE, EXPLAIN) but they are fragmented and incomplete rather than copy-paste ready scripts. The migration workflow in step 6 mixes prose with partial SQL. No complete, executable script is provided for any of the core operations—most guidance is descriptive with SQL fragments embedded in prose. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced and covers the full lifecycle from identification to verification. Step 6 includes a migration workflow with verification (row count matching) and step 10 includes EXPLAIN-based validation. However, there are no explicit feedback loops for error recovery during migration (e.g., what to do if row counts don't match, or if the rename fails mid-way). For destructive operations like table renames and partition detachment, the lack of rollback guidance caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files to reference. While it has clear section headers (Overview, Instructions, Output, Error Handling, Examples, Resources), the instructions section is quite long and could benefit from splitting detailed PostgreSQL vs MySQL guidance into separate reference files. External URLs are provided but no internal file references exist for deeper content. | 2 / 3 |
Total | 8 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.