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
Quality
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 severely underdeveloped, functioning more as a label than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The redundant trigger term and absence of natural user language make it unlikely to be selected appropriately.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Gatling simulation scripts, defines user scenarios, configures load profiles, and generates performance test code in Scala.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to create load tests, write Gatling scripts, simulate concurrent users, or set up performance testing scenarios.'
Include common variations users might say: 'load testing', 'stress test', 'Scala simulation', 'virtual users', 'throughput testing', '.scala test files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Gatling Scenario Creator') and category ('Performance Testing') without describing any concrete actions. No specific capabilities like 'create load tests', 'simulate user traffic', or 'generate performance reports' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('gatling scenario creator' listed twice) and overly specific. Missing natural variations users might say like 'load test', 'performance test', 'stress test', 'simulate users', or 'Gatling script'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Gatling' provides some specificity to distinguish from generic performance testing tools, but 'Performance Testing' category is broad and could overlap with other load testing or benchmarking 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 template with no actual instructional content. It describes what a Gatling scenario creator skill would do but provides zero actionable guidance, code examples, or workflow steps. The content fails to teach Claude anything about Gatling's DSL, scenario structure, or performance testing patterns.
Suggestions
Add executable Gatling scenario code examples in Scala showing basic HTTP requests, feeders, and assertions
Include a clear workflow for creating scenarios: define protocol -> create scenario -> set up injection profile -> configure assertions -> run simulation
Provide concrete DSL patterns like `scenario("name").exec(http("request").get("/endpoint")).inject(rampUsers(100).during(60))`
Remove generic boilerplate sections (Purpose, Capabilities, Example Triggers) and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Gatling. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly but never shows how to actually create a Gatling scenario - no Scala/Java code, no DSL examples, no configuration snippets. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no sequences, validation checkpoints, or process flows for creating Gatling scenarios. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. No references to example files, API documentation, or advanced topics 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
0c08951
- 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.