Skip to main content
skill CX Codex

coco-ads — Claude Code skill: turn code into launch videos

Claude Code skill that turns your project code into a short launch video (15–25 seconds). Triggers on /coco-ads or phrases like "make a launch video".

MIT ★ 328 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add coco-research/coco --skill coco-ads -a claude-code
Open on GitHub

What coco-ads does

Reads project files, plans the concept and script, then hands the composition to HyperFrames — HeyGen's local HTML render engine. The video is assembled locally, without sending code to the cloud. Seven tone presets (default, polished, yc-parody, chaotic, deadpan, cinematic, app-store) range from playful to dramatic. You can specify a custom direction: "make it feel like a fake 2016 startup launch."

Requires Node 22+, FFmpeg on PATH, and the HyperFrames CLI (npx hyperframes …). Music is not bundled: the skill is tuned for "Happy Beats / Business Moves" (ende.app), which you download yourself — instructions in assets/music/README.md; SFX are included. Output goes to coco-ads-output/: the plan (coco-ads-plan.md), composition, render (brag.mp4), and share copy. Without FFmpeg or Node 22, the skill will not run.

What it helps with

  • create a launch video from project code for social media
  • generate a short promo clip without screenshots or live URLs
  • render video locally using HyperFrames
  • build a script and storyboard from repository files
  • package a finished feature into a 15–25 second video with music and text

Example prompts for the agent

  • Make a launch video from this project
  • Run /coco-ads --tone chaotic --format vertical
  • Create a promo in YC parody style

How to install coco-ads

1Skills CLI (Vercel)

npx skills add coco-research/coco --skill coco-ads -a claude-code

2Manually: put the files in place

~/.claude/skills/coco-ads/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/coco-ads/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about coco-ads

How to install coco-ads in Claude Code?

Run npx skills add coco-research/coco --skill coco-ads -a claude-code, then check ~/.claude/skills/coco-ads/SKILL.md.

What does coco-ads do?

Reads project code, plans the video concept and script, builds the composition via HyperFrames, and renders an MP4 locally — no data sent to the cloud.

Why are Node 22 and FFmpeg required?

HyperFrames needs Node 22+ to run and FFmpeg to render video. Without them, the skill cannot produce the final MP4.

Source text

SKILL.md · MIT
---
name: coco-ads
description: Turn the project you just shipped into a short, polished, shareable launch video (an "ad") using HyperFrames. Use when someone says "/coco-ads", "make a launch video", "brag about this", "turn this into a promo", "make an ad for this", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed. Renders locally.
argument-hint: "[--tone <preset|freeform>] [--format landscape|vertical|square] [--duration <s>] [--no-music] [--title <name>]"
user-invocable: true
domain: design
---

# /coco-ads — launch videos from your repo

You built it. Now let CoCo make the ad.

`/coco-ads` turns the current project into a short (15–25s), polished, shareable launch video using the HyperFrames toolchain, rendered **locally**. It is narrow, opinionated, and fast.

