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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill soak-test-plannerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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, lacks diverse trigger terms, and gives Claude no guidance on when to select this skill. The only slight positive is that 'soak test' is a somewhat specific term in the performance testing domain.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates soak test plans, defines duration parameters, establishes baseline metrics, and monitors system stability over extended periods.'
Include a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to plan endurance tests, long-running performance tests, stability testing, or wants to verify system behavior under sustained load.'
Add natural keyword variations users might say: 'endurance test', 'stability test', 'long-duration test', 'sustained load test', 'memory leak detection'.
| 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' (no actions described) and 'when should Claude use it' (no explicit use-case guidance beyond the narrow trigger phrase). Both components are missing or very weak. | 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 somewhat specific to a particular type of performance testing, which provides some distinctiveness. However, the vague 'Performance Testing' category could overlap with other performance-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no actual instructional value. It describes what a soak test planner skill would do without providing any concrete guidance, code examples, test configurations, or workflows for planning soak tests. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete soak test configuration examples (e.g., k6 or JMeter scripts) with specific duration, ramp-up, and steady-state parameters
Include a clear workflow: 1) Define baseline metrics, 2) Configure test duration (typically 4-24 hours), 3) Set up monitoring, 4) Define pass/fail criteria, 5) Analyze results
Provide specific guidance on what to monitor during soak tests (memory leaks, connection pool exhaustion, disk space, response time degradation)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual soak testing instructions
| 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 about soak testing. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of soak test configurations. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. A soak test planner should include steps for defining test duration, load patterns, resource monitoring, and success criteria - none of which are present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual soak testing content. No references to detailed materials, examples, or configuration templates are provided. | 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.