orchestrate

Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.

Quality

66%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/orchestrate/SKILL.md

Quality

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has good structure with explicit 'Use when' guidance and identifies the core domain of wiring components together. However, it lacks specific concrete actions and relies on somewhat generic trigger terms that could overlap with other development-focused skills. The description would benefit from more specific capability examples and distinctive trigger terms.

Suggestions

Add specific concrete actions like 'orchestrate multi-agent workflows', 'chain command outputs', or 'coordinate sequential task execution'

Include more natural trigger terms users might say: 'workflow', 'pipeline', 'orchestration', 'multi-step process', 'coordinate agents'

Dimension	Reasoning	Score
Specificity	Names the domain (Wire Commands, Agents, Skills) and mentions 'complex features' with phases (research, planning, implementation), but doesn't list concrete actions like 'orchestrate workflows', 'chain agent outputs', or 'coordinate multi-step tasks'.	2 / 3
Completeness	Clearly answers both what ('Wire Commands, Agents, and Skills together for complex features') and when ('Use when building features that need research, planning, and implementation phases') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms ('Commands', 'Agents', 'Skills', 'research', 'planning', 'implementation') but misses natural user phrases like 'workflow', 'orchestration', 'multi-step', 'pipeline', or 'coordinate'.	2 / 3
Distinctiveness Conflict Risk	'Complex features' and 'research, planning, implementation' are somewhat generic and could overlap with project management or general development skills. The specific mention of 'Commands, Agents, and Skills' helps but the trigger conditions are broad.	2 / 3
	Total	9 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a solid conceptual framework for multi-phase feature development with good structure and efficient token usage. However, it lacks concrete executable examples for invoking agents and specific validation procedures, making it more of a reference guide than actionable instructions. The references to other system components (agents, Pro-Workflow) would benefit from explicit links.

Suggestions

Add concrete examples showing how to invoke each agent (e.g., actual command syntax or delegation patterns)

Specify what 'quality gates' entail - what checks are run, what thresholds trigger holds, and how to handle failures

Add links to agent documentation files (e.g., 'See [AGENTS.md](AGENTS.md) for agent configuration')

Include an example of a GO/HOLD decision with sample confidence scoring criteria

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables and structured lists to convey information without unnecessary explanation. Every section serves a purpose and assumes Claude understands orchestration concepts.	3 / 3
Actionability	Provides clear conceptual guidance with numbered steps and decision criteria (70% confidence threshold), but lacks executable code examples or concrete commands. The agent references (scout, orchestrator, reviewer) are mentioned without showing how to invoke them.	2 / 3
Workflow Clarity	The multi-phase workflow is clearly sequenced with a visual diagram and numbered steps, but validation checkpoints are vague ('quality gates every 5 edits') without specifying what validation looks like or how to handle failures.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and a table for agent selection, but references to agents (scout, orchestrator, reviewer, debugger) and concepts (Pro-Workflow, self-correction loop) lack links to detailed documentation.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: rohitg00/pro-workflow
Commit: 57b813b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.