agent-performance-optimizer
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-performance-optimizer44
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 19.39xAgent success when using this skill
Validation for skill structure
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 critically deficient across all dimensions. It functions more as a label than a description, providing only the skill name and invocation syntax without any explanation of capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add specific concrete actions describing what the skill optimizes (e.g., 'Analyzes code for performance bottlenecks, identifies slow database queries, optimizes memory usage')
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions slow code, performance issues, optimization, speed improvements, or profiling')
Specify the domain/scope to distinguish from other potential optimization skills (e.g., is this for Python code? Web apps? Database queries? System resources?)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for performance-optimizer' is completely abstract and doesn't describe what the skill actually does - no verbs, no capabilities, no domain specifics. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides invocation syntax ($agent-performance-optimizer) with no functional description or trigger guidance. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'performance-optimizer' which is technical jargon rather than natural language users would say. Missing natural terms like 'speed up', 'slow', 'optimize', 'performance issues', 'bottleneck', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Performance-optimizer' is extremely vague - it could apply to code optimization, database queries, web performance, memory usage, or countless other domains. No clear niche is established. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is excessively verbose, explaining many concepts Claude already understands while providing code examples that are incomplete and not truly executable. The content would benefit significantly from aggressive trimming, splitting into focused reference files, and replacing pseudocode with complete, working examples.
Suggestions
Reduce content by 70%+ by removing explanations of basic concepts (what metrics are, what optimization means) and keeping only the specific MCP tool usage patterns
Make code examples fully executable by defining all helper functions or removing them in favor of inline implementations
Split into SKILL.md (quick start + tool overview) with separate files for EXAMPLES.md, METRICS.md, and INTEGRATION.md
Add explicit validation steps to workflows, especially for the 'Real-Time Optimization' section which involves continuous system changes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with extensive explanations of concepts Claude already knows (what bottleneck identification is, what throughput means, basic optimization concepts). Lists like 'System Performance Metrics' and 'Optimization Strategies' describe obvious concepts without adding actionable value. | 1 / 3 |
Actionability | Contains JavaScript code examples that appear executable, but many are pseudocode-like with undefined helper functions (e.g., buildAllocationMatrix, extractAllocation, calculateEfficiency). The MCP tool calls show structure but lack complete, copy-paste ready implementations. | 2 / 3 |
Workflow Clarity | Example workflows at the end list steps but lack validation checkpoints and error handling. The numbered workflows (Cloud Infrastructure Optimization, etc.) are high-level descriptions without explicit validation steps or feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed code examples, metric definitions, and integration patterns that could be split into separate reference documents. No clear navigation structure. | 1 / 3 |
Total | 6 / 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.
- 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.