CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

arn-code-swift

This skill should be used when the user says "arness code swift", "small change", "just do this", "quick feature", "swift fix", "implement this quickly", "add this quickly", "simple change", "just implement this", "arn-code-swift", "quick task", or wants a lightweight, pattern-aware implementation for a small feature or enhancement (1-8 files) without going through the full Arness pipeline. Bridges the gap between raw Claude Code and the full feature-spec/plan pipeline. Includes architectural assessment, targeted testing, and pattern compliance review.

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

75%Weight 40%Scale 1-5

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-checkpointed workflow skill: verbatim prompts, exact schemas, self-healing test loops, and a complete review/ship cycle, with genuine one-level-deep reference files. The main costs are token efficiency (a verbatim-duplicated preference block and inline schema detail inflate the body) and a step-numbering collision between Step 2's subsections and the standalone Step 2b/2c sections.

Suggestions

Extract the preference-check/gate/follow-up block (duplicated verbatim between Steps 4b and 5b, ~40 lines) into a shared reference (e.g., preference-gates.md) and invoke it from both paths.

Fix the numbering collision: Step 2 contains subsections 2a-2d while separate top-level sections are also named 'Step 2b'/'Step 2c'; renumber the sketch offer and sketch manifest sections (e.g., Steps 2E/2F) so the sequence is unambiguous.

Move the field-by-field CHANGE_RECORD spec and the long UI/security term lists into reference files to slim the main body.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is dense procedural instruction, but the ~600-line body duplicates the entire preference-check/gate/follow-up block verbatim between Step 4A section 4b and Step 4B section 5b, and inlines the field-by-field CHANGE_RECORD spec and long UI/security term lists that belong in references. Mostly efficient but could be tightened, matching anchor 3 rather than 4 because the duplication exceeds 'minor instances'.

3 / 5

Actionability

Fully executable guidance throughout: verbatim user-facing messages, exact commands ('mkdir -p <plans-dir>/SWIFT_<name>'), exact JSON field structures for SWIFT_REPORT.json and CHANGE_RECORD.json, verbatim agent dispatch payloads with specific questions, exact AskUserQuestion wording and option sets, and concrete table formats. Copy-paste ready and covers the common cases across all three routing paths.

5 / 5

Workflow Clarity

Clear sequence (Step 0 through Step 4A/B/C) with explicit validation checkpoints: plan approval gates, test self-healing with escalation ('up to 3 attempts per failing test... If the same test fails 3 times, escalate'), and review verdicts (PASS / PASS WITH WARNINGS / NEEDS FIXES) with re-run after fixes. However, Step 2's subsections 2a-2d collide with separate top-level sections also named 'Step 2b: Arness-Sketch Offer' and 'Step 2c: Load Sketch Manifest' that appear after 'Step 2d', making the intended order ambiguous.

4 / 5

Progressive Disclosure

Good structure with three well-signaled, one-level-deep references (complexity-criteria.md, swift-plan-template.md, swift-review-checklist.md) that all exist in the bundle, called out as blockquote 'Read...' notes. Gaps: the duplicated preference machinery and the CHANGE_RECORD schema are inlined rather than split out, and several referenced paths point outside this bundle (arn-code-ensure-config and arn-code-execute-plan files), so overall organization is good but not exemplary.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 with explicit what/when structure and rich natural trigger phrases. The main weaknesses are mild: a few concrete capabilities (the plan/report/change-record artifacts) are left unstated, and several generic trigger terms ('just do this', 'small change') create overlap risk with closely related pipeline skills.

Suggestions

Tie the generic triggers ('just do this', 'small change', 'quick task') to the 1-8-file scope or narrow them, so they cannot fire for sibling pipeline skills (e.g., bug-spec) on similar phrases.

Mention the concrete deliverables (SWIFT_<name>.md plan, SWIFT_REPORT.json, CHANGE_RECORD.json) in the 'what' clause to round out capability coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('architectural assessment, targeted testing, and pattern compliance review' for 'a small feature or enhancement (1-8 files)'), but omits the concrete deliverables (SWIFT plan, SWIFT_REPORT.json, CHANGE_RECORD.json) and the 'Bridges the gap' sentence is meta-positioning rather than a capability. It exceeds the 1-2-action anchor at 3 but falls short of the comprehensive coverage at 5.

4 / 5

Completeness

Explicitly answers both: 'what' ('a lightweight, pattern-aware implementation for a small feature or enhancement (1-8 files)... Includes architectural assessment, targeted testing, and pattern compliance review') and 'when' ('This skill should be used when the user says...' followed by concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage with synonyms: 'small change', 'simple change', 'quick feature', 'swift fix', 'quick task', 'just do this', 'just implement this', 'implement this quickly', 'add this quickly', plus both the natural phrase 'arness code swift' and the skill name 'arn-code-swift'. These are phrases a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

The niche is somewhat specific (swift tier, 1-8 files, named triggers 'arness code swift'/'arn-code-swift'), but several triggers are so generic ('just do this', 'small change', 'quick task') that they would plausibly fire for sibling pipeline skills (e.g., bug-spec or feature-spec). This matches the 'somewhat specific but could still overlap with similar skills' anchor better than the 'minor overlap risk' anchor at 4.

3 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (617 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

AppsVortex/arness

Path

plugins/arn-code/skills/arn-code-swift/SKILL.md

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.