performance-testing
This skill enables Claude to design, execute, and analyze performance tests using the performance-test-suite plugin. It is activated when the user requests load testing, stress testing, spike testing, or endurance testing, and when discussing performance metrics such as response time, throughput, and error rates. It identifies performance bottlenecks related to CPU, memory, database, or network issues. The plugin provides comprehensive reporting, including percentiles, graphs, and recommendations.
92
53%
Does it follow best practices?
Impact
100%
1.00xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/performance-test-suite/skills/performance-test-suite/SKILL.mdQuality
Discovery
100%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 a strong skill description that clearly articulates specific capabilities (designing, executing, analyzing performance tests and identifying bottlenecks), includes explicit trigger conditions with natural user terms (load testing, stress testing, response time, throughput), and occupies a distinct niche. The only minor issue is the use of 'It is activated' which is acceptable third-person voice, and the description could be slightly more concise, but overall it is well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'design, execute, and analyze performance tests', identifies bottlenecks related to 'CPU, memory, database, or network issues', and provides 'percentiles, graphs, and recommendations'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (design, execute, analyze performance tests; identify bottlenecks; provide reporting with percentiles, graphs, recommendations) and 'when' ('activated when the user requests load testing, stress testing, spike testing, or endurance testing, and when discussing performance metrics'). Explicit trigger guidance is present. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'load testing', 'stress testing', 'spike testing', 'endurance testing', 'response time', 'throughput', 'error rates', 'performance bottlenecks', 'CPU', 'memory', 'database', 'network'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around performance testing with specific plugin reference ('performance-test-suite plugin'). The trigger terms are highly specific to performance/load testing and unlikely to conflict with general coding, monitoring, or other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content reads like a marketing overview rather than actionable instructions for Claude. It lacks any concrete plugin API calls, configuration examples, command syntax, or executable code. The content mostly describes what the skill does in abstract terms and explains concepts Claude already knows, wasting token budget without providing the specific guidance needed to actually perform performance testing.
Suggestions
Add concrete, executable examples showing actual plugin API calls or commands (e.g., the exact function/tool call to configure and run a load test with specific parameters).
Replace the abstract 'How It Works' section with a step-by-step workflow containing actual commands, configuration schemas, and validation checkpoints (e.g., 'verify test config before execution').
Remove the 'When to Use This Skill' and 'Best Practices' sections—these explain things Claude already knows—and replace them with a configuration reference showing supported parameters, their types, and defaults.
Add a concrete example showing the expected output format (report structure, metrics schema) so Claude knows exactly what to produce after test execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what load/stress/spike/endurance tests are, what metrics are). The 'How It Works' section describes Claude's own behavior back to it. 'When to Use This Skill' repeats the description. Best Practices are generic platitudes Claude already understands. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no plugin API calls, no configuration schemas, and no copy-paste ready examples. The examples describe what the skill 'will do' in abstract terms rather than showing actual plugin invocations or configuration syntax. | 1 / 3 |
Workflow Clarity | The workflow steps are vague descriptions ('design a load test configuration', 'execute the load test') with no actual commands, validation checkpoints, or error recovery steps. There is no guidance on what to do if a test fails or produces unexpected results. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, which provides some structure. However, it's a monolithic document with no references to external files for detailed configuration schemas, API references, or advanced usage patterns. | 2 / 3 |
Total | 5 / 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.
- Commit
c8a915c
- 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.