agent-v3-performance-engineer
Agent skill for v3-performance-engineer - invoke with $agent-v3-performance-engineer
35
0%
Does it follow best practices?
Impact
96%
3.20xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-v3-performance-engineer/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 is an extremely weak description that provides virtually no useful information for skill selection. It only contains an invocation command and a generic label, failing on every dimension. Claude would have no basis to select this skill appropriately from a pool of available skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Profiles application performance, identifies bottlenecks, optimizes query execution, and analyzes resource utilization metrics.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions performance optimization, slow queries, latency issues, load testing, benchmarking, or resource profiling.'
Remove the invocation command from the description (it's operational metadata, not descriptive content) and replace with domain-specific language that distinguishes this skill from other engineering-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it's an 'agent skill' with an invocation command, providing zero information about what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides an invocation command with no explanation of capabilities or trigger conditions. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'performance-engineer' embedded in the agent name, but there are no natural keywords a user would say. No terms like 'optimize', 'benchmark', 'latency', 'profiling', or any domain-specific triggers are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from any other skill. 'Performance engineer' could overlap with many domains (web performance, database optimization, load testing, etc.) and provides no clear 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 essentially a project specification document masquerading as an agent skill. It defines aspirational performance targets and pseudocode benchmark classes that reference non-existent APIs, providing no actionable guidance Claude could follow. The content is extremely verbose, poorly structured for progressive disclosure, and lacks any concrete workflow for actually performing performance engineering tasks.
Suggestions
Replace pseudocode benchmark classes with actual executable commands or scripts that Claude can run (e.g., specific npm/node commands, real benchmark tool invocations, or actual test scripts with real file paths).
Add a clear step-by-step workflow: what to measure first, how to run benchmarks, how to interpret results, what to optimize, and how to validate improvements - with explicit validation checkpoints.
Reduce content to under 100 lines by moving detailed benchmark implementations to separate referenced files and keeping only a concise overview with concrete first steps in the main skill.
Replace the ASCII box diagrams and aspirational target descriptions with actionable instructions - Claude doesn't need motivational framing, it needs specific commands and decision criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. The ASCII box diagrams are decorative and redundant with the text. The TypeScript benchmark classes are lengthy pseudocode that Claude cannot execute - they reference non-existent APIs (this.sona.adapt, this.flashAttention, etc.) and serve as aspirational documentation rather than actionable instructions. The coordination section and mission statement add fluff. | 1 / 3 |
Actionability | Despite containing extensive TypeScript code, none of it is executable - all methods reference undefined APIs (this.agentDBMemory.hnswSearch, this.standardAttention, this.flashAttention, etc.). These are conceptual class skeletons, not copy-paste ready code. There are no concrete commands, real file paths, or actual implementation steps that Claude could follow to perform optimization work. | 1 / 3 |
Workflow Clarity | There is no clear sequential workflow for performing performance optimization. The content presents benchmark class definitions and a checklist but never explains what steps to take, in what order, or how to validate results. The checklist at the end is a list of goals, not a process. No feedback loops or error recovery steps are defined for any operation. | 1 / 3 |
Progressive Disclosure | The entire content is a monolithic wall of text with no references to external files. All benchmark classes are inlined despite being lengthy. There's no separation between overview/quick-start and detailed reference material. The content would benefit enormously from splitting benchmark implementations into separate files with a concise overview in the main skill. | 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.