CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-report

This skill should be used when the user says "report issue", "arness code report", "code report", "something went wrong", "report a bug", "file arness code issue", "arness code broke", "report arness code problem", "diagnose issue", "arness doctor", "run doctor", "diagnose arness code", "arn-code-report", or wants to report a problem with an Arness Code workflow skill. Invokes the arn-code-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. For Spark issues use /arn-spark-report. For Infra issues use /arn-infra-report.

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, actionable multi-step workflow with clear sequencing, validation checkpoints, and properly externalized references that all exist in the bundle. The main weakness is repetition of the local-file fallback pattern across several sections, which inflates token usage without adding clarity.

Suggestions

Consolidate the `arness-code-report-<YYYY-MM-DD>.md` local-save fallback into a single named section (e.g. an 'Output fallback' subsection) and reference it from Steps 3, 5, 6, and Error Handling instead of restating the behavior each time.

Extract the repeated prerequisite/error-handling prose into a short checklist so the workflow steps stay lean.

DimensionReasoningScore

Conciseness

The body is dense and purposeful with no concept-explanation fluff, but the fallback filename `arness-code-report-<YYYY-MM-DD>.md` and its save behavior are restated across Step 3, Step 5, Step 6, and Error Handling, which could be consolidated. It is mostly efficient but could be tightened.

2 / 3

Actionability

Provides concrete, executable commands — `gh issue create --repo <owner/repo> --title "<title>" --body "<body>" --label "arn-code-report"`, `gh auth status`, `git -C ${CLAUDE_PLUGIN_ROOT} remote get-url origin` — plus exact file paths and a clear Task-tool dispatch, making the guidance copy-paste ready modulo standard substitution.

3 / 3

Workflow Clarity

Steps 0–6 are clearly sequenced with explicit validation checkpoints (prerequisite checks in Step 3, explicit consent gate in Step 5) and feedback loops for error recovery (label-missing retry in Step 6, submission-failure local-save fallback).

3 / 3

Progressive Disclosure

The body is an overview that delegates detail to one-level-deep, clearly signaled references — `references/arness-knowledge-base.md` and `references/issue-template.md` — both of which exist in the bundle. Content is appropriately split rather than inlined.

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 excellent: concrete actions, natural trigger phrases, explicit when-guidance, and strong disambiguation against sibling report skills. Voice is correctly third person throughout.

DimensionReasoningScore

Specificity

Names concrete actions — "Invokes the arn-code-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository" — listing multiple specific operations rather than vague language. Uses third person ("This skill should be used"), satisfying the voice requirement.

3 / 3

Completeness

Explicitly answers both what (invoke doctor agent, file GitHub issue) and when ("This skill should be used when the user says...") with explicit trigger guidance.

3 / 3

Trigger Term Quality

Lists many natural phrases users would actually say — "report issue", "something went wrong", "report a bug", "arness doctor", "run doctor", "diagnose issue" — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clear niche with explicit disambiguation — "Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue", plus redirects for Spark and Infra issues — making conflict with sibling skills unlikely.

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.