CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-bug-spec

This skill should be used when the user says "bug spec", "arness code bug spec", "investigate this bug", "help me debug", "trace this bug", "diagnose this issue", "I found a bug", "something is broken", "why is X not working", "fix this bug", "debug this", "why is this not working", or wants to iteratively investigate a bug through guided conversation with diagnostic analysis. Bridges the gap between a bug report and either a direct fix or a structured bug specification for the Arness pipeline.

72

Quality

88%

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.

The body is highly actionable with executable commands, precise agent-invocation contexts, and a well-sequenced workflow featuring explicit validation and error-recovery feedback loops. Progressive disclosure is strong, with a concise overview pointing to four real one-level-deep reference files. The main weakness is conciseness: the same model-dispatch parenthetical and diagnosis-flow pointer are repeated verbatim several times.

Suggestions

Define the agent model-dispatch convention once (e.g., in the agent-invocation-guide reference) and reference it instead of repeating the full parenthetical '(see .../ensure-config.md "Dispatch convention" for fallback)' in Steps 3 and 6B.

Reference the diagnosis-flow.md document once at the start of the iterative phase rather than restating the 'Read .../diagnosis-flow.md' pointer in Steps 4, 5, 6A, and 6B.

Merge the duplicated 'For simple bugs... For complex bugs...' summary that appears in both the intro paragraph and the second paragraph into a single statement to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no primer on what a bug is), but it repeats the model-dispatch parenthetical verbatim across Steps 3, 6B and restates the diagnosis-flow pointer four times, which could be tightened to match the lean score-3 anchor.

2 / 3

Actionability

It gives concrete, copy-paste-ready guidance throughout: an executable `mkdir -p <plans-dir>/BUGFIX_<name>/reports` command, exact Task tool invocation contexts with named parameters, and precise file paths and templates, matching the score-3 anchor for fully executable instruction.

3 / 3

Workflow Clarity

Steps 0–7 are clearly sequenced, with explicit validation checkpoints (architect validation in Step 3, convergence checks in Step 4, complexity routing in Step 5, error-handling feedback loops for failed fix attempts and inconclusive investigators), fulfilling the score-3 anchor for clear sequence with feedback loops for error recovery.

3 / 3

Progressive Disclosure

The SKILL.md is an overview that signals four real one-level-deep references (agent-invocation-guide.md, diagnosis-flow.md, bugfix-plan-template.md, bug-spec-template.md, all present in references/), splitting detail appropriately and pointing to each with a clear 'Read ...' callout, matching the score-3 anchor.

3 / 3

Total

11

/

12

Passed

Description

92%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 specific, trigger-rich, and complete with an explicit 'Use when' clause and concrete actions, scoring well on specificity, trigger quality, and completeness. Its main weakness is distinctiveness: several trigger phrases overlap with general debugging skills, so it could fire when a simpler debug skill would suffice.

Suggestions

Narrow the trigger phrasing or add a qualifier that ties activation to the Arness pipeline (e.g., 'when the user wants a structured bug spec for the Arness pipeline') so the skill is less likely to grab plain 'help me debug' requests better served by a general debugging skill.

Consider dropping or de-emphasizing the most generic phrases ('something is broken', 'why is X not working') in favor of terms more strongly associated with producing a bug specification.

DimensionReasoningScore

Specificity

The description names concrete actions ('iteratively investigate a bug through guided conversation with diagnostic analysis', 'Bridges the gap between a bug report and either a direct fix or a structured bug specification'), matching the score-3 anchor that lists multiple specific actions rather than vague language.

3 / 3

Completeness

It answers both 'what' (bridges bug report to fix or structured spec, performs diagnostic analysis) and 'when' ('This skill should be used when the user says...'), with an explicit trigger clause that prevents the score cap of 2.

3 / 3

Trigger Term Quality

It enumerates natural trigger phrases a user would actually say ('bug spec', 'help me debug', 'trace this bug', 'why is X not working', 'fix this bug', 'something is broken', 'I found a bug'), giving good coverage of common variations as the score-3 anchor requires.

3 / 3

Distinctiveness Conflict Risk

The niche is somewhat specific (Arness pipeline bug specs) but the trigger phrases ('help me debug', 'fix this bug', 'something is broken') are broadly shared with general debugging skills, creating overlap risk that fits the score-2 'could still overlap with similar skills' anchor rather than a clear distinct niche.

2 / 3

Total

11

/

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.