team-planex

Unified team skill for plan-and-execute pipeline. Pure router — coordinator always. Beat model is coordinator-only in monitor.md. Triggers on "team planex".

Quality

48%

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 ./.claude/skills/team-planex/SKILL.md

Quality

Content

72%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 routing skill that clearly defines architecture, role dispatch, and worker spawn mechanics with concrete templates and commands. Its main weakness is the lack of explicit validation checkpoints in the coordinator workflow — the multi-step orchestration (analyze → dispatch → spawn → monitor) would benefit from numbered steps with verification gates. The content is mostly concise but the inline spawn template and session directory structure add bulk that may be better placed in referenced files.

Suggestions

Add a numbered coordinator workflow sequence with explicit validation checkpoints (e.g., 'Verify task-analysis.json is valid before spawning workers', 'Confirm all workers acknowledged via team_msg before entering monitor loop').

Consider moving the Worker Spawn Template and Session Directory structure to referenced files (e.g., specs/spawn-template.md, specs/session-layout.md) to keep the router leaner.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient and avoids explaining basic concepts, but includes some structural overhead (e.g., the ASCII architecture diagram and verbose spawn template) that could be tightened. The role registry table and session directory layout are useful but borderline for what a coordinator-only router needs inline.	2 / 3
Actionability	Provides concrete, copy-paste-ready spawn templates with exact Agent() parameters, specific CLI commands (ccw cli --mode analysis/write), exact message bus calls, and precise file paths. The role router logic is explicit and unambiguous.	3 / 3
Workflow Clarity	The architecture diagram and role router section show the flow clearly, and the error handling table covers failure scenarios. However, there are no explicit validation checkpoints between steps (e.g., verify task-analysis.json before spawning workers, confirm worker readiness), and the coordinator workflow is implicit rather than sequenced with numbered steps and feedback loops.	2 / 3
Progressive Disclosure	Excellent progressive disclosure structure: SKILL.md serves as a pure router/overview, with clear one-level-deep references to role specs (roles/coordinator/role.md, roles/planner/role.md, roles/executor/role.md) and pipeline specs (specs/pipelines.md). Content is appropriately split between the overview and role-specific files.	3 / 3
	Total	10 / 12 Passed

Description

25%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.

This description is heavily laden with internal jargon and lacks concrete, user-facing language about what the skill actually does. While it includes a trigger phrase ('team planex'), the phrase is technical and narrow, and the description fails to explain the skill's purpose or capabilities in accessible terms. It reads more like internal developer notes than a functional skill description.

Suggestions

Replace jargon like 'pure router', 'coordinator-only', and 'beat model' with concrete descriptions of what the skill does, e.g., 'Coordinates multi-step task execution by breaking complex requests into subtasks and delegating them.'

Add natural trigger terms that users might actually say, such as 'plan and execute', 'break down task', 'multi-step workflow', 'coordinate tasks', in addition to the internal 'team planex' trigger.

Add an explicit 'Use when...' clause describing the scenarios in which this skill should be selected, e.g., 'Use when the user needs a complex task broken into steps and executed sequentially by multiple agents.'

Dimension	Reasoning	Score
Specificity	The description uses vague, jargon-heavy language like 'plan-and-execute pipeline', 'pure router', and 'coordinator always' without describing any concrete actions or capabilities that a user would understand.	1 / 3
Completeness	It has a minimal 'when' clause ('Triggers on "team planex"'), but the 'what' is extremely vague — 'plan-and-execute pipeline' and 'pure router' don't clearly explain what the skill actually does. The trigger guidance is present but very narrow.	2 / 3
Trigger Term Quality	The only explicit trigger is 'team planex', which is an internal/technical term unlikely to be naturally used by users. Terms like 'pure router', 'coordinator-only', and 'beat model' are internal jargon, not natural user language.	1 / 3
Distinctiveness Conflict Risk	The specific trigger phrase 'team planex' provides some distinctiveness, but the vague description of being a 'coordinator' and 'router' for a 'plan-and-execute pipeline' could overlap with other orchestration or planning skills without clearer boundaries.	2 / 3
	Total	6 / 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: .claude/skills/team-planex/SKILL.md
Commit: 07491b0

Reviewed: 18 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.