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 what the skill does (design, execute, analyze performance tests and identify bottlenecks), when to use it (load/stress/spike/endurance testing scenarios), and includes rich natural trigger terms. The description is well-structured, specific, and distinctive, covering both capabilities and activation conditions comprehensively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'design, execute, and analyze performance tests', identifies bottleneck types (CPU, memory, database, network), and specifies reporting outputs (percentiles, graphs, recommendations). | 3 / 3 |
Completeness | Clearly answers both 'what' (design, execute, analyze performance tests; identify bottlenecks; provide reporting) and 'when' ('activated when the user requests load testing, stress testing, spike testing, or endurance testing, and when discussing performance metrics'). | 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'. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around performance testing with specific trigger terms like 'load testing', 'stress testing', 'spike testing', and 'endurance testing' that are unlikely to conflict with 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 reads like a marketing overview or README rather than actionable instructions for Claude. It lacks any concrete plugin invocation syntax, configuration examples, or executable code. The content mostly describes what the skill does conceptually rather than teaching Claude how to actually perform the tasks.
Suggestions
Add concrete plugin invocation syntax showing exactly how to call the performance-test-suite plugin, including parameter names, types, and example values (e.g., actual JSON/YAML configuration for a load test).
Replace the abstract 'The skill will' examples with executable, copy-paste-ready examples showing the actual commands or API calls Claude should use, including expected output formats.
Remove the 'How It Works', 'When to Use This Skill', 'Best Practices', and 'Integration' sections—these describe Claude's own behavior back to it and waste tokens. Replace with a quick-reference table of test types and their required parameters.
Add validation checkpoints to the workflow, such as how to verify a test configuration is valid before execution and how to interpret error responses from the plugin.
| 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 reasoning process back to it. 'When to Use This Skill', 'Best Practices', and 'Integration' sections add padding without actionable value. | 1 / 3 |
Actionability | There are no concrete commands, code snippets, API calls, or plugin invocation syntax. The examples describe what 'the skill will' do in abstract terms rather than showing actual plugin commands, configuration formats, or executable steps. There is no indication of how to actually invoke the performance-test-suite plugin. | 1 / 3 |
Workflow Clarity | The workflow steps are abstract descriptions ('Design a load test configuration', 'Execute the load test') with no concrete commands, validation checkpoints, or error recovery steps. There is no guidance on what to do if a test fails to start, produces unexpected results, or how to verify test configuration before execution. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, which provides some structure. However, there are no references to external files, no bundle files exist, and content that could be separated (e.g., detailed configuration schemas, metric interpretation guides) is neither inline nor referenced—it's simply absent. | 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
13d35b8
- 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.