菜单
Ship a product end to end — render marketing assets with the animations studio, then run the launch-engine flow with videos attached to X and LinkedIn posts. Run from the product's repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ucsandman/claude-skills --skill ship-it命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Fill a repo's .env from the machine's credential stores without ever reading or printing a secret value. Use when the user says "/secrets", "fill in the .env", "get the keys", "wire up the credentials", "pull the secrets from offlocal", or when launch.py / a dev server refuses to start because keys are still on example values.
Use when finished work needs to go out — the user says "ship it", "update docs commit and push", "commit and push", or asks "anything else we need to update?" before a release or at the end of a work session.
Use before writing a new skill, before saying no skill exists for something, or whenever Wes asks "do I have a skill for X" / "is there a skill that…". Also use when a task sounds like it needs a capability that might already be installed (spreadsheets, PDFs, docx, scraping, copywriting, a framework, a provider) — most of this machine's skills are NOT in the session listing, so "I don't see one" is not evidence that none exists.
基于 SOC 职业分类
正在显示 SKILL.md
| name | ship-it |
| description | Ship a product end to end — render marketing assets with the animations studio, then run the launch-engine flow with videos attached to X and LinkedIn posts. Run from the product's repo. |
Run from the product repo you want to ship. Engines: the animations studio at
C:\Projects\animations (rendering) and launch-engine at C:\Projects\launch-engine
(distribution). Repos stay separate; this skill is the pipeline.
C:\Projects\animations\brands\<id>.json
(ask the user if ambiguous). Kit = C:\Projects\animations\out\<brand>\postkit\manifest.json./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 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 C:\Projects\animations\out\<brand>\postkit to launch 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).POST.md checklists.render-matrix.mjs + build-postkit.mjs in the animations repo, not by unwiring the kit silently.