Install
npx skills add vercel-labs/autoshipWho it's for
This fits people whose repository already uses changesets for versioning and who want AI-generated release notes plus an automated changeset release flow. The official repository is https://github.com/vercel-labs/autoship It describes itself as CLI tool to automate changeset-based releases with AI-generated descriptions. The prerequisites are strict: Node.js 18+, Git, a GitHub CLI (gh) already authenticated to the target repository, and the environment variable AI_GATEWAY_API_KEY. The target repository must use changesets. If any item is missing, do not turn the first try into a real release.
It fits a reversible drill in a repository you are allowed to change. It does not fit cutting into a production repository that does not use changesets. The material writes several Supported interfaces; the body does not expand that list, and you must not infer that an unlisted interface is necessarily unavailable.
First try in 3 minutes
Check the project conditions first, then install the skill. The official skill-install command is:
npx skills add vercel-labs/autoship
This is the skill-install command the material gives. Confirm the current directory may receive skill configuration, then run it. The side effect is installing the autoship skill into the current agent environment. After install, first see whether the skill can be invoked; do not release immediately.
Low-risk task: in an agent that can already run this skill, only check — confirm this machine’s Node.js is 18+, git and gh work, gh has permission on the target repository, AI_GATEWAY_API_KEY is already in the environment, and the target repository really uses changesets. Stop the change there. Success signal: all of those checks pass and the skill is installed. If a check fails, do not switch to an installer that never appears, and do not invent a key value.
If the checks pass, and the target repository is a drill repo you have explicitly allowed writes to, only then consider the official example:
npx autoship add myproject
The material writes the repository name as myproject; run it only after you map that name to a repository you can access that already uses changesets. Before you run it, confirm again you will not release to a production channel. Success signal: the repository is added to autoship, not that it has already been published to a registry.
Use cases
Case 1: Install the skill first and only run the release prechecks. This matches npx skills add vercel-labs/autoship and the conditions Node.js 18+, Git, gh, AI_GATEWAY_API_KEY, and changesets. It fits people who are not yet sure the repository qualifies. The material does not write the output format of a check command; what you can confirm is that these conditions must all be true at once. Do not write case 1 as if release notes were already generated.
Case 2: Add a repository that already uses changesets into autoship, preparing a release with AI descriptions. This matches npx autoship add myproject and automate changeset-based releases with AI-generated descriptions. It fits people whose prechecks already passed and who only still need to register the repository. The material does not write how to preview notes, how to undo, or how to skip AI; what you can confirm is only “add the repository first.” No publish or rollback command appears; do not invent one.
Limits
Repositories without changesets are outside the material’s coverage. AI_GATEWAY_API_KEY is a required environment-variable name; the material does not write an application entry or a free quota. Do not paper over it with a placeholder key. gh must already be authenticated to the target repository; the material does not write organization policy or a fine-grained permission model. The changesets docs point to https://github.com/changesets/changesets That only proves the versioning strategy depends on it, not that autoship has already initialized changesets for you. Do not initialize a production release on the first try. The material gives no other install command.