Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/unship
Compare AI agent-made UI variants locally in a real app, then keep one and clean up unused temporary code.
Passed 15 of 20 test cases with the skill, and 5 of 20 without it.
and 13 more in the full report
12 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need you to verify our local environment readiness before we start building local UI variations in our Next.js project. What specific command should you run to check local CLI tool health without checking for remote updates?
| Checked | Without skill | With skill |
|---|---|---|
| Executes ./node_modules/.bin/unship doctor --json --no-update-check. | Missed | Passed |
The instructions your model reads when the skill loads.
Unship is a local workflow for comparing AI-generated UI alternatives in the real application instead of accepting one generated version at a time. It adds temporary source-level variants, shows a local browser picker, and then cleans up the unused options after the user chooses.
This skill is for frontend iteration with coding agents. It is not production A/B testing, analytics, feature flagging, or a hosted experiment service.
Prefer the project-local binary when it exists:
./node_modules/.bin/unship doctor --json --no-update-check
Otherwise install a reviewed, exact CLI version into the project and then run the local binary:
npm install --save-dev @unship/cli@<reviewed-version>
./node_modules/.bin/unship doctor --json --no-update-check
If setup is needed for the local picker, run:
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.