CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-assess

This skill should be used when the user says "arness code assess", "arn-code-assess", "assess codebase", "technical review", "codebase assessment", "find improvements", "what should I improve", "tech debt review", "tech debt audit", "pattern compliance check", "codebase health check", "assess the project", "improvement plan", "review my codebase", "what needs fixing", "code quality check", "audit my code", "run an assessment", or wants a comprehensive technical assessment of the codebase against stored patterns followed by prioritized improvement execution through the full Arness pipeline.

68

Quality

83%

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 content is a well-structured, highly actionable sequencer with explicit gates, resumability, and feedback loops, and it appropriately offloads detail to two one-level-deep references; its main weakness is token padding from repeated progress-display blocks.

Suggestions

Replace the per-step ASCII progress-display blocks with a single defined format referenced once, or show only the active-stage variant, to cut repeated padding across the ~13 steps.

Consider condensing the repeated gate-option tables into a compact shared format now that the full gate table already appears in the 'Decision Gates' section.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens (gates table, state-detection table, exact tool invocations), but repeats a near-identical ASCII progress-display block for each of the ~13 steps and verbose gate-option tables that a leaner version could collapse, fitting anchor 2.

2 / 3

Actionability

It provides fully concrete, executable guidance: exact Skill invocations ("Skill: arn-code:arn-code-feature-spec"), exact agent names, exact file paths, exact AskUserQuestion option text, and exact artifact-detection rules, matching the copy-paste-ready anchor 3.

3 / 3

Workflow Clarity

The 13-step pipeline is clearly sequenced with 7 explicit gates (G1–G7), a resumability/state-detection table, a conflict-detection loop (G5), and a re-test feedback loop (G6), giving clear checkpoints and feedback loops for the risky batch pipeline.

3 / 3

Progressive Disclosure

SKILL.md is an overview/sequencer that defers detail to two real, one-level-deep reference files (assessment-protocol.md, orchestration-flow.md) signaled with exact Read paths, while keeping only the sequencing logic inline, matching the clear-overview anchor 3.

3 / 3

Total

11

/

12

Passed

Description

82%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 has excellent trigger coverage and clearly answers both what the skill does and when to use it, but is written in second person as a trigger list rather than third-person capability voice, and includes several generic review phrases that risk overlap with sibling skills.

Suggestions

Rewrite the capability statement in third person (e.g., "Runs a comprehensive technical assessment...") and move trigger phrases into a concise 'Use when...' clause to satisfy the third-person voice guideline.

Tighten the trigger list by dropping or narrowing generic phrases like "technical review" and "code quality check" that could collide with other review skills, keeping the distinctive 'arness'/'arn-code-assess' and stored-patterns terms.

DimensionReasoningScore

Specificity

The description names the domain ("comprehensive technical assessment of the codebase against stored patterns followed by prioritized improvement execution through the full Arness pipeline") but states capabilities mostly as trigger phrases rather than a list of concrete action verbs; it is not a comprehensive action enumeration, fitting anchor 2.

2 / 3

Completeness

It explicitly answers both "what" (comprehensive technical assessment against stored patterns plus prioritized improvement through the pipeline) and "when" (an explicit "This skill should be used when the user says..." clause with many triggers), so it is not capped at 2.

3 / 3

Trigger Term Quality

It lists an extensive set of natural phrases a user would actually say ("codebase assessment", "tech debt review", "code quality check", "audit my code", "what should I improve", "run an assessment"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Arness pipeline framing and "arn-code-assess" invocation carve a niche, but generic phrases like "technical review", "code quality check", and "review my codebase" could overlap with other review skills, so it is somewhat specific rather than clearly conflict-free.

2 / 3

Total

10

/

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.