load-testing-apis
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill load-testing-apisExecute comprehensive load and stress testing to validate API performance and scalability. Use when validating API performance under load. Trigger with phrases like "load test the API", "stress test API", or "benchmark API performance".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill is fundamentally misaligned - it claims to be about load testing APIs but contains generic API development boilerplate instead. There are no load testing tools, metrics, commands, or workflows. The content appears to be a template that wasn't customized for the stated purpose.
Suggestions
Replace the generic API development content with actual load testing instructions using specific tools (k6, locust, wrk, or artillery) with executable code examples
Add concrete load testing workflow: define test scenarios → configure load parameters → execute tests → analyze metrics → validate against thresholds
Include specific metrics to capture (RPS, latency percentiles, error rates) and how to interpret results
Provide example load test scripts that are copy-paste ready with realistic scenarios (ramp-up, sustained load, spike testing)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't relate to load testing. It explains prerequisites Claude already knows and includes irrelevant sections about API development (routes, controllers, models) rather than load testing specifics. | 1 / 3 |
Actionability | No concrete load testing code, commands, or tools are provided. The instructions describe general API development steps rather than actual load testing procedures. Missing specific tools like k6, locust, or wrk with executable examples. | 1 / 3 |
Workflow Clarity | The numbered steps are for API development, not load testing. There's no clear workflow for executing load tests, analyzing results, or validating performance thresholds. No validation checkpoints for test results. | 1 / 3 |
Progressive Disclosure | References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is poorly organized and doesn't provide a useful overview of load testing before pointing to references. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
90%This is a solid skill description with excellent trigger term coverage and completeness. The explicit 'Use when' and 'Trigger with phrases' clauses make it easy for Claude to know when to select this skill. The main weakness is that the capabilities could be more specific about what concrete actions the skill performs beyond the high-level 'validate performance and scalability'.
Suggestions
Add specific concrete actions like 'simulate concurrent users', 'measure response times and throughput', 'generate performance reports', or 'identify bottlenecks under load' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (load/stress testing, API performance) and general actions (validate performance and scalability), but lacks specific concrete actions like 'simulate concurrent users', 'measure response times', 'generate performance reports', or 'identify bottlenecks'. | 2 / 3 |
Completeness | Clearly answers both what (execute load and stress testing to validate API performance and scalability) and when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples). | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms users would say: 'load test', 'stress test', 'benchmark', 'API performance'. These are common phrases developers use when requesting this type of testing. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on load/stress testing for APIs with distinct triggers like 'load test', 'stress test', 'benchmark API performance' - unlikely to conflict with general API testing or other performance skills. | 3 / 3 |
Total | 11 / 12 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.