stress-test-config
Stress Test Config - Auto-activating skill for Performance Testing. Triggers on: stress test config, stress test config Part of the Performance Testing skill category.
41
11%
Does it follow best practices?
Impact
100%
1.00xAverage 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/stress-test-config/SKILL.mdQuality
Discovery
22%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 extremely thin and formulaic, providing almost no information about what the skill actually does. It relies on a repeated trigger term and a category label without describing any concrete actions or explicit usage guidance. It would be very difficult for Claude to confidently select this skill over alternatives based on this description alone.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates stress test configuration files, defines load profiles, sets concurrency levels and ramp-up parameters.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create or modify stress test configs, load test setups, performance benchmarks, or throughput testing parameters.'
Remove the redundant duplicate trigger term and expand with natural variations users might say, such as 'load testing config', 'performance test configuration', 'stress testing setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only states it is for 'Performance Testing' and mentions 'stress test config' but never describes what it actually does (e.g., generate config files, validate parameters, run load tests). | 1 / 3 |
Completeness | The 'what' is essentially missing—there is no explanation of what the skill does beyond naming its category. The 'when' is weakly implied by 'Triggers on: stress test config' but there is no explicit 'Use when...' clause with meaningful guidance. | 1 / 3 |
Trigger Term Quality | It includes 'stress test config' as a trigger term, which is somewhat relevant, but the trigger is repeated verbatim and lacks natural variations users might say (e.g., 'load test configuration', 'performance test setup', 'stress testing', '.yaml config'). | 2 / 3 |
Distinctiveness Conflict Risk | The term 'stress test config' is fairly specific and unlikely to conflict with many other skills, but the lack of concrete capability descriptions means it could overlap with other performance testing skills without clear differentiation. | 2 / 3 |
Total | 6 / 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 a placeholder with no substantive content. It contains only generic meta-descriptions of what the skill could do, without any actual instructions, code, configuration examples, or workflows for stress test configuration. It provides no value beyond what the skill's title and description already convey.
Suggestions
Add concrete, executable examples of stress test configurations (e.g., a complete k6 script or JMeter config snippet with specific parameters like ramp-up, duration, virtual users, and thresholds).
Define a clear workflow: e.g., 1) Identify target endpoints, 2) Configure load profile, 3) Set thresholds/assertions, 4) Run test, 5) Validate results against thresholds.
Remove all generic filler ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual best practices (e.g., 'Start at 10% of expected peak, ramp to 150% over 10 minutes, hold for 5 minutes').
Add references to detailed files for advanced topics (e.g., 'See K6_EXAMPLES.md for distributed load testing patterns' or 'See THRESHOLDS.md for SLA-based pass/fail criteria').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing it doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. There is no actual technical content—every token is wasted on meta-description rather than instruction. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no configuration examples, no specific tools or parameters. The skill describes what it could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. There are no validation checkpoints or error-handling instructions. The bullet 'Provides step-by-step guidance' is ironic given that no steps are actually included. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. The 'Related Skills' section names a category but links to nothing. | 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
3e83543
- 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.