arn-infra-define
This skill should be used when the user says "define infrastructure", "generate IaC", "infra define", "arn infra define", "generate terraform", "generate opentofu", "generate pulumi", "generate cdk", "generate bicep", "create kubernetes manifests", "provision cloud resources", "create IaC", "infrastructure as code", or wants to generate infrastructure-as-code in their chosen IaC tool for configured cloud provider(s). It produces provider-specific infrastructure code, validates it through a multi-level validation ladder, and writes an infrastructure architecture spec.
62
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/arn-infra/skills/arn-infra-define/SKILL.mdQuality
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 excels in trigger term coverage and completeness. It clearly defines what the skill does and provides an extensive list of explicit trigger phrases that users would naturally use. The only minor weakness is that the description leads with the 'when' clause rather than the 'what' clause, which slightly reduces readability, but all essential information is present.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'produces provider-specific infrastructure code', 'validates it through a multi-level validation ladder', and 'writes an infrastructure architecture spec'. These are concrete, actionable outputs. | 3 / 3 |
Completeness | Clearly answers both 'what' (produces provider-specific infrastructure code, validates through multi-level validation, writes architecture spec) and 'when' (explicit list of trigger phrases plus the general condition 'wants to generate infrastructure-as-code in their chosen IaC tool'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'define infrastructure', 'generate IaC', 'generate terraform', 'generate opentofu', 'generate pulumi', 'generate cdk', 'generate bicep', 'create kubernetes manifests', 'provision cloud resources', 'infrastructure as code'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around infrastructure-as-code generation. The specific tool names (Terraform, OpenTofu, Pulumi, CDK, Bicep) and domain-specific triggers make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 error handling, but it suffers significantly from verbosity. The 9-step workflow with validation ladder and error recovery is well-designed, but the content could be compressed by 50-60% without losing actionable information. Many sections repeat patterns (agent invocation boilerplate) and include explanatory text that Claude doesn't need.
Suggestions
Compress agent invocation blocks into a single reusable template pattern referenced once, rather than repeating the full context-passing structure for both the specialist and cost-analyst agents.
Remove explanatory prose that describes what each step 'does' conceptually and keep only the concrete instructions — e.g., 'This step is skipped if a triage brief was found in Step 2' can be expressed as a simple conditional without the narrative framing.
Convert the placeholder-heavy context templates (e.g., `--- APPLICATION CONTEXT ---`) into a concise schema or table format that takes fewer tokens while conveying the same structure.
Move the detailed error handling section into a separate reference file (e.g., `error-handling.md`) and keep only a brief summary inline, since the error handling alone accounts for ~25% of the document.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It over-explains workflows that Claude can infer, repeats agent invocation patterns multiple times with nearly identical boilerplate, includes lengthy template blocks for context passing, and explains concepts like 'what a monorepo is' or 'what environments are' that Claude already knows. Many sections could be compressed to a fraction of their size. | 1 / 3 |
Actionability | The skill provides specific tool commands (e.g., `tofu validate`, `cdk synth`, `kubectl apply --dry-run=client`) and clear file paths, but much of the guidance is procedural description rather than executable code. The agent invocation blocks are template-like but not truly copy-paste ready — they use placeholder syntax like `[list of services with roles]` extensively. No actual executable code examples are provided. | 2 / 3 |
Workflow Clarity | The 9-step workflow is clearly sequenced with explicit validation checkpoints (the validation ladder in Step 6), feedback loops for error recovery (auto-fix and re-validate), conditional branching (triage brief exists vs. doesn't), and a comprehensive error handling section. Destructive operations (overwriting files) require user approval with diff display. | 3 / 3 |
Progressive Disclosure | The skill references many external files (paas-config-patterns.md, opentofu-patterns.md, validation-ladder.md, infra-architecture-template.md, etc.) which is good progressive disclosure design, but no bundle files were provided to verify these exist. The SKILL.md itself is monolithic — the entire 9-step workflow plus error handling is inline rather than splitting detailed reference material into separate files. The references are one-level deep and clearly signaled, which is positive. | 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.