load-testing-apis

Quick Review

The skill has a clear structure with good separation of concerns (main file plus references), but suffers from a critical mismatch between its stated purpose and implementation. The description promises 'load and stress testing to validate API performance' but the instructions describe API development/implementation tasks (creating routes, controllers, models). The Prerequisites and Output sections reinforce this API-building focus rather than load testing. While taskKnowledge scores moderately (assuming referenced files contain relevant content), descriptionCoverage is low because a CLI agent would be confused about whether to build APIs or test them. Novelty is modest as load testing tools (k6, JMeter, Locust) are standard and the skill doesn't clearly demonstrate cost savings over direct tool usage. To improve: align all content with load testing (test plan creation, execution with tools like k6/Artillery, metrics collection, bottleneck analysis), clarify when to use this over running 'k6 run script.js' directly, and ensure the description matches the actual workflow.