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
Quality
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 severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs, what outputs it produces, or meaningful guidance on when Claude should select it. The redundant trigger terms and lack of concrete capabilities make this ineffective for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates soak test plans including duration, load profiles, resource monitoring strategies, and success criteria'
Add a proper 'Use when...' clause with natural trigger terms like 'endurance testing', 'stability testing', 'long-running performance test', 'sustained load test'
Include context about what distinguishes soak tests from other performance tests (e.g., 'for testing system stability under sustained load over extended periods')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Soak Test Planner') and category ('Performance Testing') without describing any concrete actions. There are no verbs indicating what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The trigger list is not a proper 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'soak test planner' repeated twice, which is redundant and overly narrow. Missing natural variations like 'endurance test', 'long-running test', 'stability test', or 'load testing'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'soak test' is fairly specific to performance testing, which provides some distinctiveness. However, the generic 'Performance Testing' category could overlap with other performance-related skills. | 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 essentially an empty placeholder with no substantive content. It describes what a soak test planner skill would do in abstract terms but provides zero actual guidance on planning soak tests—no durations, load profiles, metrics to monitor, tools to use, or example configurations. The entire content could be replaced with actual soak testing knowledge.
Suggestions
Add concrete soak test parameters: typical durations (4-24 hours), load levels (60-80% capacity), and key metrics to monitor (memory leaks, response time degradation, connection pool exhaustion)
Include executable code examples for k6 or JMeter showing a basic soak test configuration with appropriate ramping and duration settings
Define a clear workflow: 1) Establish baseline metrics, 2) Configure test duration and load, 3) Set up monitoring/alerting, 4) Define success criteria, 5) Analyze results for degradation patterns
Add specific examples of what soak tests detect (memory leaks, database connection exhaustion, log file growth) with corresponding monitoring approaches
| 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 soak test planning information. | 1 / 3 |
Actionability | Contains zero concrete guidance on how to actually plan a soak test. No code, no commands, no specific parameters, durations, metrics, or thresholds. Entirely abstract descriptions with no executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. A soak test planner should specify steps like defining duration, load levels, monitoring metrics, and success criteria, but none of this is present. | 1 / 3 |
Progressive Disclosure | No actual content to organize. The skill mentions 'Related Skills' and tags but provides no references to detailed materials, examples, or supporting documentation that would help with soak test planning. | 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.