plan-orchestrate

Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.

Quality

90%

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

Quality

Content

88%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced instruction skill with concrete templates, a full agent catalogue, and a validation checklist. The main weaknesses are deliberate-but-repeated cross-form constraints and a monolithic structure that could benefit from splitting reference material into bundle files.

Suggestions

Consolidate the 'never emit both forms / no # plugin form comments' rule into one authoritative location and reference it from Phase 0, Phase 4, and the self-check instead of restating it each time.

Move the available-agent catalogue and the tag-to-chain table into a references/ file (e.g. CATALOGUE.md) and link to it, keeping SKILL.md as a leaner overview that still inlines the composition rules.

Consider extracting the two worked examples into an examples/ reference so the main body stays focused on the phase algorithm and output contract.

Dimension	Reasoning	Score
Conciseness	Dense and operational with no padding of concepts Claude already knows, but the 'never emit both forms / no # plugin form comments' constraint is restated across the shape, install, Phase 0, Phase 4, and self-check sections and could be tightened.	4 / 5
Actionability	Fully executable guidance — exact command shape, a full agent catalogue, a tag-to-chain table, numbered composition rules, task-description format with char limits, an output template, and two copy-paste-ready worked examples.	5 / 5
Workflow Clarity	Phase 0–5 are clearly sequenced and Phase 5 is an explicit self-check checklist that validates the output before emitting, satisfying the validation/checklist anchor for a complex generative process.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but the skill is a single monolithic file over 200 lines; the catalogue, tag table, or examples could be split into referenced files for a cleaner overview.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 strong, third-person description that states concrete capabilities and an explicit 'Use when' trigger. Minor room to broaden trigger synonyms, but it clearly communicates both purpose and activation conditions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts' — covering the skill comprehensively.	5 / 5
Completeness	Explicitly answers both what (read/decompose/design chain/emit prompts) and when ('Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand').	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('multi-step plan', 'drive it through orchestrate', 'composing chains by hand') but the trigger vocabulary is somewhat specialized around the /orchestrate command rather than broad synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (bridging plan documents to /orchestrate custom via the ECC catalogue) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/plan-orchestrate/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.