test-parallelizer
Test Parallelizer - Auto-activating skill for Test Automation. Triggers on: test parallelizer, test parallelizer Part of the Test Automation skill category.
35
3%
Does it follow best practices?
Impact
91%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/test-parallelizer/SKILL.mdQuality
Discovery
7%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 is essentially a placeholder that provides almost no useful information beyond the skill's name. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select it. The repeated trigger term and boilerplate category mention do not help Claude distinguish this skill from others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Splits test suites across parallel workers, configures concurrent test execution, and optimizes test run times by distributing tests evenly.'
Add a 'Use when...' clause with natural trigger terms like 'run tests in parallel', 'speed up test suite', 'parallelize tests', 'concurrent testing', 'distribute tests across workers'.
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say when needing this capability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Test Automation') and the concept ('Test Parallelizer') but provides no concrete actions. There is no indication of what the skill actually does—no verbs describing specific capabilities like 'splits test suites', 'distributes tests across workers', or 'configures parallel execution'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'test parallelizer' repeated twice. There are no natural variations a user might say such as 'parallel tests', 'run tests in parallel', 'speed up tests', 'concurrent test execution', or 'parallelize test suite'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'test parallelizer' is fairly niche and unlikely to conflict with many other skills, but the lack of specificity about what it does versus other test automation skills (e.g., test runners, test splitters) means there could be overlap within the test automation category. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no substantive content. It contains only generic boilerplate descriptions about what the skill supposedly does without providing any actual guidance, code, commands, or workflows for test parallelization. It fails on every dimension because it teaches Claude nothing actionable.
Suggestions
Add concrete, executable code examples showing how to configure test parallelization in specific frameworks (e.g., pytest-xdist, Jest --workers, JUnit parallel execution).
Define a clear workflow: e.g., 1) Identify test independence, 2) Configure parallel runner, 3) Handle shared state/fixtures, 4) Validate no flaky tests introduced by parallelism.
Include specific commands and configuration snippets (e.g., `pytest -n auto`, Jest `maxWorkers` config) instead of abstract descriptions of capabilities.
Remove all generic filler sections ('Purpose', 'When to Use', 'Example Triggers') that provide no actionable information and replace with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing it doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous and waste tokens without conveying any actionable information about test parallelization. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific tools, no configuration examples, no actual steps for parallelizing tests. The entire content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic boilerplate with no references to detailed materials, no links to examples, configuration files, or advanced guides. There is no meaningful structure beyond placeholder headings. | 1 / 3 |
Total | 4 / 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
3e83543
- 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.