CtrlK
BlogDocsLog inGet started
Tessl Logo

team-coordination

Use before deciding how you should organize team work: DAG vs Loop, dependency shape, task waves, quality gates, acceptance criteria, interruption, replanning, or what to do after Worker results arrive. Always use this skill for team organization strategy before you call project-management or task-management.

68

Quality

81%

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

75%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 well-structured, directive strategy skill that assumes competence and supplies concrete operations and checkpoints. It scores consistently strong across dimensions; a worked example and trimming the small redundancy would lift actionability and conciseness.

Suggestions

Add one short worked scenario (e.g. a 3-node DAG with an evaluation decision) to make the abstract strategy fully concrete.

Tighten the Patch Rules section so it does not restate guidance already given in Design The Work and Result Decisions.

Consider extracting the multi-step interruption procedure into a reference file to keep SKILL.md a tighter overview.

DimensionReasoningScore

Conciseness

The body is lean, directive, and assumes Claude's competence without explaining what a DAG/Project/Worker is; minor redundancy between the Patch Rules anti-patterns and earlier guidance keeps it just short of fully lean.

4 / 5

Actionability

As an instruction-only skill it provides concrete guidance: exact strategic flows, named operations (plan_dag, ready_nodes, plan_loop, record_loop_iteration), and explicit decision lists, with only a worked example missing for a 5.

4 / 5

Workflow Clarity

Sequenced DAG and Loop flows with evaluation checkpoints after each result/iteration, plus a confirmation gate before hard interruption; minor validation gaps remain but no destructive/batch cap applies to this strategy skill.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with no bundle files needed; the ~175 lines of dense strategy is self-contained and navigable, though parts (detailed interruption procedure, per-mode definition lists) could plausibly live in references.

4 / 5

Total

16

/

20

Passed

Description

88%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 clearly states its niche, lists concrete decision areas, gives explicit "use before/when" trigger guidance, and distinguishes itself from sibling skills. Slightly more user-natural trigger phrasing would push it to full marks.

Suggestions

Add one or two plain-language trigger phrases users might naturally say (e.g. "split work across workers" or "parallel vs sequential tasks") alongside the internal terms.

Consider naming the most common triggering scenario up front so the trigger reads as a user need before the enumeration of decision axes.

DimensionReasoningScore

Specificity

Comprehensively enumerates concrete strategic decisions the skill covers ("DAG vs Loop, dependency shape, task waves, quality gates, acceptance criteria, interruption, replanning") rather than vague activity labels.

5 / 5

Completeness

Explicitly answers both what (team organization strategy across the listed decision axes) and when ("Use before deciding...", "Always use this skill... before you call project-management or task-management").

5 / 5

Trigger Term Quality

Natural phrases like "organize team work", "DAG vs Loop", and "replanning" appear, but some terms ("task waves", "Worker results") lean toward internal jargon and a few common user synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear strategy-layer niche and explicitly defers operations to project-management/task-management, leaving only minor overlap risk with those closely related skills.

4 / 5

Total

18

/

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.

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.