team-executor
Lightweight session execution skill. Resumes existing team-coordinate sessions for pure execution via team-worker agents. No analysis, no role generation -- only loads and executes. Session path required. Triggers on "Team Executor".
80
76%
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-executor/SKILL.mdQuality
Discovery
75%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 functionally complete with clear trigger conditions and a well-defined narrow scope that distinguishes it from other skills. Its main weakness is that the actual execution actions remain abstract ('loads and executes' without specifying what is executed), and the trigger terms are technical jargon rather than natural user language. The explicit negations help define boundaries but the core capability could be more concrete.
Suggestions
Specify what is actually executed — e.g., 'Executes task plans, runs coordinated workflows across team-worker agents' to make the concrete actions clearer.
Add natural language trigger variations beyond the exact phrase 'Team Executor' — e.g., 'resume session', 'run team tasks', 'execute team plan' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (session execution, team-worker agents) and some actions (resumes sessions, loads and executes), but the actual concrete actions are vague — 'executes' what exactly? The negations ('No analysis, no role generation') help clarify scope but don't add concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('resumes existing team-coordinate sessions for pure execution via team-worker agents') and when ('Triggers on "Team Executor"', 'Session path required'). The explicit trigger guidance is present and specific. | 3 / 3 |
Trigger Term Quality | Includes the explicit trigger phrase 'Team Executor' and terms like 'session execution', 'team-worker agents', and 'session path', but these are fairly technical/internal jargon. A user would need to know the exact phrase 'Team Executor' to trigger it, and natural language variations are absent. | 2 / 3 |
Distinctiveness Conflict Risk | Very narrow niche — specifically for resuming team-coordinate sessions for execution only, with a distinct trigger phrase 'Team Executor' and requirement for a session path. Unlikely to conflict with other skills due to its highly specific scope and explicit trigger. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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 execution skill with strong actionability — concrete agent spawn templates, validation steps, and completion handlers are all clearly specified. The workflow is well-sequenced with proper state reconciliation and error handling. The main weaknesses are moderate verbosity (some redundant tables and sections) and inline content density that could benefit from better progressive disclosure to separate files.
Suggestions
Consider moving the full spawn template and completion action handlers to separate reference files, keeping only a concise summary in the main SKILL.md
Remove the integration table with team-coordinate — this is context about another skill that doesn't add execution value here
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy — the ASCII architecture diagram, the role router dispatch table, and the integration table with team-coordinate add bulk without proportional value. The error handling table partially duplicates validation steps already described above. | 2 / 3 |
Actionability | Provides concrete, executable spawn_agent/wait_agent/close_agent templates with specific parameter structures, exact validation steps, user command tables, and completion action handlers with request_user_input examples. The code blocks are copy-paste ready for the agent coordination context. | 3 / 3 |
Workflow Clarity | The lifecycle is clearly sequenced (validate -> Phase 0 reconcile -> Phase 1 spawn -> worker callback -> advance -> Phase 2 report), with explicit state reconciliation on resume, error recovery paths, and validation checkpoints before execution begins. The feedback loop of worker execute -> callback -> advance is well-defined. | 3 / 3 |
Progressive Disclosure | References to external files exist (roles/executor/role.md, specs/session-schema.md, session role-specs) but the main file is quite long with inline content that could be split out (e.g., the full spawn template, completion action handlers). The references that do exist are clearly signaled but the overall document is somewhat monolithic. | 2 / 3 |
Total | 10 / 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.