Convert existing Artillery YAML scripts to TypeScript or ESM JavaScript, auto-detecting the best output format, resolving YAML anchors by inlining, type-annotating exports, and verifying the output via tsc or node --check. Use when the user wants to migrate, rewrite, or translate Artillery load-test scripts from YAML to TS/JS for better IDE support, type checking, and composability.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%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 is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and carves out a distinct niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Convert existing Artillery YAML scripts to TypeScript or ESM JavaScript', 'auto-detecting the best output format', 'resolving YAML anchors by inlining', 'type-annotating exports', and 'verifying the output via tsc or node --check'. | 3 / 3 |
Completeness | Clearly answers both what (convert Artillery YAML to TS/JS with specific processing steps) AND when (explicit 'Use when the user wants to migrate, rewrite, or translate Artillery load-test scripts from YAML to TS/JS'). | 3 / 3 |
Trigger Term Quality | Includes excellent natural keywords users would say: 'Artillery', 'YAML', 'TypeScript', 'TS/JS', 'migrate', 'rewrite', 'translate', 'load-test scripts', plus mentions benefits like 'IDE support', 'type checking', 'composability'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically targets Artillery load-testing framework YAML-to-TypeScript conversion. Unlikely to conflict with general YAML or TypeScript skills due to the specific domain focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides clear, actionable guidance for converting Artillery YAML to TypeScript/JS. It excels at workflow clarity with explicit decision points, handles edge cases (YAML anchors), includes verification steps, and provides concrete executable examples. The structure is logical and the content is appropriately concise.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Artillery or YAML is. | 3 / 3 |
Actionability | Provides fully executable guidance with concrete code examples, specific file patterns to glob, exact commands to run (npx tsc, node --check), and a complete before/after conversion example that is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit decision points marked, verification steps for both TS and JS outputs, and proper handling of edge cases (YAML anchors). The workflow includes validation before completion. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and appropriate depth for a self-contained skill. The content is appropriately structured with headers, and the complexity level doesn't warrant external file references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
78a9dbe
Table of Contents
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.