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".
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.codex/skills/team-planex/SKILL.mdQuality
Discovery
7%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 reads like internal developer notes rather than a functional skill description. It fails to communicate what the skill actually does for users, relies on jargon ('pure router', 'beat model', 'coordinator-only'), and provides no natural trigger terms beyond the specific phrase 'team planex'. It would be nearly impossible for Claude to correctly select this skill based on user intent.
Suggestions
Replace jargon with a clear explanation of what the plan-and-execute pipeline actually accomplishes for the user (e.g., 'Coordinates multi-step task execution by breaking complex requests into subtasks and delegating them to specialized agents').
Add a 'Use when...' clause with natural trigger terms that describe user scenarios, such as 'Use when the user needs to orchestrate complex multi-step workflows, delegate tasks across agents, or coordinate parallel work streams'.
Remove internal implementation details like 'pure router', 'beat model', and 'coordinator-only in monitor.md' that serve no purpose for skill selection and replace them with user-facing capability descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, jargon-heavy language like 'plan-and-execute pipeline', 'pure router', 'coordinator always', and 'beat model is coordinator-only in monitor.md' without describing any concrete user-facing actions or capabilities. | 1 / 3 |
Completeness | The 'what' is extremely vague — it says it's a 'router' for a 'plan-and-execute pipeline' but never explains what that pipeline actually does for the user. The 'when' is limited to the trigger phrase 'team planex' with no broader context for when this skill should be selected. | 1 / 3 |
Trigger Term Quality | The only explicit trigger is 'team planex', which is internal jargon unlikely to be naturally used by end users. Terms like 'pure router', 'coordinator', and 'beat model' are technical internals, not natural user language. | 1 / 3 |
Distinctiveness Conflict Risk | The very specific trigger phrase 'team planex' does reduce conflict risk since it's unlikely to match other skills accidentally. However, the rest of the description is so vague that without that exact trigger phrase, it would be impossible to distinguish this skill's purpose from others. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
85%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-crafted orchestration skill that serves as an effective router document. Its strengths are the concrete spawn templates, clear delegation lock table, and well-organized progressive disclosure to role-specific files. Minor verbosity in some sections (architecture diagram + role registry + role router overlap) prevents a perfect conciseness score, but overall the content is highly actionable and well-structured for its complex coordination purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured and avoids explaining basic concepts, but includes some redundancy (e.g., the architecture diagram partially duplicates the role registry table and role router section). The model selection guide and some agent coordination details could be tightened. Overall mostly efficient but not maximally lean. | 2 / 3 |
Actionability | Provides concrete spawn_agent templates with exact parameter structures, a specific delegation lock table with allowed/blocked tool calls, exact file paths, CLI commands, and message bus API calls. The worker spawn template is copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | The two-phase pipeline pattern is clearly sequenced (spawn planner → wait → spawn executors → wait → close). Validation checkpoints are present via the delegation lock, agent health checks with list_agents for reconciliation, and error handling table with specific recovery actions for each failure scenario. | 3 / 3 |
Progressive Disclosure | SKILL.md acts as a clear router/overview pointing to one-level-deep role specs (roles/coordinator/role.md, roles/planner/role.md, roles/executor/role.md) and specs (specs/pipelines.md). The role registry table provides a navigable index. Session directory structure is documented inline appropriately since it's shared context. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
- Commit
0f8e801
- 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.