team-agent-orchestration

Run team-based orchestration for agent squads using work items, ownership, agent Kanban, merge gates, and control pane handoffs. Use when coordinating an agent squad with work items, ownership, Kanban, and merge gates.

Quality

88%

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

88%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 tight, well-structured orchestration skill that pairs a concrete card schema and Kanban table with a gated, validated multi-step flow and crisp failure-mode guidance. Actionability and progressive disclosure have minor room to improve via execution-mode selection detail and optional reference files for the schema/examples.

Suggestions

Add brief guidance on how to pick among the execution modes (single-agent vs dynamic workflow vs worktree fan-out) so step 2 is actionable rather than enumerated.

Consider extracting the card schema and a worked card example into a references file to push progressive disclosure toward the top anchor.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: uses a compact Kanban table, a copy-paste card schema, and terse failure-mode bullets, assuming Claude's competence with no boilerplate about what agents or Kanban are.	5 / 5
Actionability	Provides concrete, executable artifacts (card JSON schema, per-state exit criteria, numbered 7-step flow), but some steps like "Pick execution mode" stay high-level without specifying how to choose.	4 / 5
Workflow Clarity	The 7-step flow is clearly sequenced with explicit validation checkpoints (merge gates, per-column exit criteria, eval before Running→Review) and feedback loops (Blocked state with owner and next action), matching the top anchor for batch/multi-agent operations.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections in a single self-contained file with no nested references and easy navigation; sits just below the 5 anchor which expects well-signaled one-level-deep external references, and the file exceeds the simple-skill 50-line threshold.	4 / 5
	Total	18 / 20 Passed

Description

87%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 states a concrete capability and an explicit trigger clause in third-person voice, covering both what and when with domain-specific terminology. Minor room to broaden trigger synonyms (e.g., 'multi-agent', 'parallel agents') for the top specificity/trigger anchors.

Suggestions

Add a few natural trigger synonyms like 'multi-agent coordination' or 'parallel agent fan-out' to broaden trigger-term coverage.

Consider naming 1-2 more concrete actions (e.g., 'track agent state', 'gate merges') to push specificity toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete mechanisms ("work items, ownership, agent Kanban, merge gates, and control pane handoffs"), giving specific actionable concepts rather than generic verbs; only minor gaps versus the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both what ("Run team-based orchestration...") and when ("Use when coordinating an agent squad...") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The "Use when coordinating an agent squad with work items, ownership, Kanban, and merge gates" clause supplies several natural terms a user would say; a few common synonyms/variations are missing versus the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The combination of agent Kanban, merge gates, and control pane handoffs carves a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/team-agent-orchestration/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.