CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-deploy

This skill should be used when the user says "deploy", "deploy to staging", "deploy to production", "promote to production", "infra deploy", "arn infra deploy", "deploy infrastructure", "apply infrastructure", "push to prod", "go live", "tofu apply", "terraform apply", "pulumi up", "cdk deploy", "fly deploy", "deploy to railway", "release to prod", "promote environment", or wants to execute a deployment of their infrastructure to a target environment. This skill handles environment promotion, CI/CD enforcement, cost gates, safety layers, and resource tracking.

74

Quality

92%

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.

The content is a high-quality, well-sequenced deployment workflow with concrete executable commands and clean progressive disclosure to verified reference files. Its only weakness is conciseness — embedded prompt text and some redundancy inflate the token budget.

Suggestions

Move the verbatim user-facing prompt strings (e.g. the AskUserQuestion wording and the deployment summary template) into a reference or collapse them to short directives to cut tokens without losing the workflow.

Tighten the Prerequisites section: the long bullet list of fields to extract could reference the Arness config schema rather than enumerating every field inline.

Consolidate repeated safety-checklist phrasing between Step 3 and the Error Handling section into a single source to avoid duplication.

DimensionReasoningScore

Conciseness

The body is largely instructional and free of concept-explaining fluff, but at ~300 lines it carries avoidable tokens: verbatim user-facing prompt strings, a dense prerequisites list, and some repeated checklist phrasing that could be tightened into the references.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance per IaC tool in a command table (e.g. 'tofu apply deploy.tfplan', 'pulumi up --stack <env> --yes'), exact file paths, label names, and the saved-plan technique, with no pseudocode gaps.

3 / 3

Workflow Clarity

A clear 9-step sequence with explicit validation checkpoints (safety gates in Step 3, promotion enforcement in Step 1, mandatory confirmation before all deployments) and feedback loops (retry/rollback/cancel on failure) appropriate for this destructive operation.

3 / 3

Progressive Disclosure

The body is an overview that offloads detail to four real, one-level-deep references (deployment-safety-checklist.md, rollback-patterns.md, resource-manifest-schema.md, infra-handoff-template.md), each clearly signaled with a '> Read ...' callout at the relevant step; all referenced files exist in ./references/.

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 strong: it pairs a comprehensive, natural-language trigger list with a concrete enumeration of the skill's capabilities and an explicit 'when to use' clause, all in third person. It is among the best examples in the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('environment promotion, CI/CD enforcement, cost gates, safety layers, and resource tracking'), matching the level-3 anchor for listing several specific actions rather than just naming a domain.

3 / 3

Completeness

Explicitly answers both what (the five handled concerns) and when ('This skill should be used when the user says... or wants to execute a deployment'), satisfying the level-3 anchor for explicit triggers rather than only implied 'when'.

3 / 3

Trigger Term Quality

Provides broad natural trigger coverage a user would actually say ('deploy', 'push to prod', 'go live', 'tofu apply', 'pulumi up', 'cdk deploy', 'fly deploy', 'release to prod'), including tool-specific variations beyond generic phrasing.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche with distinct triggers ('arn infra deploy', 'promote to production') unlikely to collide with other skills, rather than the generic overlap seen at level 2.

3 / 3

Total

12

/

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.