orchestration-protocols
Coordinates multiple agents with parallel task spawning, health monitoring, circuit breakers, and escalation paths. Use when managing parallel agents, handling agent timeouts, orchestrate agents, run tasks in parallel, concurrent agent execution, or fan-out tasks. Use when coordinating multi-agent task delegation.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 (parallel spawning, health monitoring, circuit breakers, escalation paths) and provides comprehensive trigger guidance with multiple natural keyword variations. It uses proper third-person voice and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'parallel task spawning', 'health monitoring', 'circuit breakers', and 'escalation paths'. These are distinct, concrete capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (coordinates multiple agents with parallel task spawning, health monitoring, circuit breakers, escalation paths) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'parallel agents', 'agent timeouts', 'orchestrate agents', 'run tasks in parallel', 'concurrent agent execution', 'fan-out tasks', 'multi-agent task delegation'. These cover many natural phrasings a user might employ. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around multi-agent orchestration and parallel execution. The specific terms like 'circuit breakers', 'fan-out tasks', and 'agent timeouts' make it highly distinguishable from general task management or single-agent skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality orchestration skill that provides concrete, actionable guidance with excellent workflow clarity and validation checkpoints throughout. The content is well-structured with tables for quick scanning, copy-paste ready commands, and explicit feedback loops for error recovery. The only minor weakness is that the progressive disclosure claim (REFERENCE.md) cannot be verified since no bundle files were provided, and the skill is moderately long for a single file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It uses tables for quick scanning, avoids explaining concepts Claude already knows (like what agents or worktrees are), and every section delivers actionable information without padding. The concrete example in Context Compaction is justified as it shows the exact format expected. | 3 / 3 |
Actionability | Provides copy-paste ready CLI commands, bash verification scripts, prompt templates, jq validation commands, and concrete examples. The parallel research protocol includes a specific prompt template and the validation table gives exact commands for each phase. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The Result Merge Protocol has numbered steps with two explicit checkpoints (verify all researchers returned results, confirm synthesized block covers all questions). The Validation & Verification Checkpoints table provides phase-by-phase checks with specific commands, including a blocker step that blocks merge on any failure. | 3 / 3 |
Progressive Disclosure | The skill references REFERENCE.md for Health & Recovery details, which is good progressive disclosure. However, no bundle files were provided to verify REFERENCE.md exists, and the main content is fairly long (~120 lines) with some sections like CLI examples and the full validation table that could potentially be split out. The structure is reasonable but the reference to REFERENCE.md cannot be verified. | 2 / 3 |
Total | 11 / 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.
- Repository
- monkilabs/opencastle
- Commit
cc13aaf
- 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.