arn-code-create-issue
This skill should be used when the user says "create issue", "file issue", "arness code issue", "arness code create issue", "arn-code-create-issue", "report bug", "request feature", "add to backlog", "create GitHub issue", "create Jira issue", "file a bug", "submit issue", "log issue", "open issue", or wants to create an issue in the current repository with Arness labels for type and priority. Requires an issue tracker (GitHub or Jira) to be configured. Do NOT use this for picking/browsing existing issues — use /arn-code-pick-issue for that.
86
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 description excels at trigger term coverage and completeness, with an extensive list of natural phrases and a clear negative boundary to prevent conflicts. Its main weakness is that it focuses heavily on when to trigger rather than detailing what concrete actions the skill performs beyond 'create an issue with Arness labels'. Adding more specificity about the skill's actual workflow would strengthen it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Prompts for issue title, description, type label, and priority label, then creates the issue in the configured tracker and returns the issue URL.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (issue creation in GitHub/Jira) and mentions Arness labels for type and priority, but doesn't list specific concrete actions beyond 'create an issue'. It lacks detail on what the skill actually does step-by-step (e.g., does it prompt for fields, auto-label, assign milestones?). | 2 / 3 |
Completeness | Clearly answers both 'what' (creates issues in the current repository with Arness labels for type and priority, requires GitHub or Jira) and 'when' (explicit list of trigger phrases plus a negative boundary distinguishing it from the pick-issue skill). The explicit 'Do NOT use' clause adds further clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including many variations users would actually say: 'create issue', 'file issue', 'report bug', 'request feature', 'add to backlog', 'create GitHub issue', 'create Jira issue', 'file a bug', 'submit issue', 'log issue', 'open issue'. This is comprehensive and covers common phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (issue creation specifically with Arness labels) and an explicit negative boundary ('Do NOT use this for picking/browsing existing issues — use /arn-code-pick-issue for that'), which directly reduces conflict risk with the most likely overlapping skill. | 3 / 3 |
Total | 11 / 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 step-by-step workflows, concrete commands, and thorough error handling. Its main weaknesses are moderate verbosity from repeated platform-conditional sections and a somewhat monolithic structure that could benefit from splitting platform-specific details into separate reference files. The trigger message inference shortcut is a nice touch that shows thoughtful UX design.
Suggestions
Consider extracting the GitHub-specific and Jira-specific details into separate reference files (e.g., github-issue-creation.md, jira-issue-creation.md) to reduce interleaving and improve progressive disclosure.
Remove repeated phrases like 'The user-facing question is the same regardless of issue tracker. The internal mapping differs by platform and is applied during submission (Step 5).' — state this once at the top.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy — the table mappings for GitHub/Jira are repeated across steps, and phrases like 'The user-facing question is the same regardless of issue tracker' are stated multiple times. Some sections could be tightened, but overall it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (gh issue create, gh label list, gh auth status, git remote -v), specific label names, exact CLI syntax, and clear Jira MCP field mappings. The guidance is copy-paste ready and leaves little ambiguity about what to do. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 numbered steps with explicit prerequisite checks, conditional branching for GitHub vs Jira vs none, a deferred label check before submission, and a comprehensive error handling section covering multiple failure modes with recovery suggestions. | 3 / 3 |
Progressive Disclosure | The skill references an external file (platform-labels.md) appropriately, but the content is somewhat monolithic — the GitHub and Jira paths are interleaved throughout every step rather than being cleanly separated into referenced sub-documents. For a skill of this length (~120 lines of substantive content), some of the platform-specific details could be split out. | 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.