gatling-scenario-creator
Gatling Scenario Creator - Auto-activating skill for Performance Testing. Triggers on: gatling scenario creator, gatling scenario creator Part of the Performance Testing skill category.
36
3%
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/gatling-scenario-creator/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 essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond the skill name repeated, and lacks any 'Use when...' guidance. It would be nearly indistinguishable from other performance testing skills and would not help Claude select it appropriately.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Gatling simulation scripts in Scala, configures HTTP protocols, defines user injection profiles, and sets up request chains for load testing.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Gatling simulations, load testing scripts, performance test scenarios, stress testing, .scala simulation files, or virtual user configuration.'
Remove the duplicate trigger term ('gatling scenario creator' is listed twice) and expand with varied natural language terms users might use such as 'load test', 'performance script', 'Gatling DSL', 'throughput test'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Gatling Scenario Creator', 'Performance Testing') but does not describe any concrete actions. There are no specific capabilities listed such as 'creates load test scripts', 'configures virtual users', or 'generates simulation files'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is limited to a redundant trigger phrase. There is no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'gatling scenario creator' repeated twice. Missing natural variations users would say like 'load test', 'performance test script', 'Gatling simulation', 'stress test', '.scala test', 'virtual users', or 'throughput testing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Gatling' provides some distinctiveness since it's a specific tool, but the generic 'Performance Testing' category label could overlap with other performance testing skills (e.g., JMeter, k6, Locust). The lack of specific actions makes it harder to distinguish. | 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 an empty shell with no actual content. It consists entirely of generic boilerplate that could apply to any topic—there is nothing specific to Gatling, scenario creation, or performance testing. It provides no actionable guidance, no code examples, no workflows, and no references to supplementary materials.
Suggestions
Add executable Gatling scenario examples using the Gatling DSL (Scala or Java), such as a basic HTTP load test with ramp-up users, request chains, and assertions.
Include a clear workflow: define scenario → configure injection profile → set assertions → run simulation → analyze results, with specific commands (e.g., `mvn gatling:test`).
Provide concrete code for common patterns like feeders (CSV data), checks (status codes, response times), and throttling configurations.
Remove all generic boilerplate sections (Purpose, When to Use, Example Triggers) and replace with actionable content that teaches Gatling-specific concepts Claude wouldn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'gatling scenario creator' excessively, and provides zero domain-specific information about Gatling or performance testing. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no Gatling DSL examples, no scenario definitions, no configuration snippets. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is described. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or advanced guides, and no meaningful structure beyond generic headings. | 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
3076d78
- 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.