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 extremely thin—it reads more like a metadata tag than a functional skill description. It lacks concrete actions, natural trigger terms, and an explicit 'when to use' clause. The only redeeming quality is the mention of 'k6' which provides minimal tool-level distinctiveness.
Suggestions
Add specific concrete actions such as 'Generates k6 load testing scripts, configures virtual user scenarios, creates HTTP request definitions, and sets performance thresholds'.
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about load testing, performance testing, stress testing, k6 scripts, or benchmarking APIs'.
Remove the duplicate trigger term and expand with natural variations users would say: 'k6', 'load test', 'performance script', 'stress test', 'benchmark', '.js test script'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'K6 Script Generator' and mentions 'Performance Testing' but does not list any concrete actions like 'generates load test scripts', 'configures virtual users', or 'creates HTTP request scenarios'. It's essentially just a name and category label. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the name 'K6 Script Generator') and the 'when' is only implied through the repeated trigger phrase. There is no explicit 'Use when...' clause or meaningful description of capabilities. | 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 API'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'k6' specifically does narrow the domain to a particular tool, which provides some distinctiveness. However, the generic 'Performance Testing' category label could overlap with other performance testing skills (e.g., JMeter, Locust). | 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 is essentially a placeholder or template with no substantive content. It contains no k6 code examples, no load testing patterns, no configuration guidance, and no actionable instructions whatsoever. Every section merely restates that the skill is about 'k6 script generator' without teaching Claude anything useful.
Suggestions
Add concrete, executable k6 script examples (e.g., a basic HTTP load test, a ramping VU scenario, threshold configuration) that Claude can directly use or adapt.
Include specific k6 CLI commands (e.g., `k6 run script.js`, `k6 run --vus 50 --duration 30s script.js`) and common configuration patterns.
Define a clear workflow for generating k6 scripts: gather requirements → select test type → generate script → validate with dry run → iterate, with explicit validation steps.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual k6 knowledge, patterns, and best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual k6 knowledge, code, or configuration. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no k6 script examples, no commands, no code snippets, no configuration patterns. The content describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' as a capability but never actually provides any steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. | 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
700215b
- 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.