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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill load-test-scenario-plannerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting only of the skill name repeated as trigger terms with no actual capability description. It fails to explain what the skill does, when to use it, or provide natural language triggers that users would actually say. This would make it nearly impossible for Claude to correctly select this skill from a library.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Designs load test scenarios, calculates expected concurrent users, defines ramp-up patterns, generates test scripts for tools like JMeter or k6').
Include a 'Use when...' clause with explicit triggers (e.g., 'Use when the user needs to plan performance tests, design load scenarios, estimate server capacity, or mentions stress testing, throughput, or concurrent users').
Add natural trigger terms users would actually say: 'performance test', 'stress test', 'load testing', 'concurrent users', 'throughput', 'scalability testing', 'capacity planning'.
| 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 | Neither 'what' nor 'when' is adequately answered. There's no explanation of capabilities and no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('load test scenario planner, load test scenario planner'). Missing natural user terms like 'performance test', 'stress test', 'concurrent users', 'throughput testing', 'JMeter', 'k6'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'load test scenario planner' is somewhat specific to performance testing domain, but without concrete actions or clear triggers, it could overlap with other performance testing or test planning skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template with no actual instructional value. It contains only meta-descriptions of what a skill should do without any concrete guidance on load test scenario planning - no example scenarios, no tool configurations, no code samples, and no actionable steps.
Suggestions
Add concrete examples of load test scenarios with specific configurations (e.g., k6 or JMeter scripts for common patterns like ramp-up, spike, and soak tests)
Include a workflow for planning load tests: define objectives → identify critical paths → set thresholds → design scenarios → validate results
Provide executable code snippets showing how to configure virtual users, think times, and assertions for different load patterns
Remove all generic boilerplate text and replace with specific, actionable guidance that Claude couldn't infer on its own
| 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 information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual load test scenarios. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes documented for planning load test scenarios. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no real information to organize. There are no references to detailed materials, no examples, and no structured content beyond empty section headers. | 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.