test-parallelizer
Test Parallelizer - Auto-activating skill for Test Automation. Triggers on: test parallelizer, test parallelizer Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill test-parallelizer35
Quality
3%
Does it follow best practices?
Impact
91%
1.01xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/test-parallelizer/SKILL.mdDiscovery
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 severely underdeveloped, essentially providing only a skill name and category without any substantive content. It fails to explain what the skill does, what actions it performs, or when it should be used. Claude would have no meaningful basis for selecting this skill over others beyond exact phrase matching on 'test parallelizer'.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Splits test suites across multiple workers, configures parallel test runners, optimizes test distribution for faster CI/CD pipelines'
Include a 'Use when...' clause with natural trigger terms like 'run tests in parallel', 'speed up test suite', 'concurrent test execution', 'distribute tests across workers', 'pytest-xdist', 'parallel CI'
Remove the duplicate trigger term and expand with variations users would naturally say when needing test parallelization help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Test Parallelizer') and mentions 'Test Automation' but provides no concrete actions. There is no explanation of what the skill actually does - no verbs describing capabilities like 'splits tests', 'distributes workloads', or 'optimizes test execution'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just the skill name repeated. There is no explicit guidance on when Claude should select this skill or what user requests would trigger it. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'test parallelizer' repeated twice, which is the skill name itself. Missing natural user phrases like 'run tests in parallel', 'speed up tests', 'concurrent testing', 'distribute test suite', or 'parallel test execution'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Test Parallelizer' is somewhat specific and wouldn't broadly conflict with general coding skills, but 'Test Automation' is generic enough to potentially overlap with other testing-related skills. The lack of specific capabilities makes it harder to distinguish from other test-related tools. | 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 actual content about test parallelization. It contains only generic boilerplate describing what a skill should do, without any concrete guidance, code examples, or actionable instructions. The skill fails to teach Claude anything about parallelizing tests.
Suggestions
Add concrete code examples showing how to configure test parallelization in specific frameworks (e.g., pytest-xdist, Jest workers, JUnit parallel execution)
Include a workflow for safely parallelizing tests: identifying stateful tests, isolating shared resources, configuring thread/process counts
Provide specific guidance on common parallelization pitfalls (database state, file locks, port conflicts) with solutions
Remove all generic boilerplate ('provides step-by-step guidance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about test parallelization. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance on how to parallelize tests. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. Test parallelization involves specific decisions (thread pools, test isolation, shared state handling) but none are addressed. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no structure for discovery or deeper learning. | 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 | |
- 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.