CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orchestrator

Delegate to external coding CLIs: A0 headless, Codex, Claude Code and others.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/_orchestrator/skills/orchestrator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-structured orchestration playbook: explicit decision logic (host vs. container with memory-backed preference), two numbered flows with smoke-test validation gates and auth feedback loops, and a clean one-level reference split whose files all exist. Only minor trims (a duplicated agent list, one comment-only code block) keep conciseness and actionability from full marks.

DimensionReasoningScore

Conciseness

The body is dense operational rules with no explanation of concepts Claude already knows, and the long verbatim A0 CLI message is intentionally exact text to relay. It is not 5 because the seven-agent list is repeated verbatim in two consecutive rules and "the pal scenario" phrasing adds unexplained jargon that could be trimmed.

4 / 5

Actionability

Concrete guidance throughout: exact tool choices ("Use `code_execution_remote`, not `code_execution_tool`"), a copy-paste install message with commands, and a `memory` action=save example. It is not 5 because the Container Pal Flow's step-1 bash block holds only a non-executable comment, and per-agent executable commands are deferred to reference files rather than shown.

4 / 5

Workflow Clarity

Both flows are explicitly sequenced with validation checkpoints and feedback loops: install check → probe `--version` → smoke prompt → relay auth and wait → "rerun the smoke prompt. Only then run the real task" → "verify important changes yourself", plus error recovery (reset a stuck TUI session, relay menu choices). This matches the anchor-5 pattern of explicit validation steps with error-recovery loops.

5 / 5

Progressive Disclosure

A ~85-line overview split into Rules, Host CLI Flow, Container Pal Flow, and a reference index; all 8 referenced files exist in references/, are one level deep, and are each mapped to a named agent, with agent-specific commands correctly offloaded ("Put agent-specific commands, auth quirks, install hints, and smoke prompts in the matching reference file"). This is a clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

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

The description states a clear, distinctive capability but is thin: one action verb, no use-when guidance, and it names only 3 of 8 supported agents, hiding the rest behind "and others". It sits at the midpoint of the rubric — readable and distinct, yet neither comprehensive nor trigger-complete.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to delegate a coding task to a terminal agent or names one (Codex, Claude Code, Cursor CLI, Gemini CLI, Grok Build, OpenCode, A0 headless)'.

List the remaining supported agent names (Cursor CLI, Gemini CLI, Grok Build, Hermes, OpenCode) instead of the vague "and others", so users naming those agents naturally match this skill.

Enumerate the concrete actions beyond "delegate" — e.g. installs the CLI, handles login interactively, runs a smoke prompt, then dispatches the task — to lift specificity.

DimensionReasoningScore

Specificity

"Delegate to external coding CLIs" names the domain and concrete tools ("A0 headless, Codex, Claude Code") but offers only a single action verb, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not 4 because several specific actions (install, authenticate, smoke-test, dispatch) are not listed.

3 / 5

Completeness

The 'what' is clear (delegate tasks to external coding CLIs), but there is no 'Use when...' clause or equivalent trigger guidance in the description, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Codex", "Claude Code", and "A0 headless" are natural terms users would say, but "and others" hides Cursor CLI, Gemini CLI, Grok Build, Hermes, and OpenCode — five supported adapters whose names a user would naturally mention. This is 'some relevant keywords but missing common variations', not the good-coverage of 4.

3 / 5

Distinctiveness Conflict Risk

"Delegate to external coding CLIs" carves a distinct orchestration niche reinforced by named CLIs, with only mild breadth added by "and others" — 'mostly distinct; minor overlap risk'. Not 5 because it lacks the explicit, distinct trigger phrases of the anchor-5 exemplar.

4 / 5

Total

13

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

agent0ai/agent-zero

Path

plugins/_orchestrator/skills/orchestrator/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.