team-coordinate

Universal team coordination skill with dynamic role generation. Uses team-worker agent architecture with role-spec files. Only coordinator is built-in -- all worker roles are generated at runtime as role-specs and spawned via team-worker agent. Beat/cadence model for orchestration. Triggers on "Team Coordinate ".

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/team-coordinate/SKILL.md

Quality

Content

77%Scale 1-3

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

This is a well-structured orchestration skill with strong actionability and workflow clarity — the delegation lock, spawn templates, and error handling are concrete and executable. The main weakness is that it tries to be both an overview and a reference document, inlining schemas and directory structures that would be better placed in the referenced spec files. Conciseness suffers from some redundancy between the architecture diagram, lifecycle description, and dispatch section.

Suggestions

Move the full team-session.json schema and session directory tree to a referenced spec file (e.g., specs/session-schema.md) and keep only a brief summary inline.

Consolidate the architecture diagram, orchestration mode lifecycle, and dispatch section — they describe overlapping concepts and could be unified into a single concise flow description.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~300 lines) with extensive tables and schemas. Some content is well-structured and necessary (delegation lock, spawn templates), but there's redundancy (architecture diagram + lifecycle + dispatch all describe similar flow) and some sections like the session directory tree and full JSON schema could be in referenced spec files rather than inline.	2 / 3
Actionability	Highly actionable with concrete spawn_agent templates, specific tool call patterns, exact file paths, JSON schemas, and explicit decision tables (delegation lock, model selection, message semantics). The spawn template is copy-paste ready and the error handling table provides specific resolutions.	3 / 3
Workflow Clarity	Clear Phase 0-5 lifecycle with explicit sequencing, validation checkpoints (agent health checks via list_agents, session state reconciliation), timeout handling with escalation steps (STATUS_CHECK -> FINALIZE -> mark timed_out -> close), and a well-defined resume flow with state reconciliation. The delegation lock acts as a validation gate before every action.	3 / 3
Progressive Disclosure	References to external specs (pipelines.md, role-spec-template.md, quality-gates.md, knowledge-transfer.md) and roles/coordinator/role.md are well-signaled, but no bundle files were provided to verify they exist. More critically, the inline content includes the full session directory tree, full JSON schema, and extensive tables that could be offloaded to referenced spec files, making the main SKILL.md heavier than necessary.	2 / 3
	Total	10 / 12 Passed

Description

57%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 establishes a distinctive architectural identity and provides an explicit trigger phrase, which helps with disambiguation. However, it leans heavily on internal implementation details (role-specs, beat/cadence model) rather than describing concrete user-facing capabilities, and the trigger mechanism is a synthetic command rather than natural language terms users would actually use.

Suggestions

Add natural trigger terms users would actually say, such as 'delegate tasks', 'coordinate team members', 'assign roles', 'multi-agent workflow', or 'parallel task execution'.

Expand the 'when' clause beyond just the command trigger — describe scenarios like 'Use when the user needs to break a complex task into subtasks handled by specialized roles' or 'when multiple distinct expertise areas are needed simultaneously'.

Replace abstract architectural language ('beat/cadence model', 'role-spec files') with concrete action descriptions like 'spawns specialized worker agents, distributes subtasks, and aggregates results'.

Dimension	Reasoning	Score
Specificity	The description names the domain (team coordination) and mentions some architectural details (team-worker agent architecture, role-spec files, beat/cadence model), but the actual concrete actions the skill performs are vague — 'coordination' and 'dynamic role generation' are abstract rather than specific user-facing capabilities.	2 / 3
Completeness	The 'what' is partially addressed (team coordination with dynamic role generation and agent architecture), and there is a trigger clause ('Triggers on "Team Coordinate"'), but the 'when' guidance is minimal — it only specifies a command prefix rather than describing scenarios or user intents that should activate this skill.	2 / 3
Trigger Term Quality	It includes the explicit trigger phrase 'Team Coordinate' but this is a synthetic command rather than a natural keyword a user would say. It lacks natural language variations like 'delegate tasks', 'assign roles', 'manage team', 'orchestrate workflow', etc.	2 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche with its specific architecture (team-worker agent, role-spec files, beat/cadence model) and explicit trigger phrase 'Team Coordinate', making it unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: catlog22/Claude-Code-Workflow
Path: .codex/skills/team-coordinate/SKILL.md
Commit: 07491b0

Reviewed: 5 days 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.