spike-test-setup
Spike Test Setup - Auto-activating skill for Performance Testing. Triggers on: spike test setup, spike test setup Part of the Performance Testing skill category.
36
3%
Does it follow best practices?
Impact
100%
1.06xAverage 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/spike-test-setup/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, essentially just restating the skill name without explaining capabilities or providing meaningful selection guidance. It lacks concrete actions, has redundant and narrow trigger terms, and provides no context for when Claude should choose this skill over others in the Performance Testing category.
Suggestions
Add specific actions the skill performs, e.g., 'Configures spike test scenarios that simulate sudden traffic bursts, sets up load patterns with rapid user increases, and generates test scripts for tools like k6, JMeter, or Gatling.'
Include a proper 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to test system behavior under sudden load spikes, burst traffic scenarios, or rapid scaling conditions.'
Expand trigger terms to include natural variations: 'spike test', 'burst test', 'sudden load', 'traffic spike', 'rapid scaling test', 'flash crowd simulation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Spike Test Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'creates', 'configures', 'generates', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause with context. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('spike test setup' listed twice) and very narrow. Missing natural variations users might say like 'load testing', 'stress test', 'performance spike', 'burst traffic test', or tool-specific terms. | 1 / 3 |
Distinctiveness Conflict Risk | While 'spike test' is somewhat specific within performance testing, the lack of detail about what distinguishes this from other performance testing skills (load tests, stress tests, endurance tests) creates potential overlap within the category. | 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 content is entirely meta-description with no actual instructional value. It describes what the skill claims to do but provides zero concrete guidance on spike test setup - no k6/JMeter examples, no configuration patterns, no load profiles, and no actual steps. This is a placeholder template, not a functional skill.
Suggestions
Add concrete code examples for spike test setup using k6 or JMeter (e.g., a complete script showing sudden load increase pattern)
Include specific spike test configuration parameters: ramp-up time, peak duration, user counts, and typical spike patterns
Provide a clear workflow: 1) Define baseline, 2) Configure spike profile, 3) Set up monitoring, 4) Run test, 5) Analyze results
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual executable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are meaningless filler without actual content. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no commands, and no actual instructions for setting up spike tests. The entire content describes what the skill supposedly does rather than providing any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for spike test setup. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, no examples, and no organized sections with actual content to navigate. | 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
e9f9c93
- 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.