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.
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/locust-test-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, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The only distinguishing element is the specific tool name 'Locust', but this alone is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific concrete actions like 'Creates Locust load test scripts, defines user behavior scenarios, configures test parameters for simulating concurrent users'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about load testing, stress testing, performance benchmarks, simulating user traffic, or mentions Locust/locustfile'
Expand trigger terms to include variations users would naturally say: 'load test', 'stress test', 'performance test', 'concurrent users', 'locustfile', '.py test scripts'
| 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 the name, and has no 'Use when...' clause or explicit trigger guidance. Both the what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('locust test creator' repeated twice) and miss 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' (a specific tool) 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%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder template with no actual content about Locust test creation. It contains only generic boilerplate text that could apply to any skill, with zero Locust-specific code, commands, patterns, or actionable guidance. The skill fails to teach Claude anything it doesn't already know.
Suggestions
Add executable Locust code examples showing basic test structure (e.g., a complete locustfile.py with @task decorators, HttpUser class, wait_time)
Include concrete commands for running Locust tests (e.g., 'locust -f locustfile.py --host=http://example.com --users 100 --spawn-rate 10')
Provide a clear workflow for creating load tests: define user behavior -> configure load parameters -> run test -> analyze results
Add specific patterns for common scenarios like API testing, authenticated requests, and custom load shapes with actual code snippets
| 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 | There is zero concrete guidance - no code examples, no Locust-specific syntax, no actual commands or configurations. The skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content merely lists vague 'capabilities' without any process for creating Locust tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to examples or advanced topics, and no useful organization for discovery. | 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.