CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-orchestration

AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.

Quality

91%

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

86%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 lean, well-structured instruction-only skill whose loop, rules, and completion criteria are specific and largely actionable. The main gaps are the unspecified command syntax and selection conditions for the Act verbs and the absence of an explicit branch for failed verification.

Suggestions

Add a one-line decision rule or command example for each Act verb (e.g., what 'approve', 'relay', and 'delegate' concretely map to), or at least complete the 'detail --tail 10' command with the agent identifier so it is copy-paste ready.

Specify the failed-verification branch in the Loop, e.g. 'If verify fails: correct or re-delegate, then re-verify; escalate after two failed verifications of the same agent', turning the implicit feedback loop into an explicit one.

Clarify when to choose each action in step 3 (e.g., approve for waiting-on-permission agents, relay when a downstream agent needs upstream output) so the sequence's checkpoint maps unambiguously to an action.

DimensionReasoningScore

Conciseness

The body is fully bullet-driven with zero concept explanations or padding, and assumes competence ('Own the loop until assigned work is complete, blocked, or stopped'). The only near-redundancy — the agent-management/agent-communication split appearing in both opening paragraphs — is not pure duplication because the second statement adds which skill owns which mechanics.

5 / 5

Actionability

Two concrete commands with flags are given ('agent list --json', 'detail --tail 10') plus specific parameters (sleep 10-60s, one status line), but the core Act verbs ('approve, clarify, correct, delegate, relay, verify, or escalate') have no command syntax or selection conditions, and 'detail --tail 10' omits the agent identifier. This is mostly executable guidance with minor gaps, matching the anchor-4 example rather than anchor 5's fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

The 5-step loop is clearly sequenced with an explicit pre-action checkpoint ('Inspect waiting, idle, unknown, missing, or stale agents before acting') and mandated validation ('Use `verify` before accepting any agent's completion claim'). It falls short of anchor 5 because no branch specifies what to do when verification fails — only a general escalation rule ('Escalate only for repeated failures') covers error recovery.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into clean, well-labeled sections (## Rules, ## Loop, ## Completion). Per the rubric's simple-skill note, this earns anchor 5 with well-organized sections alone.

5 / 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 description that is specific, complete, and explicitly disambiguated from sibling skills via both a positive trigger clause and a negative boundary. The only weakness is slightly thin natural-language trigger coverage.

Suggestions

Add one or two common user phrasings as triggers — e.g., 'orchestrate agents', 'coordinate an agent team', or 'monitor agent progress' — to broaden natural keyword coverage toward the anchor-5 standard.

DimensionReasoningScore

Specificity

Six concrete, distinct actions are named ('poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion'), giving comprehensive coverage of the supervision domain. This matches anchor 5; it is not anchor 4 because there are no meaningful gaps in the action inventory.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' is the concrete action list, and the 'when' is a concrete trigger clause ('Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions') that also states a negative boundary. This matches anchor 5 exactly and exceeds anchor 4, whose 'when' is merely less specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage exists ('multi-agent workflows', 'multi-agent coordination', 'supervise', 'waiting agents'), but a few natural user phrasings are missing — e.g., 'orchestrate agents', 'agent team', 'monitor agent status'. This fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (ongoing multi-agent supervision over repeated passes) and explicitly fences off the one-off list/detail/send/start/kill actions that would otherwise collide with sibling agent-management/agent-communication skills. Anchor 5 (clear niche with distinct triggers, minimal conflict risk) fits; anchor 4 would imply only an implicit or partial boundary.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

codeaholicguy/ai-devkit

Path

skills/agent-orchestration/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.