CtrlK
BlogDocsLog inGet started
Tessl Logo

teamharness-team-coordination

Use when a Leader must choose Project Work boundaries, owners, dependency shape, DAG vs Loop, acceptance criteria, or follow-up strategy. Do not use for Quick Task execution after the mode is already selected.

80

Quality

100%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, actionable coordination playbook: it sequences the Leader workflow, provides a clear accept/reject feedback loop, and enumerates concrete anti-patterns without padding. With no bundle files present, its self-contained, well-sectioned organization appropriately serves progressive disclosure.

DimensionReasoningScore

Conciseness

Lean, instruction-style prose that assumes Claude's competence — it gives decision criteria rather than explaining what a DAG or loop is, and each section earns its place without padding.

3 / 3

Actionability

Concrete, specific guidance throughout: explicit pre-delegation clarifications, enumerated result-decision options after `check_task`, and named anti-patterns; absence of code is appropriate for this instruction-only skill per the rubric scoring notes.

3 / 3

Workflow Clarity

Sequenced workflow (design boundaries -> choose DAG/Loop -> delegate -> accept results) with an explicit feedback loop in Result Decisions that lists accept/revise/verify/ask/block branches.

3 / 3

Progressive Disclosure

Self-contained body with no external reference files (none of references/scripts/assets exist), organized into clearly headed sections with no nested reference chains; well-structured for a skill that needs no offloaded detail.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, specific, and complete: it states concrete decisions the skill governs, gives an explicit positive trigger, and disambiguates with a negative trigger. Trigger terms are domain-native and the niche is clearly distinct from sibling skills.

DimensionReasoningScore

Specificity

Names multiple concrete decision areas — 'Project Work boundaries, owners, dependency shape, DAG vs Loop, acceptance criteria, or follow-up strategy' — matching the multiple-specific-actions anchor; not merely a domain label.

3 / 3

Completeness

Explicitly answers both what ('choose ... boundaries, owners, dependency shape ... acceptance criteria') and when ('Use when a Leader must choose ...'), plus a negative trigger ('Do not use for Quick Task execution').

3 / 3

Trigger Term Quality

Covers natural domain terms a TeamHarness Leader requester would say — 'Project Work', 'DAG vs Loop', 'acceptance criteria', 'follow-up strategy', 'Quick Task' — giving good coverage of relevant variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear TeamHarness Leader-coordination niche with an explicit negative trigger, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentscope-ai/AgentTeams
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.