CtrlK
BlogDocsLog inGet started
Tessl Logo

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

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The skill body is concise and well-structured with strong progressive disclosure, but its workflow lacks validation feedback loops and the top-level file delegates all executable code to references rather than providing copy-paste-ready guidance inline.

Suggestions

Add a validation/feedback step to the workflow (e.g., after executing a load test, verify thresholds passed before scaling to the next multiplier, and re-run with adjusted parameters if a stage fails) to reach workflow_clarity 3.

Include at least one minimal executable k6 or wrk snippet directly in SKILL.md (or a copy-paste run command) so actionability does not depend on opening a reference file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, giving concrete ramp profiles and thresholds without explaining basic concepts; every section earns its place.

3 / 3

Actionability

The guidance is concrete (specific stages, p95 < 500ms, error rate < 1%), but SKILL.md itself contains no executable code or ready-to-run commands — the runnable examples live only in references/examples.md — so it is not fully copy-paste ready at the top level.

2 / 3

Workflow Clarity

The 9-step sequence is clearly ordered, but load testing is a batch/resource-intensive operation with no validation checkpoints or fix→retry feedback loops in the main workflow; per the rubric feedback-loops note this caps workflow_clarity at 2.

2 / 3

Progressive Disclosure

A concise overview points to one-level-deep, clearly signaled references (implementation.md, errors.md, examples.md), all of which are real files with appropriately split content and easy navigation.

3 / 3

Total

10

/

12

Passed

Description

85%Weight 40%Scale 1-3

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 clearly communicates a specific niche with explicit what/when guidance and natural trigger phrases. Its main weakness is mild abstraction in naming capabilities rather than enumerating several concrete actions.

Suggestions

Replace the abstract "Execute comprehensive load and stress testing" with a concrete action list (e.g., "Generate k6/Artillery load test scripts, ramp virtual users to find breaking points, and report latency/throughput against SLOs") to lift specificity to 3.

Drop the filler word "comprehensive" since it does not add information a user or Claude can act on.

DimensionReasoningScore

Specificity

It names the domain ("load and stress testing") and actions ("validate API performance and scalability"), but "comprehensive" and "validate" are somewhat abstract and it does not enumerate multiple concrete actions like the score-3 anchor, so it sits at the level below.

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 trigger phrases), matching the score-3 anchor with an explicit 'Use when...' clause.

3 / 3

Trigger Term Quality

"load test the API", "stress test API", and "benchmark API performance" are natural phrases a user would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

API load/stress testing is a clear niche with distinct triggers ("load test the API", "benchmark API performance"), making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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