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.
84
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that excels at listing explicit trigger terms and concrete actions. The 'what' and 'when' are both clearly addressed. The main weakness is that some trigger terms ('done', 'finalize', 'finish up', 'wrap up') are overly generic and could cause false matches with unrelated skills.
Suggestions
Consider removing or qualifying overly generic triggers like 'done', 'finalize', 'finish up', and 'wrap up' to reduce conflict risk with other skills — e.g., 'done with code changes' instead of just 'done'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: branching, staging, committing, pushing, and PR creation. Also mentions it operates as 'a single guided flow' and chains from another skill. | 3 / 3 |
Completeness | Clearly answers both 'what' (handles branching, staging, committing, pushing, and PR creation as a single guided flow) and 'when' (extensive explicit trigger list at the beginning of the description). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations like 'shipping', 'ship it', 'ship', 'create PR', 'open pull request', 'push and PR', 'commit and push', 'wrap up', 'finalize', 'finish up', 'done', and more. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | While the shipping/PR-specific terms are distinctive, some triggers like 'done', 'finalize', 'finish up', and 'wrap up' are very generic and could easily conflict with other skills that handle task completion in different contexts. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestration skill with clear workflow sequencing and appropriate delegation to sub-skills. Its main weakness is some unnecessary meta-commentary about its own design philosophy that doesn't help Claude execute the task. The error handling section partially restates what the invoked skill already handles, adding tokens without value.
Suggestions
Remove design-philosophy statements like 'This is a thin orchestration wrapper' and 'It MUST NOT duplicate arn-code-ship logic' — these are author notes, not actionable instructions for Claude.
Trim the error handling section to only cover errors this skill can actually act on (remove the bullet about 'Nothing to ship' since it explicitly says no action is needed).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary meta-commentary (e.g., 'This is a first-citizen entry point', 'This skill is a thin orchestration wrapper', 'It MUST NOT duplicate arn-code-ship logic'). These are design notes for the skill author, not actionable instructions for Claude. The error handling section also restates things the invoked skill already handles. | 2 / 3 |
Actionability | The skill provides a clear sequence of actions (read config, invoke ship skill, present handoff message), but it's largely delegation — the actual concrete work is deferred to other skills. The progress indicator ASCII art is a nice touch, but there's no executable code or commands beyond skill invocations and a file path to read. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, explicit prerequisites (Step 0), a clear invocation point (Step 1), and a defined completion handoff (Step 2). Error handling covers the main failure modes with specific recovery actions. For an orchestration wrapper, this is well-structured. | 3 / 3 |
Progressive Disclosure | The skill appropriately delegates to referenced skills (arn-code-ship, ensure-config) rather than inlining their logic. References are one level deep and clearly signaled with file paths and skill invocation syntax. The structure is well-organized for a thin orchestration layer. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- AppsVortex/arness
- Commit
1fe948f
- 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.