locust-test-creator
Locust Test Creator - Auto-activating skill for Performance Testing. Triggers on: locust test creator, locust test creator Part of the Performance Testing skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill locust-test-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 it. The only distinguishing element is the specific mention of 'Locust' which hints at the Python load testing framework.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Locust load test scripts, defines user behavior classes, configures test parameters for simulating concurrent users'
Include a 'Use when...' clause with natural trigger terms like 'load testing', 'stress test', 'performance test', 'simulate users', 'locustfile', 'concurrent requests'
Remove the duplicate trigger term and expand with variations users would naturally say when needing performance/load testing help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Locust Test Creator') and category ('Performance Testing') without describing any concrete actions. No specific capabilities like 'create load tests', 'simulate users', or 'generate test scripts' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'locust test creator' repeated twice. Missing natural variations users would say like 'load testing', 'performance test', 'stress test', 'locustfile', or 'simulate traffic'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Locust' specifically (a Python load testing framework) provides some distinctiveness from generic testing skills, but 'Performance Testing' is broad enough to potentially conflict with other performance-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty placeholder with no actual instructional content. It describes what a Locust test creator skill would do in abstract marketing language but provides zero actionable guidance - no code examples, no commands, no workflows, no concrete instructions of any kind. It fails every dimension of the rubric.
Suggestions
Add executable Python code showing a basic Locust test file (locustfile.py) with a simple user class and task
Include concrete CLI commands for running Locust tests (e.g., `locust -f locustfile.py --host=http://example.com`)
Provide a clear workflow: 1) Create locustfile.py, 2) Define user behavior, 3) Run test, 4) Analyze results
Add specific examples of common patterns like sequential tasks, wait times, and assertions for performance thresholds
| 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 actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance whatsoever. The skill describes what it does in abstract terms but provides zero actual instructions for creating Locust tests - no Python code, no locustfile examples, no CLI commands. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content merely lists vague 'capabilities' without explaining how to actually perform any task. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to examples or advanced topics. The content is both shallow and poorly organized with no path to deeper information. | 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.