orchestrating-multi-agent-systems

Execute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers. Use when building complex AI systems requiring agent collaboration, task delegation, or workflow coordination. Trigger with phrases like "create multi-agent system", "orchestrate agents", or "coordinate agent workflows".

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/ai-ml/ai-sdk-agents/skills/orchestrating-multi-agent-systems/SKILL.md

Quality

Content

57%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.

The skill body is well-structured with good progressive disclosure and concrete API references, but it lacks inline executable code examples and explicit validation feedback loops in its workflow, leaving actionability and workflow clarity at the mid level.

Suggestions

Add a short executable code block for a minimal agent with ai.tool()/ai.handoff() so guidance is copy-paste ready rather than API-name-only.

Insert an explicit validation checkpoint (e.g., 'verify handoff chain has no cycles before wiring the workflow') with a fix-and-retry loop in the Instructions steps.

Trim the Prerequisites section to drop explanations of familiar concepts like Zod's validation role, keeping only the install commands and version requirements.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concise numbered steps, a table, and scenario examples, but the Prerequisites section restates concepts Claude already knows (e.g., explaining Zod's role) and could be tightened, fitting 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	Specific API names and commands appear (ai.tool(), ai.handoff(), npm install ai..., AbortController), but the body provides no executable code blocks or copy-paste examples — guidance is concrete yet incomplete, matching 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	A clear 10-step sequence is present, but it lacks explicit validation checkpoints or feedback loops within the workflow; step 10 only loosely mentions testing then validating, which caps workflow clarity at 2 per the destructive/batch-operations guidance.	2 / 3
Progressive Disclosure	The body is a concise overview with three clearly-signaled, one-level-deep references (implementation.md, errors.md, examples.md) that are all real bundle files, with content appropriately split and easy to navigate.	3 / 3
	Total	9 / 12 Passed

Description

90%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.

The description clearly states capabilities and when to use the skill with natural trigger phrases and a distinct niche. The only weakness is specificity, where the action list is somewhat broad rather than enumerating many concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('handoffs, routing, and workflows across AI providers') but the action list is broad rather than enumerating multiple distinct concrete capabilities, fitting the 'names domain and some actions' anchor.	2 / 3
Completeness	Explicitly answers both what ('Execute orchestrate multi-agent systems with handoffs, routing, and workflows') and when ('Use when building complex AI systems requiring agent collaboration, task delegation, or workflow coordination') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural phrases users would say — 'create multi-agent system', 'orchestrate agents', 'coordinate agent workflows' — giving good coverage of likely trigger phrasings.	3 / 3
Distinctiveness Conflict Risk	The multi-agent orchestration niche with distinct, specific triggers ('orchestrate agents', 'coordinate agent workflows') is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/ai-ml/ai-sdk-agents/skills/orchestrating-multi-agent-systems/SKILL.md
Commit: c4eafaf

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