CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-report

This skill should be used when the user says "infra report", "report infra issue", "infra broke", "arn-infra-report", "infrastructure issue", "report deployment problem", "report infrastructure problem", "diagnose infra", "infra doctor", or wants to report a problem with an Arness Infra workflow skill. Invokes the arn-infra-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository. Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue for that.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a well-structured, highly actionable skill with clear multi-step workflow, explicit validation checkpoints, comprehensive error handling, and strong safety constraints around data privacy and user consent. Its main weakness is moderate verbosity — some sections like the Smart Routing keyword lists and the scripted user explanation could be tightened. The progressive disclosure is decent with references to external templates and knowledge bases, though the main file is on the longer side.

Suggestions

Condense the Smart Routing keyword lists into a more compact format (e.g., a brief table or comma-separated list) to reduce token usage.

Shorten Step 1's scripted explanation — Claude can adapt the phrasing naturally; a brief bullet list of what will happen is sufficient.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary verbosity — the full user-facing explanation script in Step 1 is somewhat padded, and the Smart Routing step with extensive keyword lists could be more compact. However, most content is functional and necessary for the workflow.

2 / 3

Actionability

The skill provides concrete, executable commands (gh issue create, gh auth status, git remote get-url), specific file paths, exact tool names (AskUserQuestion, Task tool), and clear fallback behaviors. The guidance is specific enough to be directly followed.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (Steps 0-6) with explicit validation checkpoints: user consent before submission, label existence check with retry, authentication verification, and multiple fallback paths. Error handling is comprehensive with a dedicated section covering each failure mode and recovery action.

3 / 3

Progressive Disclosure

The skill references external files (infra-knowledge-base.md, issue-template.md, ensure-config.md) which is good progressive disclosure, but the main SKILL.md itself is quite long and some content (like the full keyword lists in Smart Routing or the detailed error handling table) could potentially be split out. No bundle files were provided to verify referenced paths exist.

2 / 3

Total

10

/

12

Passed

Description

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 across all dimensions. It provides extensive trigger terms, clearly describes what the skill does and when to use it, and explicitly distinguishes itself from a related skill to prevent misselection. The use of third person voice and concrete actions makes it both precise and actionable.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Invokes the arn-infra-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository.' Also explicitly distinguishes from a related skill (/arn-code-create-issue).

3 / 3

Completeness

Clearly answers both 'what' (diagnoses infra issues via arn-infra-doctor agent and files GitHub issues on the Arness plugin repo) and 'when' (explicit list of trigger phrases plus a 'Use when' equivalent at the start, and a 'Do NOT use' negative boundary).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including many variations: 'infra report', 'report infra issue', 'infra broke', 'infrastructure issue', 'report deployment problem', 'diagnose infra', 'infra doctor'. These are terms users would naturally say.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche (Arness Infra workflow issues specifically), and explicitly differentiates itself from the related /arn-code-create-issue skill, reducing conflict risk significantly.

3 / 3

Total

12

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.