orchestrating-test-workflows
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill orchestrating-test-workflowsThis 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content describes capabilities at a high level but fails to provide actionable guidance. It lacks executable code examples, concrete plugin invocation syntax, and specific configuration details. The content explains concepts Claude already understands while omitting the specific information Claude would need to actually use the test-orchestrator plugin.
Suggestions
Add concrete code examples showing actual test-orchestrator plugin invocations with real syntax (e.g., workflow definition format, CLI commands, or API calls)
Remove explanatory sections like 'How It Works' and 'When to Use This Skill' - replace with executable quick-start examples
Include the actual configuration schema or DSL for defining test dependencies and workflows
Add validation steps and error handling guidance for when test orchestration fails
| 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 API calls. | 1 / 3 |
Workflow Clarity | The examples list high-level steps but provide no actual commands, validation checkpoints, or error handling. There's no concrete sequence Claude can follow to execute these workflows. | 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 API documentation, configuration schemas, or advanced usage patterns. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%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. The description uses proper third-person voice throughout.
| 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 |
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.