plano-agent-orchestration

Improve multi-agent orchestration in Plano. Use for agent registration, agent listener wiring, and capability-focused agent descriptions for accurate routing.

Quality

85%

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

85%

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

The body is tight and well-structured with a clear, validated checklist for a simple instruction-only skill. Its lone weakness is actionability: it tells Claude what to do but never shows a concrete example of a capability-focused, non-overlapping agent description.

Suggestions

Add one before/after example of an agent description rewritten to be capability-focused and non-overlapping so Claude can copy the pattern.

Show a concrete snippet of the `agents`/`listeners[].agents` config relationship (a small YAML/JSON example) to make the registration check unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padded explanations of concepts Claude already knows; every section earns its place, matching the efficient-anchor example rather than the level-2 case that includes unnecessary explanation.	3 / 3
Actionability	It gives concrete, config-aware guidance (verify agents in both `agents` and `listeners[].agents`, rewrite descriptions to be capability-focused) but provides no executable code or before/after example of a capability-focused description, leaving guidance incomplete; it is above level 1 because the direction is specific, not abstract.	2 / 3
Workflow Clarity	The numbered Execution Checklist sequences the work and step 5 ("Provide test prompts to validate routing outcomes") supplies an explicit validation checkpoint, matching the clear-sequence-with-validation anchor; it is not level 2, which lacks checkpoints.	3 / 3
Progressive Disclosure	The skill is under 50 lines with no external references and well-organized sections (When To Use, Apply These Rules, Execution Checklist), so per the simple-skills note it scores 3 without needing separate files.	3 / 3
	Total	11 / 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.

The description is concise, third-person, and covers both what the skill does and when to use it with an explicit trigger clause. Its main weakness is trigger-term naturalness — the phrasing leans technical rather than mirroring how users ask.

Suggestions

Add more natural trigger phrasings users would actually say, e.g. "Use when the user asks to fix routing, agents aren't being selected correctly, or descriptions overlap."

Include a couple of plain-language synonyms alongside the technical terms (e.g. "agent setup", "routing not working") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "agent registration", "agent listener wiring", and "capability-focused agent descriptions for accurate routing" — matching the anchor for several specific concrete actions; it is not the level below (which only names a domain and some actions).	3 / 3
Completeness	It states what ("Improve multi-agent orchestration in Plano") and gives an explicit "Use for..." when-clause, answering both what and when; not level 2, where when is only implied.	3 / 3
Trigger Term Quality	Terms like "agent registration" and "agent listener wiring" are relevant but technical/internal rather than natural phrasings a user would say, and common variations are missing; it does not reach the broad natural-term coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	It targets a distinct niche (Plano multi-agent orchestration) with specific triggers unlikely to fire for unrelated skills; it is more clearly scoped than the level-2 overlap case.	3 / 3
	Total	11 / 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: katanemo/plano
Path: skills/plano-agent-orchestration/SKILL.md
Commit: d23e276

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.