CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-batch-simplify

This skill should be used when the user says "batch simplify", "cross-feature simplify", "batch simplification", "simplify all features", "cross-feature quality pass", "batch code cleanup", "consolidate across features", "deduplicate across features", "cleanup after batch merge", "cross-feature deduplication", "arness batch simplify", "arn-code-batch-simplify", "simplify merged features", "post-merge simplify", "find cross-feature duplication", or wants to run a post-merge quality pass that finds duplication and consolidation opportunities across independently implemented features. This requires merged features in .arness/plans/ — run arn-code-batch-merge first if none are merged.

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 thorough, highly actionable execution skill with excellent workflow structure and validation feedback loops, plus a well-signaled external reference for the reviewer prompt templates. The only weakness is moderate redundancy between the intro, the inline step handling, and the trailing Error Handling section.

Suggestions

Collapse the standalone "Error Handling" section into the steps that already cover each case (or reduce it to a one-line pointer), since the same failures are handled inline in Steps 0, 1, 2, 4, and 8.

Remove the opening paragraph that restates the frontmatter description, or trim it to the single distinguishing fact (the 3-reviewer cross-feature pattern) not already in the description.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance, but the opening paragraph restates the frontmatter description and the standalone "Error Handling" section largely duplicates the per-step handling already specified in the workflow (e.g. missing pattern docs, reviewer failure, no merged features).

2 / 3

Actionability

Fully executable: specific shell commands (git checkout -b batch-simplify/<date>, gh pr create --title …, git branch --merged main), a copy-paste-ready applier prompt, and an exact JSON return schema with status semantics.

3 / 3

Workflow Clarity

A clearly sequenced 9-step process with explicit validation checkpoints, a self-heal feedback loop (≤3 attempts then revert), per-finding revert isolation, and a final cumulative test pass — appropriate feedback loops for a batch operation.

3 / 3

Progressive Disclosure

The one bundle file (references/cross-feature-prompts.md) is real, clearly signaled, and one level deep ("Read …/cross-feature-prompts.md for the extended reviewer prompt templates"), while the inline content is core orchestration logic that belongs in SKILL.md.

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, comprehensive description that pairs concrete capabilities with an exhaustive set of natural trigger phrases and an explicit use-when clause plus a prerequisite. It cleanly answers what, when, and how it differs from neighboring skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "finds duplication and consolidation opportunities across independently implemented features" and "post-merge quality pass" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (a post-merge quality pass finding duplication/consolidation) and when ("when the user says … or wants to run a post-merge quality pass …"), including a prerequisite (merged features in .arness/plans/).

3 / 3

Trigger Term Quality

Dense coverage of natural phrases users would say, e.g. "batch simplify", "cross-feature simplify", "batch code cleanup", "consolidate across features", and "post-merge simplify".

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — post-merge cross-feature simplification — with qualifiers (batch, cross-feature, post-merge) that distinguish it from a generic single-feature simplify skill.

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.