Name: arn-infra-report
Rating: 74.4 (1 reviews)
Author: AppsVortex

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 body is a well-structured, actionable multi-step workflow with strong sequencing, an explicit consent checkpoint before the irreversible public submit, and clean progressive disclosure into real reference files. Its only weakness is repetition of the local-fallback messaging and keyword lists that could be tightened.

Suggestions

Consolidate the repeated local-file fallback ("arness-infra-report-<YYYY-MM-DD>.md in the project root") into a single named note referenced from Steps 5–6 and Error Handling instead of restating it ~6 times.

Move the verbatim Code/Spark keyword lists (16 + 9 terms) into a short reference table or a bundled file so the main routing step stays scannable.

The cross-skill fallback path to `plugins/arn-infra/skills/arn-infra-ensure-config/references/ensure-config.md` is outside this bundle; either confirm it resolves at runtime or inline the dispatch convention so the skill is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept-explanation fluff, but the local-file fallback filename ("arness-infra-report-<YYYY-MM-DD>.md in the project root") is repeated across Steps 5–6 and the Error Handling section, and the dense Code/Spark keyword lists could be consolidated.	2 / 3
Actionability	Provides concrete, executable commands — `gh issue create --repo <owner/repo> --title … --label "arn-infra-report"`, `gh auth status`, `git -C ${CLAUDE_PLUGIN_ROOT} remote get-url origin` — plus specific tool usage (AskUserQuestion, Task tool) and real reference-file paths.	3 / 3
Workflow Clarity	Steps 0–6 are clearly sequenced with an explicit validation checkpoint in Step 5 (full draft review + explicit user consent before the outward-facing submit) and a dedicated Error Handling section covering recovery paths for each failure mode.	3 / 3
Progressive Disclosure	SKILL.md is an overview that points to two real, one-level-deep references — `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-report/references/infra-knowledge-base.md` (365 lines) and `references/issue-template.md` — both confirmed present and clearly signaled with full paths.	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 specific, trigger-rich, complete, and distinctively scoped with explicit negative guidance. It reads in third person and avoids vague fluff or over-claims. This is a strong, well-constructed skill description.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Invokes the arn-infra-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository" — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (diagnose then file a GitHub issue) and when ("This skill should be used when the user says…"), satisfying the clear what-and-when-with-explicit-triggers anchor.	3 / 3
Trigger Term Quality	Provides broad natural-language triggers a user would actually say ("infra report", "infra broke", "report deployment problem", "diagnose infra", "infra doctor"), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Arness Infra workflow issues) and adds negative guidance ("Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue"), making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AppsVortex/arness
Path: plugins/arn-infra/skills/arn-infra-report/SKILL.md
Commit: 7f87870

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.