Name: arn-implementing
Rating: 69.6 (1 reviews)
Author: AppsVortex

arn-implementing

This skill should be used when the user says "implementing", "arness implementing", "start implementing", "execute the plan", "build it", "implement this", "run the tasks", "execute", "start building", "implement the feature", "implement the fix", "quick change", "swift", "swift mode", "quick implementation", "standard", "standard mode", "standard implementation", "start execution", "build the feature", "arn-implementing", or wants to execute an implementation plan, run a quick implementation, a standard-tier implementation, or manage the build-simplify-review cycle. Chains to arn-shipping at completion.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%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 highly actionable, well-sequenced orchestration skill with strong workflow clarity and concrete routing guidance. It loses points on conciseness (duplicated preference/follow-up logic) and progressive disclosure (everything inline with no reference files).

Suggestions

Extract the duplicated two-tier preference lookup and "remember this?" write logic into a single shared reference (e.g. references/preference-gates.md) and have G3/G4 point to it, eliminating the verbatim repetition.

Move the detailed CHANGE_RECORD.json field-by-field population list in Step 7 into a reference file, keeping only the trigger conditions and output path inline in SKILL.md.

Fix the duplicate "Step 0" numbering (Ensure Configuration vs Input Routing) to avoid sequence confusion.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but the two-tier preference lookup chain and the "remember this?" follow-up with its write logic are duplicated nearly verbatim across G3 and G4, and two sections are both numbered "Step 0".	2 / 3
Actionability	Guidance is concrete and executable for an instruction-only orchestrator: exact `Skill: arn-code:...` invocations, literal AskUserQuestion prompts and options, specific artifact paths, preference keys, and file-write logic.	3 / 3
Workflow Clarity	A clearly sequenced gate flow (G0-G5) with a state-detection resume table, explicit decision gates, a NEEDS-FIXES review feedback loop, a complexity-override checkpoint, and a dedicated Error Handling section.	3 / 3
Progressive Disclosure	Sections are well organized, but the skill is monolithic - no bundle files exist and all detail (CHANGE_RECORD.json field population, preference lookup chain, gate logic) lives inline in SKILL.md rather than being split into one-level-deep references.	2 / 3
	Total	10 / 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.

A strong, trigger-rich description that clearly states both capability and activation conditions in third person. Its main weakness is a set of broadly generic trigger terms that raise conflict risk against neighboring execution skills.

Suggestions

Tighten generic triggers like "build it", "execute", and "standard" with disambiguating context (e.g. "execute the implementation plan") to reduce overlap with sibling arn execution skills.

Consider leading with the distinctive niche phrase ("manage the build-simplify-review cycle") earlier so the skill's unique role is apparent before the long trigger list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - "execute an implementation plan, run a quick implementation, a standard-tier implementation, or manage the build-simplify-review cycle" - rather than vague language.	3 / 3
Completeness	Explicitly answers both what (execute plan / quick / standard-tier / build-simplify-review cycle) and when via an explicit "should be used when the user says..." trigger clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Broad coverage of natural phrases users would say ("implement this", "build it", "execute the plan", "quick change", "swift", "standard mode"), matching the score-3 anchor for natural-term coverage.	3 / 3
Distinctiveness Conflict Risk	The implementation-orchestration niche is clear, but several triggers ("build it", "execute", "standard", "quick change") are generic enough to overlap with sibling arn skills or unrelated coding skills, so it is not a clean score-3.	2 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AppsVortex/arness
Path: plugins/arn-code/skills/arn-implementing/SKILL.md
Commit: 7f87870

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.