CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

Quality

100%

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

100%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 executable and tightly written, with a clear sequenced workflow, explicit prerequisite validation per tracker, and concrete commands/mappings for both GitHub and Jira. It is self-contained with no unnecessary reference indirection.

DimensionReasoningScore

Conciseness

Lean step-by-step prose with concrete commands and no padding or explanations of concepts Claude already knows; tables carry only the necessary mapping detail.

3 / 3

Actionability

Provides copy-paste-ready commands (gh issue create --title/--body/--label, gh label list --search, gh label create --force) and explicit Jira MCP fields (Project, Issue type, Summary, Description, Priority, Labels).

3 / 3

Workflow Clarity

A clear 5-step sequence with per-tracker prerequisite checks, an idempotent deferred-label check, and feedback loops (prerequisite failure stops the flow; issue-creation failure offers retry).

3 / 3

Progressive Disclosure

No local bundle files exist, so the self-contained body is appropriately sectioned (Prerequisites, Classify, Priority, Compose, Submit, Error Handling, Conventions) with one signaled external plugin reference; organization supports easy navigation.

3 / 3

Total

12

/

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 comprehensive, concrete, and well-triggered, covering both what and when with an explicit disambiguation against a sibling skill. It avoids fluff and uses third-person voice throughout.

DimensionReasoningScore

Specificity

Names concrete actions ("create an issue ... with Arness labels for type and priority") across two concrete trackers (GitHub or Jira), rather than vague language.

3 / 3

Completeness

Explicitly answers both what (create an issue with Arness labels for type and priority) and when ("This skill should be used when the user says ... or wants to create an issue"), plus a negative trigger for disambiguation.

3 / 3

Trigger Term Quality

Broad natural-phrase coverage a user would actually say ("create issue", "file issue", "report bug", "request feature", "add to backlog", "create GitHub issue", "create Jira issue", etc.).

3 / 3

Distinctiveness Conflict Risk

Clear niche (issue creation in a configured tracker) and an explicit guard ("Do NOT use this for picking/browsing existing issues — use /arn-code-pick-issue"), making wrong-skill triggering 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.