메뉴
Use when the user wants a full launch video / hero video / 30-90s product announcement composing demo footage, logo, and copy (e.g. "/launch-video", "make the launch video for DashClaw").
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ucsandman/claude-skills --skill launch-video명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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 | launch-video |
| description | Use when the user wants a full launch video / hero video / 30-90s product announcement composing demo footage, logo, and copy (e.g. "/launch-video", "make the launch video for DashClaw"). |
REQUIRED BACKGROUND: marketing-studio skill. Work in C:\Projects\animations.
Produces: out/<brand>/launch.mp4 — ~45s five-act composition: logo reveal ->
hook headline -> live demo -> feature beats (1-3) -> end card, over the brand's
background loop.
docs/templates/DIRECTION.md, kill two with its kill questions, and record the
survivor + its signature move in out/<brand>/marketing/direction.md. Skip only if
that file already exists for this version.background_loop scene per brand; PLAYBOOK seam rules),
demo capture + telemetry (product-demo skill steps 1-4), feature screenshots.scripts/build-<brand>-launch-props.mjs from the
noban one — it is the copy's source of truth (headline, feature lines, CTA; no em
dashes) and pulls telemetry from the demo props so they never drift. Run it.studio/src/lib/launchTiming.ts (shared with
calculateMetadata — never duplicate the math; adjust constants there if pacing
changes, and its vitest tests with them).out/<brand>/launch-v1.mp4, -v2,
... The director loop is render -> watch -> write your own defect list -> fix ->
re-render as a NEW versioned file (notes are symptoms, not specs — translate before
fixing). npx remotion render LaunchVideo out/<brand>/launch-vN.mp4 --props=props/<brand>-launch.json (~1350 frames, minutes).out/<brand>/launch.mp4 — mission-control and
review-in-magnetic expect that exact path. Deliver per marketing-studio.