load-testing-apis

Execute 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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized with concrete, actionable steps and a clean reference structure, but it lacks explicit validation checkpoints in its load-ramp workflow and its referenced implementation guide is off-topic (API building instead of load testing). Conciseness is good with minor tightening opportunities.

Suggestions

Add explicit validation checkpoints between load stages, e.g. after each ramp level check error rate and p95 against thresholds before proceeding to 2x/5x/10x, to satisfy the batch-operation feedback-loop expectation.

Replace references/implementation.md (currently an API-building guide) with actual load-testing implementation guidance, or rename/repurpose it so the referenced "full implementation guide" matches the skill's load-testing scope.

Tighten the dense Overview sentence and remove or sharpen vague Resources entries (e.g. give the Google SRE chapter a URL, drop "Performance testing anti-patterns and best practices" or link a specific source).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not waste tokens explaining concepts Claude already knows, but the dense single-sentence Overview and vague Resources entries ("Performance testing anti-patterns and best practices", "Google SRE: Load Testing chapter" with no URL) could be tightened, matching the score-2 anchor of mostly efficient with some unnecessary content.	2 / 3
Actionability	The 9-step Instructions give concrete, specific guidance with real numbers and tools ("ramp-up (2 min), sustained load (10 min), spike (2 min at 3x)", "p95 response time < 500ms, error rate < 1%, throughput > 100 requests/second", "2x, 5x, and 10x"), and executable scripts are appropriately delegated to the examples reference, so the guidance is actionable per the code-vs-instruction scoring note.	3 / 3
Workflow Clarity	The steps are clearly sequenced (spec -> scenarios -> scripts -> thresholds -> execute -> analyze -> report), but for a heavy/batch operation like ramping load to 10x there are no explicit validation checkpoints between stages (e.g. verify error rate before increasing load), so per the destructive/batch cap it stays at score 2.	2 / 3
Progressive Disclosure	The structure is good: a concise overview with three real, one-level-deep, clearly signaled references (implementation.md, errors.md, examples.md). However the referenced "full implementation guide" (references/implementation.md) actually describes building an API rather than load testing, so the content is not appropriately split for this skill, pulling it below the score-3 anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states a clear niche, includes explicit "Use when" trigger guidance with natural phrases, and is unlikely to conflict with other skills. Its only weakness is specificity, relying on the vague qualifier "comprehensive" instead of enumerating concrete actions.

Suggestions

Replace "comprehensive" with a short list of concrete actions, e.g. "Generate k6/Artillery load-test scripts, model ramp-up and spike stages, assert p95/error-rate/throughput thresholds, and produce a bottleneck analysis report."

Optionally add "soak testing" to the description since the body covers it, so the stated capability set matches the skill's actual scope.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of actions ("Execute comprehensive load and stress testing to validate API performance and scalability") but does not enumerate multiple concrete capabilities; "comprehensive" is mild fluff rather than a specific action, matching the score-2 anchor of naming domain and some actions without being comprehensive.	2 / 3
Completeness	It explicitly answers both what ("Execute comprehensive load and stress testing to validate API performance and scalability") and when ("Use when validating API performance under load" plus explicit trigger phrases), matching the score-3 anchor that clearly answers both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Natural trigger phrases users would actually say are well covered: "load test the API", "stress test API", and "benchmark API performance", plus the "Use when validating API performance under load" clause, matching the score-3 anchor of good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	"Load testing APIs" is a clear niche with distinct, domain-specific triggers unlikely to collide with other skills, matching the score-3 anchor of a clear niche with distinct triggers and low conflict risk.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.