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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill gatling-scenario-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger terms and boilerplate structure suggest this is a template that was never properly filled out.
Suggestions
Add specific capabilities: describe what the skill actually does (e.g., 'Creates Gatling simulation scripts, defines user scenarios, configures load profiles, and generates Scala-based performance tests').
Add a 'Use when...' clause with natural trigger terms like 'load testing', 'performance testing', 'stress test', 'simulate concurrent users', 'Gatling script', or 'Scala simulation'.
Remove the redundant trigger term and expand to include variations users would naturally say when needing this skill.
| 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 provides no 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 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' specifically provides some distinctiveness from generic performance testing tools, but the lack of specific capabilities means it could still conflict with other performance testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual Gatling-specific content. It contains no executable code, no scenario examples, no DSL syntax, and no concrete guidance for creating performance test scenarios. The entire content could apply to any skill by changing the name.
Suggestions
Add concrete Gatling Scala DSL examples showing how to create HTTP scenarios, define user injection profiles, and set up assertions
Include a step-by-step workflow: 1) Define HTTP protocol, 2) Create scenario with requests, 3) Configure injection profile, 4) Add assertions, 5) Run simulation
Provide copy-paste ready code for common patterns like ramping users, constant throughput, and response time validation
Remove all generic boilerplate text and replace with Gatling-specific configuration examples and command-line usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual Gatling-specific information. | 1 / 3 |
Actionability | There is zero concrete guidance - no Gatling code, no scenario examples, no DSL syntax, no executable commands. The skill describes what it could do rather than providing any actual instructions for creating Gatling scenarios. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Creating Gatling scenarios involves specific steps (defining protocols, scenarios, simulations, assertions) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers that contain no useful content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.