Name: arn-infra-env
Rating: 74.4 (1 reviews)
Author: AppsVortex

arn-infra-env

This skill should be used when the user says "manage environments", "arn infra env", "infra env", "environment setup", "configure environments", "set up staging", "set up production", "environment management", "create environment", "environment promotion", "promote to staging", "promote to production", "environment isolation", "configure dev staging prod", "environment-specific config", "tfvars per environment", "arn-infra-env", or wants to configure, create, or manage infrastructure environments (dev/staging/production) with isolation strategies, variable overrides, and promotion rules.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable 7-step workflow with concrete IaC-tool guidance, real one-level-deep reference files, and explicit verification for destructive overwrites. Its only weakness is token efficiency: repeated experience-tier prose and verbatim prompt templates across steps could be consolidated.

Suggestions

Consolidate the repeated Expert/Intermediate/Beginner branching into a single shared helper or table referenced from Steps 2, 3, and 5, instead of restating the three-tier prose in each step.

Shorten the verbatim AskUserQuestion prompt text (e.g. Step 1's 'What would you like to do?' / 'Which task?') to the essential question and rely on the Options list, removing redundant quoting.

Trim the lengthy INSTRUCTIONS block in Step 4 to the rules that are not already implied by the ENVIRONMENT CONTEXT template, since several items (e.g. include variable overrides, environment-specific tags) duplicate the context fields above.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the Expert/Intermediate/Beginner branching prose is repeated nearly verbatim across Steps 2, 3, and 5, and AskUserQuestion prompt text is quoted in full multiple times — efficient yet could be tightened, matching the 2-anchor rather than the every-token-earns-its-place 3-anchor.	2 / 3
Actionability	Provides a concrete per-IaC-tool config table with file paths and example values (`environments/<env>.tfvars`, `instance_type = "t3.small"`, `Pulumi.<env>.yaml`), explicit specialist-agent dispatch with a model parameter, and a copy-ready structured context template — fully executable guidance at the 3-anchor.	3 / 3
Workflow Clarity	A clearly sequenced 7-step workflow with decision-point pauses, current-state presentation, and verification/recovery for risky overwrites ("Existing config files are shown in a diff before overwriting", retry-on-empty-output, fallback patterns), satisfying the validation-checkpoint 3-anchor and avoiding the destructive-operation cap.	3 / 3
Progressive Disclosure	The SKILL.md body is an overview workflow that points one level deep to clearly signaled reference files (`environment-patterns.md`, `promotion-patterns.md`), both of which exist in ./references/ — content appropriately split with easy navigation, matching the 3-anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong activation driver: it pairs an explicit 'should be used when' trigger clause with a wide set of natural user phrasings and a concrete capability list scoped to a distinct infrastructure-environment niche. It uses third-person voice and avoids vague fluff, so no anchor penalties apply.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "configure, create, or manage infrastructure environments (dev/staging/production) with isolation strategies, variable overrides, and promotion rules" — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what (configure/create/manage envs with isolation, overrides, promotion) and when ("This skill should be used when the user says ... or wants to ..."), satisfying the explicit-trigger 3-anchor rather than the implied-when 2-anchor.	3 / 3
Trigger Term Quality	Dense coverage of natural phrasings users would actually say ("manage environments", "set up staging", "promote to production", "tfvars per environment", "arn-infra-env"), matching the good-coverage anchor; not the sparse 2-anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — infra environment management with tooling-specific signals (tfvars, arn-infra-env) — making accidental activation by unrelated skills unlikely, matching the distinct-niche 3-anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AppsVortex/arness
Path: plugins/arn-infra/skills/arn-infra-env/SKILL.md
Commit: 7f87870

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.