CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-help

This skill should be used when the user says "infra help", "arn infra help", "where am I in the pipeline", "what's next for infra", "infra status", "pipeline status", "infra pipeline", "arn-infra-help", "show infra pipeline", "what step am I on for infra", "infra workflow", "infrastructure status", "show infrastructure pipeline", or wants to see their current position in the Arness Infra workflow and get guidance on the next step. This skill detects whether the user is in Quick (interactive) mode or Full Pipeline mode and renders an ASCII diagram with the active stage marked.

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.

A well-structured read-only diagnostic skill with concrete, actionable guidance, clear step sequencing, and good progressive disclosure to a single reference file. Its only weakness is mild redundancy (repeated default listings and a verbose follow-up Q&A section) that slightly inflates the token budget.

Suggestions

Consolidate the infra directory defaults: the Prerequisites list and the "If any of the infra-specific directory fields are missing" block repeat the same three defaults — keep one and reference it from the other.

Trim Step 5's common-questions list to the few highest-value items or move the full FAQ into pipeline-map.md, keeping only a pointer inline to reduce token usage.

Where Error Handling restates Prerequisites conditions (e.g., deferred mode and missing ## Arness), cross-reference the earlier section instead of repeating the full guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of conceptual filler, but repeats material — directory defaults appear twice (Prerequisites then the "If any… missing" block) and Step 5's long follow-up Q&A list is verbose — so it lands at the "mostly efficient but could be tightened" level rather than fully lean.

2 / 3

Actionability

Gives concrete, executable guidance — exact reference paths, explicit most-advanced-to-least stage ordering with "first match wins", exact user-facing messages, and fully-qualified command suggestions — meeting the copy-paste-ready top anchor for an instruction-only skill.

3 / 3

Workflow Clarity

Steps 0–5 are clearly sequenced with explicit detection rules, stop conditions, and fallbacks, plus a dedicated Error Handling section covering missing config, no artifacts, ambiguous state, missing directories, missing reference, and deferred mode — clear sequence with explicit checkpoints.

3 / 3

Progressive Disclosure

The body is an overview that offloads bulky detail (detection rules, ASCII templates, next-step tables) to a single one-level-deep reference (references/pipeline-map.md, confirmed present) with clear signaling, matching the well-split, easy-navigation top 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.

A high-quality description that names concrete actions, covers natural trigger terms broadly, and answers both what and when with explicit triggers. It is clearly scoped to the Arness Infra niche and written in third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "detects whether the user is in Quick (interactive) mode or Full Pipeline mode", "renders an ASCII diagram with the active stage marked", and "get guidance on the next step" — matching the top anchor rather than the single-action level 2.

3 / 3

Completeness

Explicitly answers both what (detect mode, render ASCII diagram with active stage, give next-step guidance) and when (a full trigger-phrase list plus "or wants to see their current position"), satisfying the explicit-triggers anchor.

3 / 3

Trigger Term Quality

Provides a broad set of natural phrases a user would actually say ("infra help", "where am I in the pipeline", "what's next for infra", "infra status", "pipeline status"), giving strong coverage rather than the partial level 2.

3 / 3

Distinctiveness Conflict Risk

Scoped to the "Arness Infra workflow" with infra-specific triggers, making it unlikely to fire for sibling skills like code-help or spark-help; not the generic, overlapping 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.