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 for skill selection. It repeats the skill name as its only trigger term and fails to describe any concrete capabilities or usage scenarios. Without knowing what the skill actually does or when to use it, Claude would struggle to select it appropriately from a pool of skills.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Splits test suites into parallel groups, configures concurrent test execution across multiple workers, and optimizes test run times.'
Add an explicit 'Use when...' clause with natural trigger terms like 'run tests in parallel', 'speed up test suite', 'concurrent testing', 'parallel test execution', 'distribute tests across workers'.
Remove the duplicate trigger term and expand with varied natural language phrases 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 or scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'test parallelizer' repeated twice, which is extremely narrow and unlikely to match natural user language. Users might say 'run tests in parallel', 'speed up tests', 'parallelize test suite', 'concurrent test execution', etc., none of which are covered. | 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 generators) 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 template with no substantive content. It contains only generic boilerplate descriptions that could apply to any skill topic, with no actual guidance on test parallelization—no code, no tool-specific instructions, no workflows, and no concrete examples. It provides zero value beyond what Claude already knows.
Suggestions
Add concrete, executable code examples for parallelizing tests in specific frameworks (e.g., pytest-xdist configuration, Jest --workers flag, parallel test runner setup).
Define a clear workflow: how to identify parallelizable tests, configure the runner, handle shared state/fixtures, and validate that parallel execution produces correct results.
Include specific guidance on common pitfalls like shared database state, file system conflicts, port collisions, and test isolation strategies.
Replace the boilerplate 'Purpose', 'When to Use', and 'Example Triggers' sections with actionable content—these meta-descriptions waste tokens and teach Claude nothing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about test parallelization. Every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There are no concrete code examples, commands, configurations, or specific instructions for parallelizing tests. The content only describes what the skill supposedly does in abstract terms without any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for how to actually parallelize tests in any framework, no validation checkpoints, and no sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to framework-specific guides, and no structured navigation to deeper content. The sections present are all superficial metadata rather than organized instructional content. | 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
3076d78
- 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.