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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill k6-script-generatorActivation
22%This description is a minimal template that fails to explain what the skill actually does or when it should be used. It relies entirely on the skill name for identification and provides no concrete actions, use cases, or natural trigger terms that users would actually say when needing performance testing help.
Suggestions
Add specific actions the skill performs, e.g., 'Generates k6 load testing scripts with virtual user scenarios, thresholds, and HTTP request configurations'
Add a 'Use when...' clause with natural triggers like 'Use when the user needs load tests, stress tests, performance benchmarks, or mentions k6, load testing, or API performance'
Include common file extensions and terms users associate with k6 such as '.js test files', 'virtual users', 'ramp-up', 'throughput testing'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'K6 Script Generator' without listing any concrete actions. It doesn't explain what generating a k6 script involves (e.g., creating load tests, defining virtual users, setting thresholds, writing scenarios). | 1 / 3 |
Completeness | The 'what' is extremely weak (just names the skill type) and the 'when' only lists the exact skill name as a trigger, not meaningful use cases. No explicit 'Use when...' clause with real scenarios. | 1 / 3 |
Trigger Term Quality | Includes 'k6 script generator' as a trigger term (duplicated), and mentions 'Performance Testing' category. Missing natural variations users might say like 'load test', 'stress test', 'performance script', 'k6 test', or 'load testing'. | 2 / 3 |
Distinctiveness Conflict Risk | The k6-specific naming provides some distinctiveness from generic testing skills, but 'Performance Testing' category is broad and could overlap with other performance testing tools (JMeter, Gatling, Locust scripts). | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actual content. It describes what a k6 script generator skill would do without providing any actual k6 knowledge, code examples, or actionable guidance. The entire content could be replaced with actual k6 script patterns, options configuration, and executable examples.
Suggestions
Add executable k6 script examples showing common patterns (HTTP requests, checks, thresholds, stages)
Include concrete code for different load testing scenarios (smoke test, load test, stress test, spike test)
Provide a clear workflow: define scenario → write script → configure options → run test → analyze results
Add specific k6 CLI commands and options configuration examples that are copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual k6-specific information. | 1 / 3 |
Actionability | There is zero concrete guidance - no k6 script examples, no code snippets, no specific commands, no actual instructions on how to generate k6 scripts. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for generating k6 scripts, no validation checkpoints, and no process to follow. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual k6 content. No references to detailed materials, examples, or advanced topics are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.