load-test-scenario-planner
Load Test Scenario Planner - Auto-activating skill for Performance Testing. Triggers on: load test scenario planner, load test scenario planner Part of the Performance Testing skill category.
36
Quality
3%
Does it follow best practices?
Impact
99%
1.04xAverage 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/load-test-scenario-planner/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 placeholder with no substantive content. It repeats the skill name as trigger terms, provides no concrete actions or capabilities, and lacks any guidance on when Claude should select this skill. The description would be indistinguishable from any other performance testing skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs load test scenarios, calculates concurrent user loads, defines ramp-up patterns, and generates test scripts for tools like JMeter or k6.'
Replace the redundant trigger terms with natural variations users would say: 'load test', 'stress test', 'performance test', 'simulate traffic', 'concurrent users', 'throughput testing'.
Add an explicit 'Use when...' clause: 'Use when the user needs to plan performance tests, design load scenarios, or determine how to stress test an application.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the skill name repeated. It doesn't describe what the skill actually does (e.g., 'designs load test scenarios', 'calculates concurrent users', 'generates test scripts'). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the name rather than providing meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('load test scenario planner, load test scenario planner'). This is redundant and misses natural variations users might say like 'performance test', 'stress test', 'load testing', 'simulate users', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'load test scenario planner' is somewhat specific to performance testing, the lack of detail about what distinguishes it from other performance testing skills (if any) and the generic 'Performance Testing skill category' label creates potential overlap risk. | 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 a placeholder template with no actual instructional value. It contains only meta-descriptions of what the skill should do without any concrete guidance on load test scenario planning, k6/JMeter configurations, or performance testing workflows. The content fails all dimensions by providing zero actionable information.
Suggestions
Add concrete examples of load test scenarios with executable k6 or JMeter code snippets
Define a clear workflow for planning load tests: identify endpoints → define user patterns → set thresholds → create script → validate → execute
Include specific guidance on calculating virtual users, ramp-up patterns, and duration based on production traffic
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-descriptions Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes what the skill 'can do' without actually showing how to plan load test scenarios, create scripts, or configure tools. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for planning load test scenarios, no validation checkpoints, and no process for creating or reviewing test plans. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure exists. There are no references to detailed documentation, no links to examples, and no organization of content by complexity or use case. | 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
0c08951
- 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.