k6-script-generator
K6 Script Generator - Auto-activating skill for Performance Testing. Triggers on: k6 script generator, k6 script generator Part of the Performance Testing skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/k6-script-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title and category label rather than a functional skill description. It lacks concrete actions, natural trigger terms, and any explicit 'when to use' guidance. The duplicate trigger term and absence of meaningful detail make it one of the weakest possible descriptions for skill selection purposes.
Suggestions
Add specific concrete actions such as 'Generates k6 load testing scripts with configurable virtual users, ramp-up patterns, thresholds, and HTTP request scenarios'.
Add a 'Use when...' clause with natural trigger terms like 'load test', 'performance test', 'stress test', 'k6 script', 'benchmark API', or 'simulate traffic'.
Remove the duplicate trigger term and expand with varied natural language phrases users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('K6 Script Generator', 'Performance Testing') but does not describe any concrete actions like 'generates load test scripts', 'configures virtual users', or 'creates HTTP request scenarios'. It is essentially a label, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely weak (just a name, no actions described) and the 'when' is missing entirely — there is no 'Use when...' clause or equivalent explicit trigger guidance. It fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'k6 script generator' repeated twice. It misses natural user phrases like 'load test', 'performance test script', 'stress test', 'k6', 'load testing', or 'benchmark'. The repetition adds no value. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'K6' specifically does narrow the domain somewhat compared to generic performance testing tools, but the lack of concrete actions or clear triggers means it could still overlap with other performance testing or script generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder with no actionable information. It contains no k6 script examples, no executable code, no workflow steps, and no concrete guidance of any kind. It merely describes what the skill is supposed to do in vague, marketing-style language rather than actually teaching Claude how to generate k6 performance testing scripts.
Suggestions
Add concrete, executable k6 script examples (e.g., a basic HTTP load test, a stress test with ramping VUs) that Claude can use as templates.
Define a clear workflow for generating k6 scripts: gather requirements → select test type → generate script → validate options/thresholds → output final script.
Include specific k6 API patterns (e.g., `http.get`, `check()`, `sleep()`, `options` configuration with stages, thresholds) instead of abstract descriptions of capabilities.
Remove the meta-content about triggers and activation—this wastes tokens on information that belongs in frontmatter, not in the skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. It explains what triggers the skill rather than providing any actual k6 knowledge or code. | 1 / 3 |
Actionability | There is zero concrete guidance—no k6 script examples, no executable code, no specific commands, no configuration snippets. The entire content describes the skill abstractly rather than instructing Claude how to generate k6 scripts. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences for generating, validating, or running k6 scripts, and no validation checkpoints of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support deeper content. There is nothing to progressively disclose. | 1 / 3 |
Total | 4 / 12 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.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
22f797a
- 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.