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".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-partition-manager/skills/managing-database-partitions/SKILL.md

Quality

Content

80%Weight 40%Scale 1-3

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

The content is lean, highly actionable, and densely packed with executable SQL and a useful error table, but the migration workflow lacks an explicit recovery feedback loop and the skill does not leverage its bundle files for progressive disclosure. Adding a validation gate and referencing the planned scripts/templates would round it out.

Suggestions

Make the migration feedback loop explicit, e.g. 'Verify row counts match; if they differ, re-copy the missing batch before renaming' and gate the atomic rename on a passing check ('Only when counts match: RENAME TABLE').

Populate and reference the bundle files — move the partition DDL templates into assets/partition_template.sql and the generation logic into scripts/partition_design.py, then link them from the relevant steps so progressive disclosure is real rather than placeholder TODOs.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich with no preamble explaining concepts Claude already knows; every section (Prerequisites, Instructions, Error Handling, Examples) earns its place and justifications like 'vastly faster than DELETE' are useful rather than padding.	3 / 3
Actionability	It provides concrete, largely copy-paste-ready SQL — CREATE TABLE ... PARTITION BY RANGE, PARTITION OF ... FOR VALUES FROM, ALTER TABLE ... PARTITION BY, batch INSERT migration, DETACH PARTITION, and EXPLAIN verification — across both PostgreSQL and MySQL.	3 / 3
Workflow Clarity	The 10-step sequence is clearly ordered with validation checkpoints ('Verify row counts match', EXPLAIN pruning check), but the destructive batch migration lacks an explicit fix-retry feedback loop, so per the rubric's database/batch-operations note workflow_clarity is capped at 2 rather than reaching 3.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic at ~75 lines, and the existing bundle directories (references/, scripts/, assets/) hold only placeholder READMEs that are never referenced from the body, so content that could be split out (detailed examples, SQL templates, maintenance scripts) is inline rather than appropriately distributed.	2 / 3
	Total	10 / 12 Passed

Description

80%Weight 40%Scale 1-3

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 has strong triggers, completeness, and distinctiveness, but its capability statement is vague and fluffy ('comprehensive guidance and automation') and slips into second-person voice. Tightening the 'what' into concrete actions would lift the specificity score.

Suggestions

Replace 'work with database partitioning' and 'comprehensive guidance and automation' with concrete actions, e.g. 'Creates range/list/hash partitions, migrates unpartitioned tables, and automates partition maintenance for PostgreSQL and MySQL.'

Rewrite in third person to remove 'you need to' (e.g. 'Use when working with database partitioning') to avoid the specificity penalty.

Dimension	Reasoning	Score
Specificity	The description names the domain but only vague actions ('work with database partitioning', 'table partitioning strategies with comprehensive guidance and automation'), with no concrete capabilities listed; per the rubric, the second-person phrasing 'when you need to work with' reduces the specificity score by 1 from a base of 2.	1 / 3
Completeness	It explicitly answers both what ('provides table partitioning strategies with comprehensive guidance and automation') and when ('use when you need to work with database partitioning' plus an explicit 'Trigger with phrases like' clause), so it is not capped at 2.	3 / 3
Trigger Term Quality	It supplies three natural trigger phrases a user would actually say — 'partition tables', 'implement partitioning', 'optimize large tables' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Database partitioning is a clear, narrow niche with distinct triggers unlikely to collide with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-partition-manager/skills/managing-database-partitions/SKILL.md
Commit: c4eafaf

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.