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.
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 explains what the skill does and when to use it, and explicitly disambiguates from related skills with negative boundaries. The only minor note is the heavy front-loading of trigger terms which makes it slightly verbose, but this doesn't detract from its effectiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: invoking the arn-code-doctor agent to diagnose issues, filing a GitHub issue on the Arness plugin repository. Also clearly distinguishes what it does NOT do. | 3 / 3 |
Completeness | Clearly answers both 'what' (diagnoses issues via arn-code-doctor agent and files GitHub issues on the Arness plugin repo) and 'when' (explicit trigger phrases and a clear 'Use when' equivalent at the start). Also includes explicit negative boundaries for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say, including many variations like 'report issue', 'something went wrong', 'report a bug', 'arness code broke', 'diagnose issue', 'run doctor', and the command alias 'arn-code-report'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit negative boundaries ('Do NOT use this for filing issues on the user's own project', 'For Spark issues use /arn-spark-report', 'For Infra issues use /arn-infra-report'), making it very unlikely to conflict with related 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 workflow skill with clear step sequencing, smart routing logic, and robust error handling. Its main weaknesses are moderate verbosity — particularly the repeated local-file fallback pattern across both the workflow and error handling sections — and the canned explanation text in Step 1 that Claude could generate naturally. The referenced bundle files (issue-template.md, arness-knowledge-base.md) support good progressive disclosure in principle, though they couldn't be verified.
Suggestions
Consolidate the repeated local-file fallback pattern into a single 'Fallback' section referenced from the workflow steps, rather than restating the same arness-code-report-<YYYY-MM-DD>.md pattern 4+ times.
Remove or significantly shorten the canned explanation in Step 1 — Claude can compose a natural explanation from the workflow context without a verbatim script.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity — the full explanation script in Step 1 is a canned message Claude could compose on its own, and some error handling cases are repetitive (the same local file fallback is described 4+ times). The smart routing keyword lists and workflow steps are mostly justified, but could be tightened. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (gh issue create with specific flags), specific file paths (${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json), exact field names to extract, specific tool invocations (AskUserQuestion, Task tool), and clear fallback behaviors. The guidance is copy-paste ready and leaves little ambiguity. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0-6) with explicit validation checkpoints: smart routing check before proceeding, prerequisite verification, user review/consent before submission, and retry logic for label failures. Error recovery paths are well-defined with fallbacks at each failure point, and the consent step acts as a critical validation gate before the destructive action of public issue filing. | 3 / 3 |
Progressive Disclosure | The skill references external files (arness-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 quite long (~120 lines of substantive content) and the error handling section largely repeats fallback patterns already described inline in the workflow steps, which could have been consolidated or extracted. | 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.