arn-infra-change-plan
This skill should be used when the user says "plan infra change", "arn-infra-change-plan", "infra change plan", "plan this infrastructure change", "create infra plan", "arn infra plan", "plan the infra spec", "infrastructure implementation plan", "infra plan from spec", "generate infra plan", "plan infrastructure", or wants to generate a phased implementation plan from an infrastructure change specification, structured by provisioning order, blast radius, rollback checkpoints, and environment promotion gates.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 a strong skill description that clearly defines its purpose, provides extensive trigger phrases, and specifies the structural output format. The description effectively communicates both when to use the skill and what it produces, with domain-specific terminology that makes it highly distinctive. Minor weakness is that the long list of trigger phrases at the beginning makes it slightly harder to parse the core capability quickly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions and structural elements: 'generate a phased implementation plan from an infrastructure change specification, structured by provisioning order, blast radius, rollback checkpoints, and environment promotion gates.' These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | The description clearly answers both 'what' (generate a phased implementation plan structured by provisioning order, blast radius, rollback checkpoints, and environment promotion gates) and 'when' (explicit trigger phrases and the condition 'when the user wants to generate a phased implementation plan from an infrastructure change specification'). | 3 / 3 |
Trigger Term Quality | The description includes an extensive list of natural trigger phrases users would say, covering many variations: 'plan infra change', 'create infra plan', 'infrastructure implementation plan', 'plan infrastructure', etc. Good coverage of both abbreviated ('infra') and full ('infrastructure') forms. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very specific niche: infrastructure change planning from specifications with particular structural elements (provisioning order, blast radius, rollback checkpoints, environment promotion gates). The custom trigger terms like 'arn-infra-change-plan' further reduce conflict risk. Unlikely to overlap with generic infrastructure or planning skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflow sequencing, explicit validation checkpoints, and thorough error handling. Its main weakness is length — the inline agent prompt templates and experience-level presentation formats add bulk that could be extracted into reference files. The skill demonstrates strong infrastructure domain knowledge with appropriate ordering concepts (provisioning dependency, blast radius, rollback checkpoints).
Suggestions
Extract the agent invocation prompt templates (Step 3 and Step 4b) into a reference file to reduce the main skill's token footprint.
Consider moving the experience-level presentation formats (Expert/Intermediate/Beginner) into a shared reference file, as these likely repeat across multiple skills in the pipeline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~200 lines) with some verbosity, particularly in the agent invocation prompt templates which are repeated twice with slight variations. The experience-level presentation formats and error handling are thorough but could be more compact. However, it avoids explaining basic concepts Claude already knows and most content is genuinely instructive. | 2 / 3 |
Actionability | The skill provides highly concrete, step-by-step guidance with specific file paths, exact naming conventions (PLAN_PREVIEW_INFRA_<spec-name>.md), precise agent invocation templates, specific user prompts to use, and detailed file lookup logic with fallback chains. Every step tells Claude exactly what to do. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 steps with explicit validation checkpoints: checking for existing plans before regenerating, a feedback loop (Step 4 -> 4b -> back to 4) for iterative refinement, explicit approval gates before proceeding, and comprehensive error handling with recovery paths for each failure mode. | 3 / 3 |
Progressive Disclosure | The skill references external files (blast-radius-guide.md, experience-derivation.md, ensure-config.md, agent-models/infra.md) with clear paths, which is good. However, no bundle files were provided to verify these references, and the skill itself is quite long — the agent prompt templates and experience-level presentation formats could potentially be extracted into reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 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.