arn-infra-wizard
This skill should be used when the user says "infra wizard", "arn infra wizard", "guided infra", "walk me through infrastructure", "infrastructure pipeline", "full infra pipeline", "infra flow", "run the infra pipeline", "guide me through infrastructure", "infra guided mode", "infrastructure wizard", "end to end infrastructure", "deploy everything", "set up my infrastructure", "infra start to finish", "arn infra guided", "run infra wizard", "set up everything", "complete infra setup", or wants to be walked through the entire Arness infrastructure pipeline in a single continuous session with guided decision gates instead of invoking each skill manually.
48
51%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/arn-infra/skills/arn-infra-wizard/SKILL.mdQuality
Discovery
54%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 heavily weighted toward trigger terms at the expense of explaining what the skill actually does. While it excels at listing activation phrases, it fails to describe any concrete capabilities, steps, or actions involved in the infrastructure pipeline. A user or Claude selecting this skill would know when to use it but not what it will accomplish.
Suggestions
Add specific actions the skill performs, e.g., 'Walks through provisioning VPCs, configuring security groups, deploying services, and setting up DNS in a guided sequence with decision gates at each step.'
Restructure to lead with a clear 'what it does' statement before the trigger phrases, e.g., 'Orchestrates the complete Arness infrastructure pipeline including [specific steps]. Use when...'
Trim the trigger phrase list to the most distinctive 5-7 phrases and use the saved space to describe the pipeline stages and what 'guided decision gates' means in practice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions or capabilities. It only mentions 'the entire Arness infrastructure pipeline' and 'guided decision gates' without specifying what steps, tools, or actions are involved. There are no specific operations like 'provision VPCs', 'deploy containers', or 'configure DNS'. | 1 / 3 |
Completeness | The 'when' is thoroughly covered with explicit trigger phrases and conditions. However, the 'what' is extremely weak — it only vaguely references 'the entire Arness infrastructure pipeline' and 'guided decision gates' without explaining what the skill actually does, what steps it performs, or what infrastructure components are involved. | 2 / 3 |
Trigger Term Quality | The description includes an extensive list of natural trigger phrases users might say, covering many variations like 'infra wizard', 'deploy everything', 'set up my infrastructure', 'walk me through infrastructure', and more. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Arness' and 'arn' prefixes provide some distinctiveness, and the wizard/guided mode framing differentiates it from individual infrastructure skills. However, generic phrases like 'deploy everything' and 'set up my infrastructure' could overlap with other deployment or infrastructure skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive orchestration skill with excellent workflow clarity and thorough error handling, but it suffers significantly from verbosity. The ~350+ line body repeats progress bar formats for every step, exhaustively enumerates error scenarios that could be condensed into a pattern, and includes explanatory text that Claude doesn't need. The progressive disclosure structure is reasonable in design but cannot be verified without bundle files, and the skill itself is too long for what is essentially a sequencer.
Suggestions
Reduce verbosity by consolidating repeated progress bar formats into a single template (e.g., 'Show progress with current step highlighted using the format from Step 2') instead of repeating the ASCII art for every step.
Condense the error handling section into a general pattern ('On sub-skill failure: present error, offer retry/skip/abort') with a small table of skill-specific notes, rather than enumerating every possible failure individually.
Move the Interactive-to-Pipeline Upgrade Path and Expertise-Adaptive Pipeline sections into reference files since they are detailed sub-flows, keeping only a one-line summary and pointer in the main SKILL.md.
Provide the referenced bundle files (decision-gates.md, entry-modes.md, artifact-detection.md, full-pipeline-flow.md) or inline the critical decision gate questions so the skill is actionable without external dependencies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines with significant repetition. Progress bar formats are repeated for every step, error handling enumerates every conceivable failure scenario in exhaustive detail, and the mode selection/entry mode detection sections contain lengthy explanations that could be condensed dramatically. Much of this content (like explaining what 'Fresh/Resume' means or how to present options) is something Claude can infer. | 1 / 3 |
Actionability | The skill provides concrete sequencing instructions and specific skill invocation names (e.g., `Skill: arn-infra:arn-infra-discover`), which is good. However, it heavily delegates to external reference files (decision-gates.md, entry-modes.md, artifact-detection.md, full-pipeline-flow.md) without providing their content, and the actual decision gate questions (Q1-Q7) are never shown inline — just referenced. The wizard logic itself is clear but incomplete without the bundle files. | 2 / 3 |
Workflow Clarity | The multi-step workflow is exceptionally well-sequenced with numbered steps, clear decision gates (Q1-Q7 for Quick mode, P1-P6 for Full Pipeline), explicit validation/error handling at each stage, resume/retry logic, and visual progress indicators. The error handling section covers failure recovery for every sub-skill with explicit options (retry/skip/abort), forming proper feedback loops. | 3 / 3 |
Progressive Disclosure | The skill references several external files (entry-modes.md, decision-gates.md, artifact-detection.md, full-pipeline-flow.md, step-0-fast-path.md, experience-derivation.md) which is good progressive disclosure design. However, no bundle files were provided, making it impossible to verify these references exist or are accurate. Additionally, the SKILL.md itself is monolithic — the inline content is very long and could benefit from moving more content (like the detailed error handling catalog or the upgrade path logic) into reference files. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- AppsVortex/arness
- Commit
b9084b6
- 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.