orchestrate

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

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/orchestrate/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

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

A lean, well-organized orchestration skill with clear sequencing and explicit validation gates. Its main weakness is underspecified mechanisms — confidence scoring and quality-gate criteria — that leave the actionability just short of fully executable.

Suggestions

Define how confidence is scored and what specific checks the "quality gates every 5 edits" run, so the implement phase is fully actionable rather than gated on an undefined mechanism.

Specify how the reviewer agent is invoked and what it checks, turning "Run the reviewer agent on changes" into a concrete, repeatable step.

Clarify the self-correction loop trigger and recovery path rather than only referencing it in the Integration section.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-structured with a compact diagram, table, and bullets; it assumes Claude's competence and does not pad with concepts Claude already knows, so every section earns its place.	3 / 3
Actionability	It gives concrete guidance (specific agents, confidence threshold 70, gates every 5 edits, reviewer agent) but leaves key mechanisms unspecified — how confidence is scored, what the "quality gates" actually check — so it is not fully copy-paste ready.	2 / 3
Workflow Clarity	The 4-phase process and 6-step numbered usage list are clearly sequenced with explicit validation checkpoints (GO/HOLD at confidence 70, approval gate, review-before-commit) and a referenced self-correction feedback loop, matching the 3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the ~65-line skill is self-contained and well-organized into logical sections (Pattern, Usage, When to/Not to Use, Agent Selection, Integration), which per the rubric guidelines earns a 3 for skills with no need for external references.	3 / 3
	Total	11 / 12 Passed

Description

75%Weight 40%Scale 1-3

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

A solid description with explicit what/when structure and a distinct multi-phase trigger. It is held back from the top band by the abstract single verb "wire" and some technical jargon in place of natural user phrasing.

Dimension	Reasoning	Score
Specificity	It names the domain ("Wire Commands, Agents, and Skills together") and a single action (wire together) for "complex features", but does not enumerate multiple concrete actions the way a 3 requires (e.g. extract/fill/merge); the verb "wire" is also somewhat abstract.	2 / 3
Completeness	It explicitly answers both what ("Wire Commands, Agents, and Skills together for complex features") and when via an explicit "Use when..." clause naming research, planning, and implementation phases, matching the 3 anchor.	3 / 3
Trigger Term Quality	The "Use when building features that need research, planning, and implementation phases" clause supplies several relevant natural terms, but "Wire Commands, Agents, and Skills together" is internal jargon users would not say, and common variations like "develop a feature" or "implement a feature" are missing.	2 / 3
Distinctiveness Conflict Risk	The multi-phase orchestration niche (research + planning + implementation phases) is a clear, distinct trigger unlikely to fire for general coding skills, satisfying the 3 anchor; "complex features" is broad but the all-three-phases requirement narrows it.	3 / 3
	Total	10 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/pro-workflow
Path: skills/orchestrate/SKILL.md
Commit: 7f7209d

Reviewed: 8 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.