team-perf-opt
Unified team skill for performance optimization. Coordinator orchestrates pipeline, workers are team-worker agents. Supports single/fan-out/independent parallel modes. Triggers on "team perf-opt".
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-perf-opt/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 reads more like an internal architecture document than a skill description meant to help Claude select the right tool. It focuses on implementation details (coordinator, workers, fan-out modes) rather than user-facing capabilities, and relies on an artificial trigger phrase instead of natural language keywords. The domain of 'performance optimization' is too broad without specifying what is being optimized.
Suggestions
Replace the artificial trigger 'team perf-opt' with natural user language, e.g., 'Use when the user asks to optimize application performance, reduce latency, improve throughput, or profile slow code.'
Specify concrete actions the skill performs, e.g., 'Profiles code execution, identifies bottlenecks, recommends caching strategies, and optimizes database queries' instead of vague 'performance optimization.'
Clarify the specific domain (web performance, code performance, database optimization, etc.) to reduce overlap with other potential skills and improve distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'performance optimization' and 'orchestrates pipeline' without specifying concrete actions. It mentions architectural patterns (fan-out, parallel modes) but doesn't describe what the skill actually does in terms of user-facing capabilities. | 1 / 3 |
Completeness | It attempts to answer both 'what' (performance optimization with coordinator/worker pattern) and 'when' ('Triggers on team perf-opt'), but the 'what' is vague and the 'when' is an artificial command rather than a meaningful usage trigger. The trigger clause exists but is not useful for natural skill selection. | 2 / 3 |
Trigger Term Quality | The trigger term 'team perf-opt' is artificial jargon that no user would naturally say. Terms like 'coordinator', 'workers', 'fan-out', and 'pipeline' are internal implementation details, not natural user language. There are no keywords a user would organically use. | 1 / 3 |
Distinctiveness Conflict Risk | The specific trigger phrase 'team perf-opt' would prevent accidental conflicts, but 'performance optimization' is extremely broad and could overlap with many other skills. The description doesn't clarify what kind of performance (web, database, code, system) is being optimized. | 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 provides highly actionable, concrete guidance for coordinating a multi-agent performance optimization pipeline. The workflow clarity is strong with explicit validation checkpoints, error recovery paths, and clear pipeline sequencing across three parallel modes. Minor verbosity in some sections (delegation lock rationale, model selection guide) prevents a perfect conciseness score, but overall token efficiency is reasonable given the complexity of the orchestration being described.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly dense and information-rich, but includes some sections that could be tightened—e.g., the Model Selection Guide rationale column restates obvious points, and the Delegation Lock table is somewhat verbose. However, most content is non-trivial orchestration logic that Claude wouldn't inherently know. | 2 / 3 |
Actionability | Provides concrete spawn_agent templates with exact parameters, specific tool call allowlists, named agent targeting examples, timeout handling sequences, and executable completion action code. The guidance is copy-paste ready for orchestration tasks. | 3 / 3 |
Workflow Clarity | The pipeline modes (single, fan-out, independent) are clearly diagrammed with explicit sequencing. Validation checkpoints are present: benchmark regression triggers auto-FIX tasks, review-fix cycles have iteration limits with user escalation, agent health checks reconcile state, and timeout handling has a clear 3-step escalation (STATUS_CHECK → FINALIZE → close). | 3 / 3 |
Progressive Disclosure | SKILL.md serves as a clear router/overview with well-signaled one-level-deep references to role files (roles/coordinator/role.md, etc.) and spec files (specs/pipelines.md, specs/team-config.json). The Role Registry table provides a clean navigation index. Content is appropriately split between the overview and referenced files. | 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.