> **Credit / lineage.** This skill adapts the launch-video flow from [**brag** by Shunit Haviv](https://github.com/latent-spaces/brag) and runs on the [**HyperFrames**](https://www.npmjs.com/package/hyperframes) HTML-composition + render engine by HeyGen. Music is not bundled: the skill is tuned for "Happy Beats / Business Moves" by ende.app, which you download yourself (see [`assets/music/README.md`](assets/music/README.md)); bundled SFX are CC0 (Kenney.nl). See [`CREDITS.md`](../../CREDITS.md). Re-implemented in CoCo's voice with attribution. Upstream `brag` is MIT-licensed (Copyright (c) 2026 Shunit Haviv Hakimi); its notice is retained at [`LICENSE`](LICENSE) in this skill directory.

## Requirements

The render path is fully local (HeyGen cloud/Lambda paths are never used). It needs:

- **Node 22+** and **FFmpeg** on `PATH`.
- The **HyperFrames** CLI, run via `npx hyperframes …` (auto-fetched on first use). The composition skills install once with `npx hyperframes skills`.
- A quick environment check: `npx hyperframes doctor` (Chrome headless-shell + FFmpeg). "Docker not running" is fine — Docker is only for distributed cloud renders, which this skill does not use.

No data leaves the machine on the default render path. If `GEMINI_API_KEY` is set, the optional snapshot frame-analysis would call Gemini — keep it off (`--describe false`) when bragging about anything you would not paste in public.

## What this skill does

1. Reads the current project code to understand the app.
2. Plans a short concept specific to this project.
3. Scripts and storyboards the video.
4. Hands a focused composition brief to HyperFrames.
5. Validates, renders locally, and writes share copy.

## Parsing the invocation

```
/coco-ads
/coco-ads --tone chaotic
/coco-ads --tone polished --format vertical
/coco-ads this. Make it feel like a ridiculous startup launch.
```

| Option | Values | Default |
|---|---|---|
| `--tone` | preset or freeform description | inferred |
| `--format` | `landscape`, `vertical`, `square` | `landscape` |
| `--duration` | seconds | auto (15-25s) |
| `--no-music` | flag | music on |
| `--no-sfx` | flag | sfx on |
| `--title` | string | inferred from project |

Tone can be a preset (`default`, `polished`, `yc-parody`, `chaotic`, `deadpan`, `cinematic`, `app-store`) or a creative direction such as "fake Series A launch from 2016". When the user gives freeform direction, map it to the nearest preset for pacing and structure, but preserve the user's direction in the plan and composition brief.

---

## Output directory

By default, output goes to `coco-ads-output/`. To avoid overwriting previous runs, use a timestamped directory (`coco-ads-output-YYYY-MM-DD-HHmmss/`) when the user asks for a new run or one already exists. Generate the timestamp once at the start of the run and use it consistently for the plan, brief, composition, render, and share copy. Keep `coco-ads-output/` out of version control.

---

## Step 1: Inspect the project

**Read:** [references/step-1-inspect.md](references/step-1-inspect.md)

Scan the project directory and extract what you need to plan the video.

**Gate:** You can answer all 9 questions in the planning rubric.

---

## Step 2: Plan and storyboard

**Read:** [references/step-2-plan.md](references/step-2-plan.md)

Write `<output-dir>/coco-ads-plan.md`. Answer the planning rubric, commit to a creative angle, and write the beat-by-beat storyboard (scenes, text, timing, transitions, SFX cues). Include a compact `Music cue guidance` section when music is selected.

**Gate:** `<output-dir>/coco-ads-plan.md` exists with a full storyboard; scene durations sum to 15–25 seconds.

---

## Step 3: Hand off to HyperFrames

**Read:** the installed HyperFrames composition skills (`npx hyperframes skills` if absent), then [references/step-3-compose.md](references/step-3-compose.md) and [references/audio.md](references/audio.md).

Write `<output-dir>/composition-brief.md`, then build the composition in `<output-dir>/composition/`. `/coco-ads` owns product angle, source material, storyboard, tone, format, audio selection, and delivery; HyperFrames owns the concrete composition structure, animation mechanics, and render workflow.

**Gate:** `npx hyperframes lint` passes with zero errors inside `<output-dir>/composition/`.

---

## Step 4: Validate, render, and deliver

**Read:** [references/step-4-deliver.md](references/step-4-deliver.md)

Validate (`npx hyperframes validate` + `inspect`), render to `<output-dir>/brag.mp4`, and write `<output-dir>/share-copy.txt`.

**Gate:** the rendered MP4 exists and share copy is written.

---

## Tone system

Seven presets ship with `/coco-ads`. Each changes scripting energy, pacing, typography personality, and transition style. Presets are defaults, not limits — always allow a freeform creative direction to refine or override.

Full definitions: [references/tones.md](references/tones.md)

| Tone | Energy | One-liner |
|---|---|---|
| `default` | Playful, clean, postable | The good-vibes default |
| `polished` | Serious, elegant | For projects that are not jokes |
| `yc-parody` | Deadpan startup energy | Fake seriousness applied to absurd projects |
| `chaotic` | Fast, loud, aggressive | Over-the-top and unhinged |
| `deadpan` | Calm, dry, understated | The joke is that nothing is a joke |
| `cinematic` | Dramatic, trailer-scale | Big motion, bigger claims |
| `app-store` | Smooth, feature-card clean | Corporate but not boring |

---

## Creative laws

These apply to every video regardless of tone.

**Short.** 15–25 seconds. Not one second more without a reason.

**Readable.** Keep the pace high through motion and cuts, never by flashing text. Every line a viewer must read holds long enough to read it (short label ~0.8s settled; a sentence ~0.3s per word). Fast-in, then hold — never fast-in, then gone.

**Specific.** The video must feel like it was made for this exact project, not any project.

**Show the thing.** At least one scene must display actual UI, copy, or a key visual from the product. No abstract filler.

**No generic SaaS language.** "Streamline your workflow" is banned. Use the project's actual copy and claims.

**The hook is everything.** The first 2 seconds decide whether someone keeps watching. Plan the hook before anything else.

**Funny earns its place.** Humor should come from the project's absurdity, not from trying to be funny.

**Pattern:**
```
Hook (2-3s) → Reveal (2-4s) → 2-3 sharp highlights (5-12s) → Punchline/outro (2-4s)
```

Adapt this. The pattern is a starting shape, not a template.

© coco-research · MIT · coco-research/coco

Similar skills

All skills for Design →

From the same set82

The whole set →
coco-ship coco-ship guides code from branch to GitHub pull request while handling corporate git guards and waiting on CI checks. Blocks direct pushes to main. CX Codex +1 ★ 328repo stars gsd-research-synthesizer gsd-research-synthesizer combines four research agents’ findings into SUMMARY.md and derives recommendations for a project roadmap. It runs as part of /gsd-new-project. CX Codex ★ 328repo stars refactoring-specialist refactoring-specialist cleans up code smells and reduces complexity step by step while maintaining existing behavior through constant test runs. CX Codex ★ 328repo stars code-reviewer code-reviewer — a subagent for code, architecture and security review. Checks SOLID, DDD, vulnerabilities, API design and performance before merging PRs. CX Codex ★ 328repo stars mermaid The command renders Mermaid diagrams (flowcharts, sequence, state, class, ER, XY charts) as SVG, standalone HTML, or terminal ASCII. CX Codex +1 ★ 328repo stars maker-mdap maker-mdap — a Claude Code skill for designing long LLM workflows with fine-grained decomposition, voting, and rejection of suspicious outputs. CX Codex +1 ★ 328repo stars arch Command to build and validate .arch/index.json, which maps each architecture component to the files implementing it. Detects when files and component descriptions have drifted apart. CX Codex +1 ★ 328repo stars develop develop runs a multi-agent build and bugfix pipeline that shards file edits across specialized agents and validates changes with regression evidence. CX Codex +1 ★ 328repo stars

Project sponsors

Companies that keep this analytics open