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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill performance-testing67
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/skillValidation for skill structure
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), includes comprehensive trigger terms covering multiple testing types and metrics, and explicitly states when it should be activated. The description uses proper third-person voice and provides enough detail to distinguish it from other testing or monitoring skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'design, execute, and analyze performance tests', identifies specific bottleneck types (CPU, memory, database, network), and describes specific outputs (percentiles, graphs, recommendations). | 3 / 3 |
Completeness | Clearly answers both what ('design, execute, and analyze performance tests', 'comprehensive reporting') AND when ('activated when the user requests load testing, stress testing...' and 'when discussing performance metrics'). | 3 / 3 |
Trigger Term Quality | Includes excellent natural keywords 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 | Clear niche focused specifically on performance testing with distinct triggers like 'load testing', 'stress testing', 'spike testing', 'endurance testing' - unlikely to conflict with general testing or monitoring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%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 more like a product description than actionable guidance for Claude. It explains concepts at a high level but fails to provide the concrete plugin syntax, configuration examples, or executable commands needed for Claude to actually perform performance testing. The workflow is described abstractly without validation steps or error handling.
Suggestions
Add concrete plugin invocation syntax showing exactly how to call the performance-test-suite plugin with specific parameters (e.g., `performance_test.run({type: 'load', users: 200, duration: '10m'})`)
Replace the abstract examples with actual configuration code or command examples that Claude can execute directly
Add validation checkpoints to the workflow, such as how to verify test configuration before execution and how to handle test failures
Remove the 'When to Use This Skill' section as it duplicates information already conveyed by the examples and description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'This skill automates performance testing workflows' and the 'How It Works' section describes what Claude would naturally do). The 'When to Use This Skill' section is redundant given the examples already demonstrate use cases. | 2 / 3 |
Actionability | No concrete code, commands, or plugin invocation syntax is provided. The examples describe what the skill 'will do' abstractly rather than showing actual plugin calls, configuration formats, or executable commands. | 1 / 3 |
Workflow Clarity | Steps are listed in the 'How It Works' section but lack specificity—no validation checkpoints, no error handling guidance, and no concrete commands for each step. The workflow is conceptual rather than actionable. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline with no references to detailed documentation. The 'Integration' section mentions other plugins without linking to relevant resources. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
- 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.