CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured overview body: lean numbered instructions, a useful error table, and properly signaled one-level-deep references. The main gaps are the absence of any in-body executable code and the failure to reference the scripts/ and assets/ bundle files.

Suggestions

Add a Resources/Bundle section listing scripts/agent_setup.py, scripts/env_setup.py, scripts/dependency_installer.py, and the assets/ templates (agent_template.ts, example_coordinator.ts, example_workflow.json) so the entire bundle is discoverable.

Include one minimal copy-paste agent + handoff snippet in the body (e.g. a single agent definition with ai.tool() and ai.handoff()) so common cases are executable without opening references.

Tighten the duplication between Overview and Prerequisites (provider lists, architecture pattern names) to recover tokens, and verify ai.tool()/ai.handoff() match current AI SDK v5 API names.

DimensionReasoningScore

Conciseness

Dense one-line instruction steps with no explanation of concepts Claude already knows; minor trimmable padding such as provider details repeated across Overview and Prerequisites and generic resource links. Efficient overall but not token-perfect, matching anchor 4.

4 / 5

Actionability

Concrete commands (npm install lines, env var names, tsconfig settings) and specific APIs (ai.tool(), ai.handoff(), AbortController) go beyond high-level hints, but no executable code block appears in the body itself — all code is delegated to references/examples.md. Anchor 4 fits better than 5 (not copy-paste ready in-body) and better than 3 (real commands, not pseudocode).

4 / 5

Workflow Clarity

Ten clearly sequenced steps ending with 'Test each agent in isolation, then validate end-to-end handoff chains', plus circuit breakers and a cause/solution error table. An explicit validate→fix→retry feedback loop is not spelled out, so anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Three one-level-deep references (implementation.md, errors.md, examples.md — all verified real files) are clearly signaled with 'See X for...' links, but none of the six files in scripts/ and assets/ are mentioned anywhere in the body, leaving bundle content orphaned. Good structure with minor organization gaps matches anchor 4.

4 / 5

Total

16

/

20

Passed

Description

83%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 description that explicitly covers what, when, and trigger phrases in third person, with only a grammar glitch ('Execute orchestrate multi-agent systems') marring the opening. Trigger coverage is good but could add common synonyms.

Suggestions

Fix the broken opening verb pair 'Execute orchestrate multi-agent systems' to a single clear verb phrase such as 'Orchestrate multi-agent systems' to sharpen the capability statement.

Add common trigger variations users naturally say, e.g. 'AI agents', 'agent handoffs', 'agent team', or 'agent framework', to raise trigger-term coverage to the comprehensive level.

Consider naming the concrete deliverable context (TypeScript / AI SDK v5) in the description to further distinguish it from generic workflow-orchestration skills.

DimensionReasoningScore

Specificity

Names the domain plus several concrete capabilities — 'handoffs, routing, and workflows across AI providers' — matching the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.

4 / 5

Completeness

Clearly answers both what ('Execute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers') and when ('Use when building complex AI systems requiring agent collaboration, task delegation, or workflow coordination') with concrete trigger phrases, matching the anchor exactly.

5 / 5

Trigger Term Quality

Explicit trigger phrases ('create multi-agent system', 'orchestrate agents', 'coordinate agent workflows') plus 'agent collaboration, task delegation, or workflow coordination' give good natural-term coverage, but common variations like 'AI agents', 'agent handoffs', or 'agent team' are missing.

4 / 5

Distinctiveness Conflict Risk

Multi-agent orchestration with handoffs and routing is a clear niche with distinct triggers; minor overlap risk with generic workflow-coordination skills keeps it below anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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/tons-of-skills-marketplace

Path

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

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.