team-issue
Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".
50
55%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.codex/skills/team-issue/SKILL.mdQuality
Discovery
25%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 focuses heavily on internal architecture (team-worker agents, coordinator, role directories) rather than describing what the skill actually does for the user. The trigger term 'team issue' is artificial and unlikely to match natural user requests. The description fails to communicate concrete capabilities or provide meaningful keywords for skill selection.
Suggestions
Replace architectural jargon with concrete actions the skill performs, e.g., 'Diagnoses and resolves team-reported issues by analyzing logs, identifying root causes, and implementing fixes'.
Add natural trigger terms users would actually say, e.g., 'Use when the user mentions bug reports, incident resolution, troubleshooting, or team escalations'.
Clarify what domain or type of issues this skill handles to distinguish it from generic debugging or support skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'issue resolution', 'domain logic', 'orchestrates pipeline' without describing any concrete actions the skill performs. It describes architecture rather than capabilities. | 1 / 3 |
Completeness | It attempts to answer both 'what' (issue resolution using team-worker architecture) and 'when' (triggers on 'team issue'), but the 'what' is vague and the 'when' trigger is extremely narrow and unnatural. The trigger clause exists but is weak. | 2 / 3 |
Trigger Term Quality | The only explicit trigger is 'team issue', which is not a natural phrase users would say. Terms like 'team-worker agent architecture', 'role directories', and 'coordinator orchestrates pipeline' are internal jargon, not user-facing keywords. | 1 / 3 |
Distinctiveness Conflict Risk | 'Issue resolution' is quite generic and could overlap with many skills (bug fixing, customer support, etc.), but the specific mention of 'team-worker agent architecture' and the narrow trigger 'team issue' somewhat limits overlap, albeit artificially. | 2 / 3 |
Total | 6 / 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-structured orchestration skill that clearly defines the coordinator/worker architecture, provides concrete spawn templates, and establishes explicit guardrails via the delegation lock. The workflow is well-sequenced with proper validation checkpoints and error handling. Minor inefficiencies exist in duplicated spawn templates and some verbosity that could be trimmed, but overall the content is highly actionable and well-organized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient for its complexity, but includes some redundant sections (e.g., the Worker Spawn Template is shown twice with near-identical content for single and parallel spawn, and the timeout cascade instructions are duplicated verbatim). Some tables and sections could be tightened. | 2 / 3 |
Actionability | Provides concrete spawn_agent templates with exact parameter structures, specific tool call allowlists/blocklists, precise file paths, session directory layouts, and executable code patterns for batch orchestration. The delegation lock table is immediately actionable. | 3 / 3 |
Workflow Clarity | The pipeline is clearly sequenced (explore -> plan -> review -> marshal -> implement) with explicit validation checkpoints including review-fix cycles (max 2 rounds), timeout cascades with escalation steps (STATUS_CHECK -> FINALIZE -> mark timed_out -> close), and agent health reconciliation. The delegation lock provides a clear decision framework before every action. | 3 / 3 |
Progressive Disclosure | Clean architecture with SKILL.md as a router/overview, role-specific logic delegated to individual role.md files via a clear role registry table with links, and pipeline specs referenced in a separate specs/pipelines.md. References are one level deep and clearly signaled. | 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
5ff5e86
- 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.