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 fails to communicate what the skill actually does beyond its name. It lacks any concrete actions, meaningful trigger term variety, or explicit 'when to use' guidance. The repetitive trigger term and boilerplate structure suggest auto-generated content with no human refinement.
Suggestions
Add specific concrete actions the skill performs, 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 needs to create or modify stress test configs, load test setups, performance benchmarking configurations, or .yaml/.json test profiles.'
Remove the duplicated trigger term ('stress test config' is listed twice) and expand with natural variations like 'load testing config', 'performance test setup', 'stress testing parameters'.
| 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 does this do' is essentially absent—there are no described capabilities beyond the name. 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 vague 'Performance Testing' category label could overlap with other performance-related skills without clearer differentiation of what this skill specifically handles. | 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 an empty shell with no substantive content. It contains only meta-descriptions of what it claims to do (stress test configuration) without any actual instructions, code examples, tool-specific guidance, or configuration templates. It provides no value beyond what Claude could infer from the skill's title alone.
Suggestions
Add concrete, executable configuration examples for at least one stress testing tool (e.g., a k6 script or JMeter test plan XML) with specific parameters like virtual users, ramp-up periods, and duration.
Define a clear workflow: e.g., 1) Define test objectives → 2) Configure load profile → 3) Set thresholds → 4) Run test → 5) Validate results against thresholds, with explicit validation checkpoints.
Remove all meta-description content ('This skill provides...', 'When to Use', 'Example Triggers') and replace with actionable reference material such as common stress test patterns, threshold configurations, and example outputs.
Include at least one complete, copy-paste-ready stress test configuration file (e.g., a k6 options block or a JMeter .jmx snippet) with annotations on key parameters to tune.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. The entire file explains what the skill is rather than providing any actual instruction or knowledge. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific stress test parameters, no tool usage. The content describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, no validation checkpoints, and no actual procedure for configuring a stress test. The skill merely claims it 'provides step-by-step guidance' without providing any. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external documents, and the content itself is a shallow placeholder with no structured information to disclose progressively. There is nothing to navigate to or from. | 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
3efb53b
- 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.