CtrlK
BlogDocsLog inGet started
Tessl Logo

team-agent-orchestration

Run team-based orchestration for agent squads using work items, ownership, agent Kanban, merge gates, and control pane handoffs.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 well-structured, actionable orchestration guide: concise, with a concrete card schema, explicit merge gates as validation checkpoints, and clear failure-mode guidance. It is an exemplary instruction-only SKILL.md body.

DimensionReasoningScore

Conciseness

The body is lean and scannable, using tables and bullets, and assumes Claude's competence without explaining what Kanban or merge gates are; every section earns its place with only minor overlap between Operating Model and later sections.

3 / 3

Actionability

As an instruction-only skill it supplies a copy-paste JSON card schema, a Kanban table with concrete exit criteria, and a specific 7-step flow — concrete and actionable guidance rather than vague direction.

3 / 3

Workflow Clarity

The Team-Based Orchestration Flow is a clear numbered sequence with explicit validation checkpoints (review-then-merge gates, eval before Running→Review) and a Failure Modes section for error recovery; validation is present so the destructive/merge cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist, and the single self-contained document is well-organized into clear headed sections with a one-level structure and no nested references, satisfying the well-organized-sections bar for a reference-light skill.

3 / 3

Total

12

/

12

Passed

Description

67%

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 is specific and distinctive, clearly conveying the skill's niche, but lacks an explicit 'Use when...' trigger clause so its activation cues rely on jargon rather than natural user phrasing. Adding a natural-language trigger line would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming natural user phrases (e.g., 'Use when managing multiple agents as a team, or when the user mentions agent squads, multi-agent work, or orchestration').

Soften jargon in the description with at least one common variation a non-expert user would actually say, to improve trigger-term coverage.

Keep the concrete mechanism list but ensure the trigger guidance mirrors the strong 'When To Activate' terms already in the body.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete mechanisms — 'work items, ownership, agent Kanban, merge gates, and control pane handoffs' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what' (run team-based orchestration) but provides no 'Use when...' clause or equivalent trigger guidance, so 'when' is missing — capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

It includes relevant keywords a user might say ('team-based orchestration', 'agent Kanban', 'squad'), but leans jargon-heavy and offers no explicit natural-language trigger clause, missing common variations.

2 / 3

Distinctiveness Conflict Risk

The vocabulary ('agent Kanban', 'merge gates', 'control pane handoffs') carves a clear niche unlikely to be confused with unrelated skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.