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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill artillery-config-generatorActivation
22%This description is essentially a placeholder that relies entirely on the skill name rather than providing useful selection criteria. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The redundant trigger terms and boilerplate category mention add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Artillery YAML configuration files for load testing, including scenario definitions, target URLs, phases, and custom plugins.'
Include a 'Use when...' clause with natural trigger terms like 'load test config', 'artillery yaml', 'stress test setup', 'performance test configuration', or 'artillery scenarios'.
Remove the redundant trigger term listing and replace with varied, user-natural phrases that would indicate need for this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Artillery Config Generator') without describing any concrete actions. It doesn't explain what configurations are generated, what parameters can be set, or what outputs are produced. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a repetition of the skill name rather than explicit trigger scenarios. There's no 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | Includes 'artillery config generator' and 'Performance Testing' as keywords, but the trigger terms are redundantly listed twice and miss natural variations users might say like 'load test', 'stress test', 'artillery yaml', 'performance config', or 'artillery script'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Artillery' specifically helps distinguish it from generic performance testing tools, but 'Performance Testing' is broad enough to potentially conflict with other load testing or benchmarking skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains no Artillery-specific syntax, configuration examples, or actionable guidance. The entire content could apply to any generic skill and teaches Claude nothing about generating Artillery load testing configurations.
Suggestions
Add concrete Artillery YAML configuration examples showing scenarios, targets, phases, and assertions
Include a step-by-step workflow for generating configs: define target -> configure phases -> add scenarios -> validate -> run test
Provide specific Artillery CLI commands (e.g., `artillery run config.yml`, `artillery quick --count 10 -n 20 http://target`)
Remove generic boilerplate sections ('Purpose', 'Capabilities', 'Example Triggers') and replace with actual configuration patterns and common load testing scenarios
| 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 Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or examples of Artillery configuration syntax. The content describes what the skill does abstractly but provides zero executable guidance on how to actually generate Artillery configs. | 1 / 3 |
Workflow Clarity | No workflow steps are provided. There's no sequence for creating Artillery configs, no validation steps, and no guidance on the actual process of generating or testing configurations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed documentation, examples, or related files. No structure for discovering more specific 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.