CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A highly actionable, clearly sequenced skill with strong validation checkpoints and concrete examples. Its weaknesses are repetition of the form-mixing warning (conciseness) and a monolithic single-file layout where a catalogue/examples split would aid progressive disclosure.

Suggestions

Consolidate the repeated "never emit both forms / never mix prefixes" guidance into a single authoritative statement and reference it from the phases and self-check instead of restating it.

Move the agent catalogue and/or worked examples into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce inline length.

Trim redundant self-check items that restate earlier rules (e.g. the form-mixing and invented-flags checks overlap with Phase 4 rendering rules).

DimensionReasoningScore

Conciseness

Most content is necessary domain reference (catalogue, detection algorithm, tag/composition tables), but the "never emit both forms / never mix prefixes" rule is restated ~4–5 times across phases, the self-check, and examples, and the 13-item self-check has some redundancy — efficient but could be tightened, so score 2 rather than 3.

2 / 3

Actionability

It provides the exact command shape, an ordered install-detection algorithm, trigger-word→chain tables, numbered composition rules, and full copy-paste bash examples — fully executable and instruction-ready, matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear Phase 0–5 sequence is paired with an explicit Phase 5 self-check checklist (validation checkpoint) and stop/report feedback ("if missing or empty, report and stop"), satisfying the score-3 anchor; it is not 2 because checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

No bundle files exist and all content is inline in one ~260-line file; it is well-sectioned but the agent catalogue and worked examples are content that could live in separate reference files, so it sits at the score-2 anchor (content that should be separate is inline) rather than 3.

2 / 3

Total

10

/

12

Passed

Description

85%

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 clearly states concrete capabilities and an explicit use-when trigger, with a distinctive niche. Trigger-term phrasing leans on product-specific jargon that could use more natural user-level variations.

Suggestions

Add more natural user-level trigger phrasings (e.g. "orchestrate this plan", "give me orchestrate prompts for each step") so the description surfaces for the words users actually say.

Soften or broaden the "ECC catalogue" / "compose chains" jargon so non-expert users recognize the trigger without prior product knowledge.

DimensionReasoningScore

Specificity

"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" lists multiple specific concrete actions, matching the score-3 anchor.

3 / 3

Completeness

It explicitly answers what (decompose → design chains → emit prompts) and when ("Use when the user has a multi-step plan…"), satisfying the score-3 anchor for both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

The trigger "Use when the user has a multi-step plan and wants to drive it through orchestrate" gives a relevant scenario, but the natural keywords are product-specific jargon ("orchestrate", "ECC catalogue", "compose chains") and lack common user-level variations, so it sits at the score-2 anchor rather than 3.

2 / 3

Distinctiveness Conflict Risk

The plan→/orchestrate-chain niche is narrow and trigger-specific, making it unlikely to fire for the wrong skill; it is not a level below because the triggers are not generic.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.