agent-v3-performance-engineer
Agent skill for v3-performance-engineer - invoke with $agent-v3-performance-engineer
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-v3-performance-engineer35
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 — 96%
↑ 3.20xAgent 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 only as an invocation reference rather than a functional description, providing no information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a skill library.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Profiles code execution, identifies bottlenecks, optimizes database queries, analyzes memory usage')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions slow performance, optimization, profiling, benchmarks, or latency issues')
Remove the invocation syntax from the description and replace with functional content that explains what performance engineering tasks this skill handles
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for v3-performance-engineer' is completely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what does this do' and 'when should Claude use it'. The description only provides an invocation command, not functional information or usage triggers. | 1 / 3 |
Trigger Term Quality | No natural keywords users would say. 'v3-performance-engineer' is technical jargon/internal naming, not terms like 'optimize', 'performance', 'speed', 'profiling', or 'benchmarking' that users would naturally use. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Agent skill' could apply to any skill. Without describing what performance engineering tasks it handles, it's impossible to distinguish from other potential performance or engineering skills. | 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 a verbose specification document masquerading as actionable guidance. It repeatedly states performance targets (2.49x-7.47x, 150x-12,500x) without providing any concrete steps to achieve them. The extensive TypeScript code is illustrative pseudocode that cannot be executed, and the document lacks any real workflow for performance optimization.
Suggestions
Replace illustrative TypeScript classes with actual executable benchmark commands or scripts that exist in the codebase
Add a concrete step-by-step workflow: 1) Run baseline benchmark, 2) Apply optimization X, 3) Validate improvement, 4) If target not met, try Y
Remove redundant target repetition - state targets once in a summary table, then focus on HOW to achieve them
Extract the benchmark code into referenced files (e.g., 'See benchmarks/flash-attention.ts') and keep SKILL.md as a concise overview with navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive ASCII art boxes, repetitive target listings, and massive TypeScript code blocks that are illustrative rather than executable. The same performance targets are repeated multiple times across different sections. | 1 / 3 |
Actionability | The TypeScript code is conceptual/illustrative rather than executable - classes reference undefined methods, missing imports, and non-existent APIs. No concrete commands or copy-paste ready instructions for actually running benchmarks or achieving the stated targets. | 1 / 3 |
Workflow Clarity | No clear workflow for how to actually achieve the performance targets. The checklist at the end lists goals but not steps. No validation checkpoints, no sequence of operations, and no feedback loops for the optimization process. | 1 / 3 |
Progressive Disclosure | Monolithic wall of content with no references to external files. All benchmark code is inline despite being extensive. The 'Coordination with V3 Team' section references other agents but provides no actual links or navigation structure. | 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.
- 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.