CtrlK
BlogDocsLog inGet started
Tessl Logo

k6-load-testing

Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.

57

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/k6-load-testing/SKILL.md

The canonical home for this skill is k6-load-testing in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

A rich, code-first reference with strong actionability and decent conciseness, but it is a single monolithic file with no progressive disclosure into bundle references and lacks an explicit validated workflow. Splitting advanced sections into referenced files and adding a validation-gated run workflow would raise the weakest dimensions.

Suggestions

Move advanced material (browser, WebSocket, CI/CD configs, full threshold reference) into separate files under references/ and link to them one level deep, leaving SKILL.md a concise overview.

Add an explicit load-test workflow with validation checkpoints (run smoke → verify checks pass → scale up → confirm thresholds → abort-on-fail), including a fix→retry feedback loop.

Correct the minor code inaccuracies (browser install command, load-zone key typo, Prometheus remote-write output flag) so examples are truly copy-paste ready.

DimensionReasoningScore

Conciseness

The body is code-heavy and mostly lean, assuming Claude's competence with little concept re-explanation; minor padding in the Overview/When-to-Use prose keeps it just below a 5.

4 / 5

Actionability

Abundant copy-paste-ready executable code across HTTP, browser, WebSocket, data, thresholds, metrics, and CI/CD, but a few examples have minor inaccuracies ("k6 install chromium", "amazon:eu: Dublin" typo, Prometheus remote-write flag syntax).

4 / 5

Workflow Clarity

Content is organized as topical reference sections rather than a sequenced multi-step process, and there are no explicit validation checkpoints or fix→retry feedback loops for the load-test lifecycle.

3 / 5

Progressive Disclosure

The 615-line body is well-sectioned with headers but monolithic — content like CI/CD configs, browser, and WebSocket guides could live in separate reference files, and no bundle files or external references exist (the <50-line simple-skill exception does not apply).

3 / 5

Total

14

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 concretely names the k6 domain and several actions with good trigger keywords and strong distinctiveness, but it lacks an explicit "Use when..." trigger clause, which caps its completeness. Adding a usage-trigger sentence would lift the weakest dimension.

Suggestions

Add an explicit trigger clause, e.g. "Use when load testing HTTP/WebSocket APIs or browser scenarios, setting up performance regression tests in CI/CD, or validating SLAs."

Include natural synonyms users say ("performance testing", "stress/spike/soak tests") to broaden trigger coverage.

Optionally note file-extension or tooling triggers ("k6", ".js test scripts") to sharpen distinctiveness further.

DimensionReasoningScore

Specificity

Names the domain (k6 load testing for API, browser, scalability) and lists several concrete actions — "Write realistic load scenarios, analyze results, and integrate with CI/CD" — but stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Clearly states what the skill does, but provides no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("load testing", "API", "browser", "scalability testing", "CI/CD") but misses common synonyms a user might say such as "performance testing" or "stress test".

4 / 5

Distinctiveness Conflict Risk

The "k6 load testing" niche with API/browser/scalability triggers is clearly distinct from other skills and unlikely to fire for the wrong skill.

5 / 5

Total

16

/

20

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

skill_md_line_count

SKILL.md is long (628 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.