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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill orchestrating-test-workflows79
Quality
53%
Does it follow best practices?
Impact
97%
1.14xAverage score across 6 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/testing/test-orchestrator/skills/test-orchestrator/SKILL.mdDiscovery
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, explicit trigger guidance with a 'Use this skill when...' clause, natural user-facing keywords, and a distinct focus on test orchestration that differentiates it from general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'define test execution graphs with dependencies', 'execute tests in parallel', 'intelligently select tests to run based on code changes'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (orchestrate test workflows, define graphs, parallel execution, smart selection) AND when with explicit 'Use this skill when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'orchestrate tests', 'test workflow', 'parallel testing', 'smart test selection', 'test dependencies', '/orchestrate', plus mentions 'CI/CD integration for testing'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on test orchestration with distinct triggers like 'test execution graphs', 'parallel testing', '/orchestrate' command. Unlikely to conflict with general testing or code 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 describes what test orchestration is rather than teaching Claude how to do it. It lacks any executable code, specific plugin commands, configuration examples, or concrete syntax. The content reads like marketing copy rather than actionable technical guidance.
Suggestions
Add concrete plugin invocation examples showing actual command syntax (e.g., `test-orchestrator define --workflow workflow.yaml` or equivalent API calls)
Include a complete, executable workflow definition example with actual test dependency syntax
Replace abstract 'The skill will...' descriptions with copy-paste ready code blocks showing exact plugin usage
Add validation steps showing how to verify the workflow is correctly configured before execution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what parallelization is, what CI/CD pipelines are). Sections like 'How It Works' and 'When to Use This Skill' add little value and could be eliminated entirely. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The examples describe what the skill 'will do' in abstract terms rather than showing actual plugin invocations, configuration syntax, or command-line usage. | 1 / 3 |
Workflow Clarity | The workflow steps are vague ('use the plugin to define', 'configure the pipeline') with no specific commands, validation checkpoints, or error handling. There's no clear sequence Claude can follow to actually orchestrate tests. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, but it's a monolithic document with no references to external files for detailed configuration, API reference, or advanced usage patterns. | 2 / 3 |
Total | 5 / 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.