CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-shipping

This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done", "arn-shipping", or wants to commit, push, and optionally create a pull request. Handles branching, staging, committing, pushing, and PR creation as a single guided flow. Chains from arn-implementing at completion.

72

Quality

90%

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

87%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 an efficient, actionable thin orchestration wrapper with a clear step sequence and well-organized sections. Its main gap is the absence of an explicit validation checkpoint before the destructive commit/push, since verification is delegated entirely to the invoked sub-skill.

Suggestions

Add a brief explicit precondition check (e.g., confirm a non-clean tree / commits ahead before invoking the ship skill) so the destructive push has a visible checkpoint at this orchestration level.

Make the Step 0 completion signal explicit (e.g., "Only proceed to Step 1 once ensure-config reports success") to tighten the validation feedback loop.

DimensionReasoningScore

Conciseness

The body is lean: it delegates all real work to arn-code-ship, assumes Claude's competence, and avoids explaining concepts Claude already knows, with every section earning its place.

3 / 3

Actionability

Guidance is concrete and executable: a specific reference path ("${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/step-0-fast-path.md"), an explicit invocation ("Skill: arn-code:arn-code-ship"), and a copy-paste progress display block.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 0 -> Step 1 -> Step 2) with an error-handling section, but shipping is a destructive operation (commit/push) and validation is delegated to the sub-skill with no explicit in-body checkpoint, capping clarity at 2.

2 / 3

Progressive Disclosure

This simple under-50-line skill is well-organized into clear sections and references only one one-level-deep external file, matching the simple-skills allowance for a top score.

3 / 3

Total

11

/

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.

The description is strong: it states concrete actions and provides explicit, extensive trigger guidance covering both what and when. Its only weakness is a set of overly generic trigger terms ("done", "finalize", "wrap up") that raise conflict risk with other skills.

Suggestions

Trim or qualify generic triggers like "done", "finalize", "wrap up", and "finish up" that users say in many non-shipping contexts, to reduce overlap with other skills.

Lead with the distinctive invocation (e.g., "arn-shipping" / "arness shipping") earlier in the description so the skill's niche is immediately clear.

DimensionReasoningScore

Specificity

"Handles branching, staging, committing, pushing, and PR creation as a single guided flow" lists multiple concrete actions rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It explicitly answers both what ("Handles branching, staging, committing, pushing, and PR creation") and when ("This skill should be used when the user says..."), with explicit trigger guidance.

3 / 3

Trigger Term Quality

It enumerates a broad set of natural phrases users would say ("shipping", "ship it", "create PR", "commit and push", "wrap up", "ready to ship"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Distinctive names like "arn-shipping" and "arness shipping" establish a niche, but generic triggers ("done", "finalize", "wrap up", "finish up") could overlap with other skills, so it is not clearly conflict-free.

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