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.
36
3%
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
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 extremely weak, essentially just restating the skill name with no actionable detail. It lacks concrete capabilities, natural trigger terms, and any 'Use when...' guidance. The only slight positive is that 'Artillery' is a specific enough tool name to provide minimal distinctiveness.
Suggestions
Add specific concrete actions like 'Generates Artillery YAML configuration files for load testing, including scenario definitions, load phases, virtual user counts, and target endpoint configuration'.
Add a 'Use when...' clause with natural trigger terms such as 'Use when the user needs to create Artillery load test configs, set up performance tests, define stress test scenarios, or generate .yml files for Artillery'.
Remove the duplicate trigger term ('artillery config generator' is listed twice) and expand with user-natural variations like 'load test config', 'performance testing setup', 'Artillery YAML', 'stress test configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Artillery Config Generator', 'Performance Testing') but does not describe any concrete actions. There are no specific capabilities listed like 'generates YAML configs', 'defines load phases', or 'configures virtual users'. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the name 'Artillery Config Generator') and the 'when' is missing entirely. There is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('artillery config generator, artillery config generator'). Missing natural user terms like 'load test', 'performance test config', 'artillery YAML', 'stress test', '.yml config', or 'load testing setup'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Artillery' specifically (a named tool) provides some distinctiveness from generic performance testing skills, but the lack of detail about what it actually generates or when to use it could cause overlap with other performance testing or config generation 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 with no substantive content. It contains no executable code, no Artillery configuration examples, no workflow steps, and no actionable guidance whatsoever. Every section restates the skill name without teaching Claude anything it doesn't already know.
Suggestions
Add a concrete, copy-paste-ready Artillery YAML configuration example (e.g., a basic load test config with phases, targets, and scenarios) as the core of the skill.
Include a clear workflow: 1) Define target URL, 2) Configure load phases, 3) Add scenarios/requests, 4) Validate config with `artillery validate config.yml`, 5) Run with `artillery run config.yml`.
Remove the generic 'When to Use', 'Example Triggers', and 'Capabilities' sections—these waste tokens and provide no value to Claude.
Add examples for common patterns (ramp-up load, stress test, spike test) with specific YAML snippets showing phase configurations and thresholds.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Sections like 'When to Use', 'Example Triggers', and 'Capabilities' restate the title and description without adding actionable information. It explains obvious concepts Claude already knows. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no Artillery YAML snippets. The skill describes what it could do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. There are no validation checkpoints or any process to follow for generating an Artillery configuration. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. | 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
3076d78
- 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.