data-partitioner
Data Partitioner - Auto-activating skill for Data Pipelines. Triggers on: data partitioner, data partitioner Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill data-partitionerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any explanation of capabilities, uses redundant trigger terms, and provides no guidance on when Claude should select this skill. The only positive element is the category association which provides minimal context.
Suggestions
Add specific actions the skill performs, e.g., 'Partitions large datasets by date, key ranges, or hash values for distributed processing'
Include a 'Use when...' clause with natural trigger terms like 'split data', 'partition by', 'shard table', 'distribute across nodes', 'chunk dataset'
Specify the data types or systems this works with (e.g., 'database tables', 'Parquet files', 'streaming data') to distinguish from other data processing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Data Partitioner') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what partitioning means or what operations it performs. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the skill name and category without explaining functionality or providing explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data partitioner' repeated twice, which is redundant and unlikely to match natural user language. Users would more likely say 'split data', 'partition table', 'shard', or 'distribute data'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Data Partitioner' is somewhat specific to a niche function, the lack of detail about what kind of partitioning (database, file, streaming) means it could overlap with other data processing skills. The category mention provides some context. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what a data partitioner skill should do without providing any actual guidance, code examples, partitioning strategies, or concrete instructions. The entire content could be replaced with a single sentence: 'This skill helps with data partitioning' without losing any information.
Suggestions
Add concrete code examples showing common data partitioning patterns (e.g., hash partitioning, range partitioning, time-based partitioning) with executable Python/Spark code
Define a clear workflow for implementing data partitioning: analyze data distribution → choose partition strategy → implement partitioner → validate partition balance
Include specific guidance on partition key selection, optimal partition sizes, and common pitfalls to avoid
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actionable technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually partition data or provides any executable examples. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no validation checkpoints or sequences for data partitioning operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or related documentation. It mentions 'Related Skills' but provides no actual links or navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 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.