CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-review-plan

This skill should be used when the user says "review plan", "validate plan", "check plan", "sanity check the plan", "verify plan", "review my plan", "audit plan", "is my plan ready", or wants to validate a structured project plan for completeness, correctness, and pattern compliance before execution. Checks structural completeness, document quality, dependency graph consistency, codebase reference validity, and pattern compliance. Offers to fix found issues interactively and can proceed directly to arn-code-taskify when the plan passes.

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.

A well-structured, highly actionable review workflow with clear sequencing and a real verification feedback loop. The only weakness is mild verbosity in the example report block and remediation option enumerations.

Suggestions

Tighten the Step 5 report-format example to a compact schema/outline rather than a full mock listing — the populated example repeats structure already implied by Step 7's report sections.

Compress the Step 6 AskUserQuestion option lists into a single concise table or shorter bullet phrasing; the three near-identical option sets (errors / warnings / no-issues) carry redundant wording.

Move the generic suggested-fix phrasing examples out of Step 2 inline prose into the references/validation-checks.md per-check details to keep the body lean.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explanation fluff, but the inline report-format example block and the enumerated AskUserQuestion remediation options are padded and could be tightened without losing clarity.

2 / 3

Actionability

Gives concrete file paths, check IDs (e.g. S001, T013), specific fix suggestions, explicit report save paths, and precise user-option lists — fully actionable even without executable code.

3 / 3

Workflow Clarity

Seven clearly sequenced steps with an explicit remediation feedback loop ('Re-run only the checks that had findings to verify the fixes resolved them') and severity-based gating before proceeding.

3 / 3

Progressive Disclosure

The SKILL.md body is an overview that points one level deep to references/validation-checks.md (verified to exist) for the detailed checklist, with clear signaling.

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.

A strong description: concrete capabilities, rich natural trigger phrases, and explicit when-guidance in proper third-person voice. It clearly distinguishes the skill and is unlikely to conflict with others.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Checks structural completeness, document quality, dependency graph consistency, codebase reference validity, and pattern compliance. Offers to fix found issues interactively') in third-person voice.

3 / 3

Completeness

Explicitly answers both what (the structural/document/pattern checks) and when ('should be used when the user says...'), with explicit trigger guidance satisfying the 'Use when...' requirement.

3 / 3

Trigger Term Quality

Provides broad coverage of natural trigger phrases users would say: 'review plan', 'validate plan', 'check plan', 'sanity check the plan', 'verify plan', 'audit plan', 'is my plan ready'.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (reviewing Arness structured project plans) with distinct, plan-specific triggers unlikely to fire for unrelated skills.

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.