CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-simplify

This skill should be used when the user says "simplify", "arness code simplify", "simplify code", "code simplification", "clean up code", "reduce complexity", "remove duplication", "check for reuse", "find duplicates", "optimize code", "efficiency review", "simplify implementation", "arn-code-simplify", or wants to review recently implemented code for reuse opportunities, quality issues, and efficiency problems after execution completes. Do NOT use this for full implementation correctness review (use arn-code-review-implementation) or PR review (use arn-code-review-pr).

74

Quality

92%

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 a well-engineered orchestration spec: highly actionable, with a clearly sequenced 8-step workflow, explicit validation/self-heal feedback loops, and clean one-level-deep progressive disclosure. The only weakness is minor redundancy from a repeated configuration-missing message.

Suggestions

Consolidate the repeated "Arness is not configured... Run /arn-implementing" message into a single Error Handling entry referenced from Prerequisites and Step 1 to remove the triple repetition.

Consider moving the inline applier prompt block (Step 6) into references/apply-prompt.md, keeping only the dispatch contract and return schema inline, to reduce body length while preserving the exact instructions.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no padding about what N+1 patterns or git are), but the "Arness is not configured..." message is repeated verbatim in Prerequisites, Step 1, and Error Handling, and the inline applier prompt is lengthy — it could be tightened, matching the level-2 "mostly efficient but could be tightened" anchor rather than fully lean.

2 / 3

Actionability

Fully executable guidance: exact Agent dispatch with model lookup, template variables ({files_to_review}, {code_patterns}), finding ID format (SIM-001), exact git commands (git diff --no-color HEAD > /tmp/pre-{findingId}.diff, git apply -R), and a complete exact JSON return schema — copy-paste ready, matching level 3.

3 / 3

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints and a feedback loop: apply -> run targeted test -> self-heal up to 3 attempts -> revert via git apply -R, then a final cumulative test pass, plus partial-failure and batch handling — matches the level-3 anchor.

3 / 3

Progressive Disclosure

SKILL.md is an overview that clearly signals two real one-level-deep references (scope-detection.md, review-prompts.md) via explicit "Read ${CLAUDE_PLUGIN_ROOT}/.../references/..." callouts; both files exist and the content is appropriately split, matching the level-3 anchor.

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 specific, trigger-rich, and explicitly disambiguated from sibling review skills with clear what-and-when guidance. It is an exemplar of a well-constructed skill description with no meaningful weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "review recently implemented code for reuse opportunities, quality issues, and efficiency problems after execution completes" — names the domain and several specific analysis axes, matching the level-3 anchor.

3 / 3

Completeness

Explicitly answers both: what (reuse/quality/efficiency review of recently implemented code) and when ("This skill should be used when the user says...") with an explicit trigger clause, plus negative boundary guidance — meets the level-3 anchor.

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say: "simplify", "simplify code", "code simplification", "clean up code", "reduce complexity", "remove duplication", "find duplicates", "optimize code", "efficiency review" — well beyond the level-2 single-keyword example.

3 / 3

Distinctiveness Conflict Risk

Clear post-execution niche with explicit disambiguation ("Do NOT use this for full implementation correctness review (use arn-code-review-implementation) or PR review (use arn-code-review-pr)") making it unlikely to trigger for the wrong skill.

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.