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
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 template placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among multiple available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs load test scenarios, defines virtual user profiles, calculates expected throughput targets, and generates test configuration files for tools like JMeter, k6, or Gatling.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about load testing, stress testing, performance benchmarks, concurrent user simulation, throughput planning, or scalability testing.'
Replace the duplicated skill name in the 'Triggers on' field with diverse natural keywords users would actually say, such as 'load test', 'stress test', 'performance test plan', 'simulate users', 'capacity planning', 'ramp-up strategy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Performance Testing') and a skill name ('Load Test Scenario Planner') but does not describe any concrete actions. There are no verbs indicating what the skill actually does—no mention of creating scenarios, configuring parameters, analyzing results, or any other specific capability. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful trigger guidance. The 'Triggers on' line is just the skill name repeated, not genuine usage context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('load test scenario planner, load test scenario planner'). There are no natural user keywords like 'load testing', 'stress test', 'performance benchmark', 'concurrent users', 'throughput', or 'scalability' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Load Test Scenario Planner' is somewhat specific to a niche (load testing scenario planning), which provides some distinctiveness. However, without concrete actions or clear triggers, it could overlap with other performance testing skills and lacks enough detail to clearly differentiate itself. | 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 an empty shell with no actual instructional content. It consists entirely of self-referential meta-descriptions that tell Claude about the skill's existence rather than teaching it how to plan load test scenarios. There is no actionable guidance, no code examples, no tool references (k6, JMeter, etc.), and no workflows despite the tags suggesting these should be covered.
Suggestions
Add concrete, executable code examples for at least one load testing tool (e.g., a k6 script or JMeter configuration) that demonstrates a realistic load test scenario.
Define a clear multi-step workflow for planning a load test scenario: e.g., 1) identify target endpoints, 2) define user profiles and ramp-up patterns, 3) set acceptance criteria/thresholds, 4) write the test script, 5) validate results against thresholds.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') and replace them with actual instructional content such as scenario templates, configuration patterns, and common load profiles.
Include specific examples of load test scenarios (e.g., spike test, soak test, stress test) with concrete parameters like virtual user counts, ramp-up durations, and threshold definitions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual actionable content. Every section restates the same vague information about 'load test scenario planner' without teaching Claude anything it doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific examples, no frameworks, no configurations. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill merely states it can provide 'step-by-step guidance' without including any actual steps. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to external files, and no layered structure. The sections are just repetitive meta-descriptions with no substance to disclose progressively. | 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
4dee593
- 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.