load-testing-apis

Quick Review

The skill has a clear structure with separated reference files, but suffers from a critical mismatch between its stated purpose (load/stress testing APIs) and its actual content (which describes API development/implementation). The description promises load testing capabilities with phrases like 'load test the API' and 'benchmark API performance', but the instructions focus on API design, endpoint creation, authentication, and boilerplate generation. This fundamental disconnect makes it unclear to a CLI agent what this skill actually does. The instructions appear to be copy-pasted from an API development skill rather than load testing. For actual load testing, one would expect steps involving traffic generation tools (JMeter, Locust, k6), concurrent request handling, performance metrics collection, and bottleneck analysis—none of which are present. The novelty is low because load testing is well-handled by existing dedicated tools.