How do I install the Ship It skill?

Run npx skillmds@latest add ucsandman/ship-it in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ship It safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ship It?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ship It free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ship It?

ucsandman (@ucsandman) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ship It by ucsandman — Agent Skill

Name: Ship It
Author: ucsandman

Ship It

Ship a product end to end — render marketing assets with the marketing studio (/marketing), then run the launch/ flow (/launch) with videos attached to X, LinkedIn, Bluesky and YouTube posts. Run from the product's repo.

ucsandman 58655c1 2.9 KB Updated Sep 17, 2026

File contents

/ship-it — develop → public, one command

Run from the product repo you want to ship. Studio root = ${CLAUDE_SKILL_DIR}/../.. (rendering). Its launch CLI lives at ${CLAUDE_SKILL_DIR}/../../launch (distribution) — run subcommands via node "${CLAUDE_SKILL_DIR}/../../launch/dist/index.js" <cmd> or npx --prefix "${CLAUDE_SKILL_DIR}/../../launch" launch <cmd>, from the product repo so its .launch/ state lands there. This skill is the pipeline.

Steps

Find the brand + kit. Brand id = the product's brand in ${CLAUDE_SKILL_DIR}/../../brands/<id>.json (ask only if ambiguous). Kit = <product>/marketing/assets/<brand>/postkit/manifest.json.
Render if needed. If the manifest is missing, run /marketing first (full pipeline, its own approval gates). If it exists, show its generatedAt and ask: reuse or re-render? Staleness is the user's judgment call, never a heuristic.
Launch flow. In the product repo, run the launch sequence — launch init (if no .launch/launch.config.json), then research, copy scaffold/fill, validate. Wire the kit: either set postkitDir in the config (the dashboard marketing tab does this with a picker) or pass --kit "<product>/marketing/assets/<brand>/postkit" to launch post.
Dry-run, then post. launch post <dir> --all --dry-run and show the user the previews — X and LinkedIn must show the video upload step. Live posting only after the user confirms, through the normal gates (ledger, validation, typed confirmation in the dashboard).
Manual platforms. TikTok / Shorts / Instagram are manual by design. Point the user at the dashboard marketing tab (Open folder per platform) or the kit's POST.md checklists. YouTube is NOT manual any more: launch post --all --live uploads to it whenever the three YOUTUBE_* keys are set. Uploads land private unless YOUTUBE_PRIVACY says otherwise -- say so out loud before any live run, and confirm it the same way as every other api-mode platform.

Rules

Never skip the dry-run step. Never post live without explicit user confirmation.
If the kit manifest promises a video whose file is missing, posting refuses — fix by re-running render-matrix.mjs <brand> --project <product> --production and build-postkit.mjs <brand> --project <product> --production, not by unwiring the kit.
Live publishing remains blocked until the current media, production plan, per-row evidence, and named full-film review are hash-bound and PASS. A dry run may preview an incomplete kit but never weakens the live gate.
Drafts own the copy; the kit contributes media. Do not paste kit captions over validated drafts.

---name: ship-itdescription: Ship a product end to end — render marketing assets with the marketing studio (/marketing), then run the launch/ flow (/launch) with videos attached to X, LinkedIn, Bluesky and YouTube posts. Run from the product's repo.---# /ship-it — develop → public, one commandRun from the product repo you want to ship. Studio root = `${CLAUDE_SKILL_DIR}/../..`(rendering). Its launch CLI lives at `${CLAUDE_SKILL_DIR}/../../launch` (distribution) —run subcommands via `node "${CLAUDE_SKILL_DIR}/../../launch/dist/index.js" <cmd>` or`npx --prefix "${CLAUDE_SKILL_DIR}/../../launch" launch <cmd>`, from the product repo soits `.launch/` state lands there. This skill is the pipeline.## Steps1. **Find the brand + kit.** Brand id = the product's brand in `${CLAUDE_SKILL_DIR}/../../brands/<id>.json` (ask only if ambiguous). Kit = `<product>/marketing/assets/<brand>/postkit/manifest.json`.2. **Render if needed.** If the manifest is missing, run `/marketing` first (full pipeline, its own approval gates). If it exists, show its `generatedAt` and ask: reuse or re-render? Staleness is the user's judgment call, never a heuristic.3. **Launch flow.** In the product repo, run the launch sequence — `launch init` (if no `.launch/launch.config.json`), then research, copy scaffold/fill, validate. Wire the kit: either set `postkitDir` in the config (the dashboard marketing tab does this with a picker) or pass `--kit "<product>/marketing/assets/<brand>/postkit"` to `launch post`.4. **Dry-run, then post.** `launch post <dir> --all --dry-run` and show the user the previews — X and LinkedIn must show the video upload step. Live posting only after the user confirms, through the normal gates (ledger, validation, typed confirmation in the dashboard).5. **Manual platforms.** TikTok / Shorts / Instagram are manual by design. Point the user at the dashboard marketing tab (Open folder per platform) or the kit's `POST.md` checklists. YouTube is NOT manual any more: `launch post --all --live` uploads to it whenever the three YOUTUBE_* keys are set. Uploads land private unless `YOUTUBE_PRIVACY` says otherwise -- say so out loud before any live run, and confirm it the same way as every other api-mode platform.## Rules- Never skip the dry-run step. Never post live without explicit user confirmation.- If the kit manifest promises a video whose file is missing, posting refuses — fix by re-running `render-matrix.mjs <brand> --project <product> --production` and `build-postkit.mjs <brand> --project <product> --production`, not by unwiring the kit.- Live publishing remains blocked until the current media, production plan, per-row evidence, and named full-film review are hash-bound and PASS. A dry run may preview an incomplete kit but never weakens the live gate.- Drafts own the copy; the kit contributes media. Do not paste kit captions over validated drafts.

Frequently asked questions