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.

48

Quality

53%

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 ./skills/k6-load-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%Scale 1-5

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

This skill is a comprehensive k6 reference guide but is poorly suited as a SKILL.md for Claude. It's excessively verbose, explaining basics Claude already knows, repeating similar patterns across sections, and inlining all content in a single monolithic file rather than using progressive disclosure. The code examples are its strongest asset—they're executable and cover a wide range of k6 features—but the lack of a clear workflow with validation checkpoints and the sheer volume of content undermine its effectiveness.

Suggestions

Reduce content by 60-70%: Remove installation instructions, the 'When to Use' section, the overview paragraph, and deduplicate code examples (the basic API test appears three times in slightly different forms).

Split into multiple files: Move HTTP testing, browser testing, WebSocket testing, data handling, CI/CD integration, and custom metrics into separate reference files, keeping SKILL.md as a concise overview with links.

Add an explicit workflow with validation: Define a clear sequence like 1) Write test with thresholds → 2) Run smoke test (1-5 VUs) → 3) Verify smoke passes → 4) Scale to target load → 5) Analyze results against thresholds → 6) If thresholds fail, investigate and iterate.

Remove the 'Related Skills' and 'Additional Resources' sections or compress them to a single line each—external URLs and cross-references to other skills add little value in the context window.

DimensionReasoningScore

Conciseness

Severely verbose for a skill targeting Claude. Explains installation steps across three OSes (Claude knows how to install packages), includes an overview section explaining what k6 is, a 'When to Use This Skill' section that's largely obvious, and repeats similar code patterns multiple times (e.g., the basic API test appears nearly identically in Quick Start, HTTP Testing, and Examples sections). The test types table and results interpretation table add bulk without much actionable value.

2 / 5

Actionability

Provides extensive executable code examples covering HTTP, WebSocket, browser testing, data handling, CI/CD configs, and custom metrics. Code is copy-paste ready with proper imports and options. Minor gap: some examples use placeholder URLs and the CI/CD examples could be more specific about threshold checking and result parsing.

4 / 5

Workflow Clarity

The skill presents individual code snippets well but lacks a clear end-to-end workflow for running a load test campaign. There's no explicit sequence like: write test → run smoke → validate results → scale up → analyze. The Best Practices section hints at a workflow ('start with smoke test') but doesn't formalize it with validation checkpoints. For a skill involving performance testing where incorrect configurations could waste resources or produce misleading results, the absence of validation/verification steps is notable.

3 / 5

Progressive Disclosure

This is a monolithic ~400-line file with no bundle files to offload content to. The extensive HTTP testing examples, WebSocket testing, browser testing, data handling, custom metrics, and CI/CD integration sections could each be separate reference files. Everything is inlined in one massive document with no references to supporting files, making it hard to navigate and consuming excessive context window.

2 / 5

Total

11

/

20

Passed

Description

61%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 identifies the tool (k6) and domain (load testing) clearly, with several useful trigger terms. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know precisely when to select this skill. The capabilities listed are somewhat high-level and could benefit from more concrete specifics.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about performance testing, load testing, k6 scripts, stress testing, or benchmarking APIs'

Include additional synonyms and related terms like 'performance testing', 'stress testing', 'spike testing', 'soak testing' to improve trigger term coverage

Add more specific capabilities like 'configure thresholds, define virtual users (VUs), set up checks, handle correlations, create custom metrics'

DimensionReasoningScore

Specificity

Names the domain (k6 load testing) and mentions a few actions ('write realistic load scenarios, analyze results, integrate with CI/CD') but these are somewhat generic and not comprehensive - missing specifics like threshold configuration, custom metrics, protocol details, etc.

3 / 5

Completeness

Has a clear 'what' (write load scenarios, analyze results, integrate with CI/CD) but lacks an explicit 'when' clause. There's no 'Use when...' guidance to tell Claude when to select this skill over others.

3 / 5

Trigger Term Quality

Includes good natural keywords like 'k6', 'load testing', 'API', 'browser', 'scalability testing', 'CI/CD', and 'load scenarios'. Missing some variations like 'performance testing', 'stress testing', 'grafana', or file extensions like '.js' scripts.

4 / 5

Distinctiveness Conflict Risk

The mention of 'k6' specifically makes this fairly distinct from generic testing or performance skills. However, 'API testing' and 'CI/CD' integration could overlap with other testing-related skills. The k6 specificity reduces most conflict risk.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation9 / 11 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

9

/

11

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.