artillery-config-generator
Artillery Config Generator - Auto-activating skill for Performance Testing. Triggers on: artillery config generator, artillery config generator Part of the Performance Testing skill category.
41
11%
Does it follow best practices?
Impact
98%
0.98xAverage 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/artillery-config-generator/SKILL.mdQuality
Discovery
22%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 a template-style placeholder that provides minimal useful information. It names the tool but fails to describe what actions it performs (e.g., generating YAML configs, defining scenarios, setting load patterns) and lacks explicit trigger guidance. The redundant trigger terms and category labeling add no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Artillery YAML configuration files for load testing, defines test scenarios, configures virtual users, and sets request patterns.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user needs to create load tests, stress tests, Artillery configs, or performance test scenarios.'
Include natural keyword variations users might say: 'load testing', 'stress test', 'artillery.yml', 'performance benchmarks', 'API load test'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Artillery Config Generator') without describing any concrete actions. It doesn't explain what generating a config involves or what capabilities it provides. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause. The 'Triggers on' section is redundant and doesn't provide meaningful guidance on when to use this skill. | 1 / 3 |
Trigger Term Quality | Includes 'artillery config generator' and 'Performance Testing' as keywords, but the trigger terms are redundantly duplicated and miss natural variations users might say like 'load testing', 'stress test', 'artillery yaml', or 'performance test config'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Artillery' specifically helps distinguish it from generic performance testing tools, but 'Performance Testing skill category' is vague and could overlap with other performance testing skills. | 2 / 3 |
Total | 6 / 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 Artillery config generation. It contains only generic boilerplate text that could apply to any skill, with no executable examples, no Artillery-specific syntax, no YAML config samples, and no actionable guidance whatsoever.
Suggestions
Add a concrete Artillery config YAML example showing a basic load test scenario with targets, phases, and scenarios
Include specific Artillery CLI commands (e.g., `artillery run config.yml`, `artillery quick --count 10 -n 20 https://example.com`)
Provide a step-by-step workflow: 1) Define target, 2) Configure phases, 3) Write scenarios, 4) Validate with `artillery validate`, 5) Run test
Add examples of common patterns like ramp-up phases, think time, payload files, and environment variable usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Artillery config generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or examples are provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate an Artillery config file or what one looks like. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content lists vague capabilities but provides no sequence for creating Artillery configs, no validation steps, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to example configs, and no links to Artillery documentation or related files. | 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.