orchestrating-test-workflows
This skill enables Claude to orchestrate complex test workflows using the test-orchestrator plugin. It allows Claude to define test execution graphs with dependencies, execute tests in parallel, and intelligently select tests to run based on code changes. Use this skill when a user requests test orchestration, dependency management for tests, parallel test execution, smart test selection, or CI/CD integration for testing. Trigger terms include "orchestrate tests", "test workflow", "parallel testing", "smart test selection", "test dependencies", and "/orchestrate".
63
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/test-orchestrator/skills/test-orchestrator/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly articulates specific capabilities, provides explicit trigger guidance with a 'Use this skill when...' clause, and lists concrete trigger terms. It is well-differentiated from general testing skills by focusing on orchestration, dependency graphs, and parallel execution. Minor improvement could come from slightly more concise phrasing, but overall it meets all rubric criteria at a high level.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: 'define test execution graphs with dependencies', 'execute tests in parallel', and 'intelligently select tests to run based on code changes'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | The description clearly answers both 'what' (orchestrate complex test workflows, define execution graphs, parallel execution, smart test selection) and 'when' (explicit 'Use this skill when...' clause with specific trigger scenarios and terms). | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger terms users would say: 'orchestrate tests', 'test workflow', 'parallel testing', 'smart test selection', 'test dependencies', '/orchestrate', and also mentions 'CI/CD integration for testing'. These cover a good range of natural user language. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around test orchestration specifically, with distinct concepts like 'test execution graphs', 'dependency management for tests', and the '/orchestrate' command. This is unlikely to conflict with general testing or CI/CD skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content reads like a marketing description rather than actionable instructions. It lacks any concrete code examples, plugin API calls, configuration syntax, or executable commands that would allow Claude to actually use the test-orchestrator plugin. The content is verbose, abstract, and explains concepts Claude already understands while failing to provide the specific technical details needed to perform the task.
Suggestions
Replace the abstract 'How It Works' and 'Examples' sections with concrete, executable code showing how to invoke the test-orchestrator plugin, define a dependency graph, and configure parallel execution (e.g., actual API calls or CLI commands).
Remove the 'When to Use This Skill' and 'Overview' sections which restate the skill description; instead, jump directly into a quick-start example with real plugin syntax.
Add a concrete workflow with validation steps, such as: define graph → validate dependencies → execute → check results → handle failures.
Include actual configuration examples (e.g., YAML/JSON workflow definitions, plugin invocation syntax) instead of describing what the skill 'will do' in narrative form.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with explanations Claude doesn't need ('This skill empowers Claude to...', 'When to Use This Skill', explaining what parallelization and smart selection mean). The 'How It Works' section describes concepts at a high level without adding actionable value. Much of the content restates the description rather than providing new, useful information. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no API calls, no configuration examples, and no copy-paste ready snippets. The examples describe what the skill 'will do' in abstract terms rather than showing how to actually invoke the test-orchestrator plugin, define a workflow graph, or configure dependencies. Everything is vague description rather than instruction. | 1 / 3 |
Workflow Clarity | The multi-step processes described in the examples are abstract narratives ('The skill will: 1. Use the plugin to identify... 2. Execute those tests...') with no actual commands, validation checkpoints, or error recovery steps. There is no concrete workflow that Claude could follow to orchestrate tests. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, which provides some structure. However, there are no references to external files, no bundle files to reference, and the content is somewhat monolithic with sections that could be trimmed rather than split. The organization is reasonable but the content itself doesn't warrant the number of sections used. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.