agent-performance-optimizer
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer
35
0%
Does it follow best practices?
Impact
97%
19.39xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-performance-optimizer/SKILL.mdQuality
Discovery
0%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 essentially an invocation instruction with no substantive content. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, provides no guidance on when to use it, and is too generic to be distinguishable from other skills. It is among the weakest possible skill descriptions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Profiles application code, identifies bottlenecks, optimizes database queries, reduces memory usage, and improves response times.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions slow performance, latency issues, profiling, speed optimization, or bottleneck analysis.'
Specify the domain or technology scope to reduce conflict risk, e.g., 'Optimizes Python/Node.js backend performance' rather than the generic 'performance-optimizer.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Performance-optimizer' is a vague label with no explanation of what it actually does—no specific capabilities like profiling, caching, reducing load times, etc. are mentioned. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no 'Use when...' clause and no explanation of functionality—only an invocation instruction. | 1 / 3 |
Trigger Term Quality | The only keyword is 'performance-optimizer,' which is a generic compound term. There are no natural user-facing trigger terms like 'slow,' 'latency,' 'speed up,' 'profiling,' 'bottleneck,' or any domain-specific terms users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | 'Performance-optimizer' is extremely generic and could overlap with database optimization, frontend performance, network optimization, code profiling, or any number of other performance-related skills. There is nothing to distinguish its niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose, largely non-actionable document that reads more like a product overview or capability catalog than an operational skill. The code examples are non-functional skeletons with undefined helper methods, the workflow sections are abstract step lists without concrete commands or validation, and the extensive bullet-point sections explaining basic performance concepts waste tokens on information Claude already knows.
Suggestions
Remove all descriptive bullet-point sections (Performance Metrics, Optimization Strategies, Advanced Techniques) that explain concepts Claude already knows, and replace with only project-specific conventions or constraints.
Make code examples executable by defining all referenced helper functions, or replace with minimal but complete working examples that demonstrate actual MCP tool usage patterns.
Add concrete validation checkpoints to workflows (e.g., 'verify optimization result has improvement > 0 before applying') and error recovery steps for each multi-step process.
Extract detailed integration patterns and lengthy code examples into separate referenced files, keeping SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Massive amounts of bullet-point lists that describe concepts Claude already knows (what throughput is, what latency is, what caching is). The 'Performance Metrics and KPIs' and 'Optimization Strategies' sections are pure padding with no actionable content. Much of the content reads like a marketing brochure rather than operational instructions. | 1 / 3 |
Actionability | Despite containing code blocks, the code is pseudocode/skeleton code with placeholder methods like `optimize_cpu_usage` that just print strings. Functions like `buildAllocationMatrix`, `extractLoadDistribution`, `calculateBalanceScore` are called but never defined. None of the code is executable or copy-paste ready—it's illustrative scaffolding that wouldn't actually optimize anything. | 1 / 3 |
Workflow Clarity | The 'Example Workflows' section lists high-level steps like 'Assess current infrastructure performance' and 'Identify performance bottlenecks' without any concrete commands, validation checkpoints, or error recovery steps. There are no feedback loops for any of the multi-step processes. The workflows are abstract descriptions rather than actionable sequences. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline regardless of depth or relevance. The document mixes overview-level bullet lists with lengthy code examples and detailed integration patterns all in one file with no navigation structure or cross-references. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
0d9f9b1
- 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.