CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-assessing

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

70

Quality

86%

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, lean orchestration wrapper with clear sequencing, validation checkpoints, and appropriate offloading to referenced skills. The only weakness is that the pre-flight file-existence checks are described rather than given as concrete executable commands.

Suggestions

Add a concrete executable check for the pre-flight step (e.g., a shell snippet or tool instruction to confirm code-patterns.md, testing-patterns.md, and architecture.md exist) rather than describing the check, to raise actionability to level 3.

Clarify the exact invocation form of `Skill: arn-code:arn-code-assess` (is it a Skill tool call, a literal string, or a slash command?) so the instruction is unambiguous and copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, declaring itself a wrapper that must not duplicate logic and listing only the orchestration steps it owns; it does not explain concepts Claude already knows.

3 / 3

Actionability

It gives concrete instructions (file paths to verify, an exact Skill invocation token, and verbatim user-facing messages), but the pre-flight check lacks a concrete verification command and relies on described checks rather than executable ones.

2 / 3

Workflow Clarity

Steps are clearly sequenced (Step 0 config, Step 1 pre-flight, Step 2 invoke, Step 3 handoff) with explicit validation checkpoints (block if pattern docs missing, retry/abort on assess failure, no chain when healthy) and feedback loops.

3 / 3

Progressive Disclosure

It is a concise overview that offloads detail to one-level-deep references (step-0-fast-path.md, the invoked assess skill, and the implementing chain) and keeps the body itself appropriately thin for a wrapper skill.

3 / 3

Total

11

/

12

Passed

Description

87%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 on completeness, trigger coverage, and distinctiveness, with an explicit use-when clause and natural trigger phrases. It is slightly less specific in enumerating concrete actions, leaning on one compound phrase rather than a list of discrete capabilities.

Suggestions

Replace the single compound action phrase ('comprehensive technical assessment ... followed by prioritized improvement execution') with a short enumerated list of concrete actions (e.g., compares codebase against stored patterns, identifies improvements, prioritizes them, chains to implementation) to lift specificity to level 3.

DimensionReasoningScore

Specificity

It names the domain ('comprehensive technical assessment of the codebase against stored patterns') and concrete actions ('prioritized improvement execution'), but does not enumerate multiple specific actions the way the level-3 anchor requires.

2 / 3

Completeness

It answers both 'what' (assessment against stored patterns followed by prioritized improvement execution) and 'when' via an explicit 'This skill should be used when...' trigger clause, satisfying both halves.

3 / 3

Trigger Term Quality

It lists an extensive set of natural trigger phrases a user would actually say ('assess codebase', 'tech debt review', 'codebase health check', 'improvement plan', 'audit my code'), covering many common variations.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (codebase assessment against stored patterns with chaining to arn-implementing) and uses distinctive, skill-specific trigger terms, making conflict with other skills unlikely.

3 / 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.