CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team

N coordinated agents on shared task list using Claude Code implicit agent teams

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/team/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 delivers exceptionally concrete, executable orchestration guidance with a well-gated staged workflow — actionability and workflow clarity are near-ideal. Its weaknesses are token efficiency (heavy repetition of the TeamCreate/TeamDelete removal note and dense version-sensitive prose) and the absence of any progressive-disclosure structure, with ~990 lines of reference-grade detail inlined into SKILL.md. Moving routing tables, CLI-worker details, and legacy comparisons into reference files would address both weaknesses at once.

Suggestions

State the 'Claude Code 2.1.178+ removed TeamCreate/TeamDelete' fact once (e.g., in a short 'Native team model' section or a deprecated/old-patterns section) and remove the ~8 repetitions across Phases, Gotchas, and State Cleanup.

Split reference-grade material into bundle files — e.g. references/role-routing.md (Per-Role Provider & Model Routing), references/cli-workers.md (CLI worker operations and startup-evidence timeouts), references/worktrees.md (worktree API) — leaving SKILL.md as a pipeline overview with one-level-deep, clearly signaled links.

Consolidate version-sensitive details (2.1.217/218/219 subagent-depth defaults, OMC_RUNTIME_V2 flags, startup-evidence budgets) into a single compatibility/version notes section so they stop bloating the main flow.

DimensionReasoningScore

Conciseness

The ~990-line body is noticeably verbose: the fact that 'Claude Code 2.1.178+ removed TeamCreate/has no TeamDelete' is repeated at least eight times (intro, native team model, Phase 3, Phase 5, Phase 7, shutdown protocol, Gotchas, State Cleanup), and dense prose blocks like the 'Cursor/Codex startup evidence timeout' section and scattered version pins (2.1.217/218/219) pad the token budget. Not anchor 1 because it rarely explains concepts Claude already knows — the material is OMC-specific protocol — but well above the lean anchor 5.

2 / 5

Actionability

Fully executable throughout: copy-paste JSON payloads for spawning, messaging, and shutdown; complete state_write calls with arguments; a full worker preamble; exact commands (cleanup-orphans.mjs --team-name, omc doctor --team-routing); env vars with precedence rules; and worked config examples covering the common cases. The only minor gap is the worktree API table referencing non-bundled git-worktree.ts, which keeps it at anchor 5 rather than revealing missing steps.

5 / 5

Workflow Clarity

The staged pipeline (team-plan -> team-prd -> team-exec -> team-verify -> team-fix) has explicit per-stage entry/exit criteria, a bounded verify/fix feedback loop with max_fix_loops stop conditions, watchdog thresholds (5/10-minute stuck-task rules), a blocking shutdown protocol with timeouts, resume semantics, and dedicated error-handling playbooks. This matches the anchor-5 pattern of explicit validation steps, feedback loops, and only-proceed-when-valid gates.

5 / 5

Progressive Disclosure

Section structure is good (clear headers, tables, examples), so it rises above anchor 2's 'minimal structure', but the skill is a ~990-line monolith with no bundle reference files at all: reference-grade material (Per-Role Provider & Model Routing, worktree API reference, CLI worker operations, legacy swarm comparison) is inlined, and cited paths like skills/cancel/SKILL.md, docs/REFERENCE.md, and scripts/cleanup-orphans.mjs do not resolve within the bundle. Fits anchor 3 ('content that should be separate is inline') rather than anchor 4, whose bulk detail is appropriately split out.

3 / 5

Total

15

/

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 is concise and concrete about what the skill does, but it omits any 'use when' trigger guidance and lacks natural trigger-term variations users would actually say. It defines a reasonably distinct niche (Claude Code implicit agent teams) but under-sells the skill's concrete capabilities. Adding an explicit trigger clause and common synonyms would substantially raise the score.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to parallelize a task across multiple agents, spawn a team of workers, or coordinate agents on a shared task list.'

Include natural trigger synonyms users would say — 'parallelize', 'multi-agent', 'team of agents', 'spawn workers' — to improve trigger-term coverage.

Name 1-2 more concrete capabilities (task decomposition, staged plan/execute/verify pipeline) to move specificity from 'domain plus one action' toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('coordinated agents', 'shared task list', 'implicit agent teams') with 1-2 concrete actions, but stops short of listing the skill's actual capabilities (task decomposition, staged pipeline, verification loop). Matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'), not anchor 4 which requires several specific actions.

3 / 5

Completeness

The 'what' is clear ('N coordinated agents on shared task list'), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not anchor 2 since the 'what' is concrete rather than vague; not anchor 4 since 'when' is entirely absent rather than just implicit.

3 / 5

Trigger Term Quality

Includes relevant keywords ('agents', 'team', 'task list', 'coordinated') but misses natural variations users would say such as 'parallel', 'multi-agent', 'spawn', 'delegate', or 'swarm'. Fits anchor 3 ('some relevant keywords but missing common variations or synonyms'), not anchor 4's 'good keyword coverage; a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

'using Claude Code implicit agent teams' carves a fairly specific niche with minimal conflict risk against unrelated skills, though it could overlap with sibling orchestration skills (the skill itself documents a legacy swarm). Matches anchor 4 ('mostly distinct; minor overlap risk'), not anchor 5 which expects explicit distinct trigger phrases.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (994 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/team/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.