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 extremely thin and formulaic, appearing to be auto-generated boilerplate rather than a thoughtfully crafted skill description. It fails to explain what concrete actions the skill performs, provides no meaningful trigger terms beyond the skill name repeated, and lacks any explicit 'Use when...' guidance that would help Claude distinguish it from other skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates spike test scripts that simulate sudden traffic surges, configures ramp-up/ramp-down patterns, and sets virtual user thresholds for tools like k6, JMeter, or Gatling.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about spike testing, sudden load simulation, burst traffic patterns, rapid user ramp-up, or stress testing with sharp traffic spikes.'
Remove the duplicate trigger term ('spike test setup' is listed twice) and expand with natural variations users might say, such as 'spike scenario', 'sudden load test', 'traffic burst test', or 'peak load simulation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('spike test setup' and 'Performance Testing') but does not describe any concrete actions. There are no verbs indicating what the skill actually does—no 'generates', 'configures', 'creates', etc. | 1 / 3 |
Completeness | The description barely addresses 'what' (spike test setup, but no specifics on what actions are performed) and the 'when' clause is essentially just restating the skill name as a trigger rather than providing meaningful guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'spike test setup' repeated twice. There are no natural variations a user might say, such as 'load spike', 'burst test', 'stress test', 'sudden traffic', 'spike scenario', or tool-specific terms like 'k6', 'JMeter', 'Gatling'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'spike test' is somewhat specific within performance testing, which gives it some distinctiveness. However, the vague framing and mention of the broad 'Performance Testing' category could cause overlap with other performance testing 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 a placeholder or template with no substantive content. It describes what the skill would do in abstract terms but provides zero actionable guidance, no code examples, no tool-specific instructions (e.g., k6 or JMeter spike test configurations), and no workflow for actually setting up a spike test. It fails on every dimension of the rubric.
Suggestions
Replace the meta-description sections with actual spike test setup instructions, including executable code examples for at least one tool (e.g., a k6 script with a spike load profile showing rapid ramp-up and ramp-down stages).
Add a clear multi-step workflow: 1) Choose tool, 2) Define spike profile (baseline → spike → recovery), 3) Configure thresholds, 4) Run test, 5) Validate results against thresholds.
Include a concrete, copy-paste-ready example configuration (e.g., k6 `options.stages` with spike pattern or JMeter thread group XML) with expected output interpretation.
Remove all 'When to Use', 'Example Triggers', and 'Capabilities' sections—these are YAML frontmatter concerns, not body content, and waste tokens describing the skill rather than teaching it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section describes rather than instructs, wasting tokens on information Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific steps for setting up a spike test. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are promises without delivery. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Setting up a spike test is inherently a multi-step process (choosing a tool, configuring load profiles, defining ramp-up/spike patterns, running, validating results), yet none of these steps are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic description with no meaningful structure. Sections like 'Capabilities' and 'Example Triggers' are meta-information about the skill rather than organized technical content. No references to detailed resources or examples are provided. | 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.