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.
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 proactively disambiguates from a related skill (/arn-code-create-issue). The only minor note is that the description leads with 'when' before 'what', but both are thoroughly covered.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple 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 what it does NOT do, adding further specificity. | 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). Also includes a 'Do NOT use' clause for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations like 'infra report', 'infra broke', 'infrastructure issue', 'report deployment problem', 'diagnose infra', 'infra doctor', and the formal command 'arn-infra-report'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — explicitly scoped to Arness Infra workflow issues and the Arness plugin repository, and explicitly distinguishes itself from /arn-code-create-issue for user project issues. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 workflow sequencing and robust error handling. Its main weakness is moderate verbosity — the scripted user-facing dialogue, repeated fallback patterns, and keyword lists add tokens without proportional value. The references to external template and knowledge base files support good progressive disclosure, though the bundle files weren't available to verify.
Suggestions
Condense the error handling section into a table (condition | action | fallback) to reduce repetition of the local-file fallback pattern
Shorten Step 0's keyword lists into a more compact format and reduce the Step 1 scripted dialogue to a brief summary of what will happen
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as the full scripted dialogue in Step 1 explaining the process to the user, and the detailed keyword lists in Step 0 that could be more compact. The error handling section repeats the same fallback pattern multiple times. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (gh issue create, gh auth status, git remote get-url), specific file paths, exact fallback filenames, and clear tool specifications. Each step has specific actions Claude can take without ambiguity. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, includes explicit validation checkpoints (user consent before submission in Step 5), feedback loops (edit and re-review), and comprehensive error recovery paths with fallbacks at every failure point. | 3 / 3 |
Progressive Disclosure | The skill references external files (infra-knowledge-base.md, issue-template.md) which is good progressive disclosure, but no bundle files were provided to verify these exist. The main SKILL.md itself is fairly long and some content (like the full error handling matrix) could potentially be split out, though it remains navigable. | 2 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- AppsVortex/arness
- Commit
1fe948f
- 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.