CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-change-spec

This skill should be used when the user says "infra change spec", "infrastructure change", "specify infrastructure change", "change spec", "arn infra spec", "describe infra change", "what infrastructure needs to change", "infra spec", "spec this infra change", "write infra spec", "infrastructure change specification", "create infra change spec", "upgrade to pipeline", "convert to pipeline", or wants to iteratively develop an infrastructure change idea into a well-formed specification through guided conversation, or wants to upgrade existing interactive IaC artifacts into the structured change pipeline.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A well-structured, highly actionable conversational workflow with clear sequencing, validation checkpoints, and clean progressive disclosure into real reference files. The main area for improvement is tightening the per-level prompt lists and parallel agent blocks to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient procedural prose with no explaining of concepts Claude already knows, but the per-experience-level prompt-question lists and two fully-spelled-out parallel agent-invocation blocks could be tightened without losing meaning.

2 / 3

Actionability

Concrete prompts, exact file paths, structured agent-invocation templates with labeled context blocks, specific user-facing error messages, and a mkdir command give copy-ready, executable guidance throughout.

3 / 3

Workflow Clarity

Steps 1–6 are explicitly sequenced with branching (upgrade vs. fresh), readiness checks, an iterative refine/re-invoke feedback loop, and an overwrite confirmation checkpoint via AskUserQuestion for the file write.

3 / 3

Progressive Disclosure

The body is an overview that points to one-level-deep, clearly signaled references (blockquoted 'Read' callouts to infra-change-spec-template.md and blast-radius-guide.md, both present in ./references/), keeping detail offloaded rather than inline.

3 / 3

Total

11

/

12

Passed

Description

90%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 trigger-rich and clearly signals both purpose and invocation conditions, with a distinctive infra-spec niche. Its only weakness is that the 'what' is stated as two slightly abstract action clauses rather than a crisp enumerated set of concrete operations.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('iteratively develop an infrastructure change idea into a well-formed specification' and 'upgrade existing interactive IaC artifacts into the structured change pipeline'), but these are phrased somewhat abstractly rather than as a crisp list of distinct operations, so it stops short of the multi-action score-3 anchor.

2 / 3

Completeness

Explicitly answers both what (develop a change idea into a specification; upgrade IaC artifacts into the pipeline) and when ('This skill should be used when the user says...'), satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

Extensive natural phrasings a user would actually say — 'infra change spec', 'infrastructure change', 'create infra change spec', 'write infra spec', 'upgrade to pipeline', 'convert to pipeline' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A clear niche within the Arness infra pipeline with distinctive, domain-specific triggers ('arn infra spec', 'upgrade to pipeline') unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AppsVortex/arness
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.