soak-test-planner
Soak Test Planner - Auto-activating skill for Performance Testing. Triggers on: soak test planner, soak test planner Part of the Performance Testing skill category.
33
3%
Does it follow best practices?
Impact
85%
1.28xAverage 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/soak-test-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 label rather than a functional description. It names the skill and its category but provides no concrete actions, no meaningful trigger terms beyond the skill name repeated, and no explicit guidance on when Claude should select it. It would be nearly useless for skill selection among multiple performance testing skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates soak test plans including duration, load profiles, resource monitoring thresholds, and success criteria for long-running stability tests.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about endurance testing, long-duration load tests, stability testing, soak tests, or sustained performance validation.'
Include variations of terminology users might use such as 'endurance test', 'stability test', 'long-running performance test', 'sustained load test' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Performance Testing') and the concept ('Soak Test Planner') but does not describe any concrete actions. There are no verbs indicating what the skill actually does—no 'generates plans', 'configures test parameters', 'analyzes endurance results', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'soak test planner' repeated twice. It misses natural variations users might say such as 'endurance test', 'long-running test', 'stability test', 'soak testing', 'load test duration', or 'performance soak'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'soak test' is fairly niche within performance testing, which provides some distinctiveness. However, the vague 'Performance Testing' category label could overlap with other performance testing skills (load test, stress test, etc.) since no distinguishing details are provided. | 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 substantive content. It contains only meta-descriptions and trigger phrases but provides zero actionable guidance on soak test planning—no test configurations, no tool-specific instructions (k6, JMeter), no duration/load parameters, no monitoring guidance, and no example scripts. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable soak test examples using k6 or JMeter (e.g., a complete k6 script with ramping stages, duration settings, and thresholds for a typical soak test).
Define a clear multi-step workflow: 1) determine baseline metrics, 2) configure soak test parameters (duration, VUs, ramp-up), 3) run the test, 4) monitor for memory leaks/resource degradation, 5) validate results against thresholds.
Include specific guidance on what distinguishes soak tests from other performance tests (e.g., recommended durations, key metrics to watch like memory growth and response time drift), with concrete threshold examples.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual instructional content that teaches how to plan and execute soak tests.
| 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 instructions, code, or actionable content. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of soak test configurations, no tool usage. It only describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section mentions 'step-by-step guidance' but none is actually provided. | 1 / 3 |
Progressive Disclosure | There are no references to external files, no structured navigation, and no layered content. The document is a shallow placeholder with no depth or organization beyond boilerplate headings. | 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.