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

arn-spark-report

This skill should be used when the user says "spark report", "report spark issue", "spark broke", "arn-spark-report", "greenfield issue", "report greenfield problem", "report spark problem", "diagnose spark", "spark doctor", "spark bug", "spark not working", or wants to report a problem with an Arness Spark workflow skill. Invokes the arn-spark-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, highly actionable multi-step workflow with explicit validation checkpoints, concrete commands, and properly externalized reference files. The only weakness is mild verbosity in the scripted user-facing dialogue that could be condensed.

Suggestions

Condense the verbatim Step 1 "Explain the Process" script to a brief bullet summary of the flow rather than a full quoted paragraph, since the same information is already conveyed by the Workflow section headings.

Trim the AskUserQuestion options block in Step 5 to concise option labels with one-line descriptions instead of multi-line quoted text, keeping the consent intent intact.

Consider moving the Step 0 keyword-routing lists (Code/Infra signals) into a short reference table or the spark-knowledge-base.md file to reduce inline length in the main skill body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concepts Claude already knows, but the verbatim Step 1 "Explain the Process" script and the full AskUserQuestion options block add length that could be tightened, matching the level-2 anchor of mostly-efficient-but-could-be-tightened rather than the lean level-3 example.	2 / 3
Actionability	Provides copy-paste-ready commands such as `gh issue create --repo <owner/repo> --title "<title>" --body "<body>" --label "arn-spark-report"` plus concrete fallbacks and specific reference file paths, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps 0–6 are clearly sequenced with an explicit consent checkpoint (Step 5) before the irreversible public submission and a retry-without-label feedback loop (Step 6), satisfying the validation-checkpoint requirement for an outward-facing operation.	3 / 3
Progressive Disclosure	Both referenced bundle files (issue-template.md, spark-knowledge-base.md) exist in ./references/ and are clearly signaled one level deep ("using the template from .../issue-template.md", "read the knowledge base at .../spark-knowledge-base.md"), with detailed material appropriately split out of the main body.	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 strong: it uses third-person voice, states concrete actions, lists natural trigger phrases, and explicitly scopes when to (and not to) use the skill. It cleanly satisfies the what/when/completeness and distinctiveness criteria.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Invokes the arn-spark-doctor agent to diagnose the issue" and "files a GitHub issue on the Arness plugin repository" — matching the anchor for listing several specific concrete actions rather than the vaguer level-2 example.	3 / 3
Completeness	Explicitly answers both what (diagnose via agent, file GitHub issue) and when via an explicit "This skill should be used when the user says..." clause, so it is not capped at 2 for missing trigger guidance.	3 / 3
Trigger Term Quality	Provides broad coverage of natural phrases a user would say ("spark report", "spark broke", "spark not working", "diagnose spark", "spark bug"), matching the anchor for good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Arness Spark workflow issues) and explicitly disambiguates with "Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue for that," 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-spark/skills/arn-spark-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.