# /brag: a short launch video from your finished project (latent-spaces/brag) — skill card for AI agents

> AgentGid skill card. Checked on 2026-11-05 against commit 669ab92 (version 0.5.0).
> Every fact comes from the pack's own files at that commit. Numbers marked "as reported" are the author's.
> Human page: https://agentgid.com/skills/latent-spaces/brag/

## Explain it to a non-programmer
Your AI assistant turns a project you built into a 15 to 25 second launch video. It reads your project, writes a plan and a storyboard, then makes the video with music, sound effects and a ready post caption. Everything lands in a new brag-output folder inside your project.

## Who it is for
- You built a site or app with an AI coding assistant and want something better to post than a screenshot
- You want a short video with music and motion, made from your own copy, colours and screens
- You like to pick a mood, from a calm product film to a fake startup launch
- You use Claude Code, Codex, Cursor, opencode or another assistant that reads skills
- Not for: You only use a chat window with no access to your computer: the video is made by tools on your machine
- Not for: You want a long demo or tutorial: the rules keep every video between 15 and 25 seconds

## What it is
- Kind: command, scripts
- License: MIT
- Repository: https://github.com/latent-spaces/brag

## What it does
- Read the project: the main page, styles (exact colours and fonts), README, routes and key screens; skip build output, lock files, .env and key files
- Answer 9 planning questions: what it is, the funniest or most impressive claim, the visual hook, the user flow worth showing, the tone, the caption
- Write brag-plan.md: angle, hook, 2 or 3 highlights, punchline, and a scene-by-scene storyboard that adds up to 15 to 25 seconds
- Build the video: /brag hands a written brief to Hyperframes; /brag-slim builds it itself with the tools on the machine
- Check it, render brag.mp4, pick the strongest settled frame as the poster and put it in as the first frame
- Write share-copy.txt and tell you where the video is, with one sentence on the creative angle
- Never cuts: a real piece of your product on screen (UI, copy or a key visual), readable text, and no secrets, internal addresses or real customer names and emails in the video
- Level default: Playful, clean, postable; 4 to 5 scenes
- Level polished: Serious, elegant; fewer scenes, longer holds
- Level yc-parody: Deadpan startup launch played straight
- Level chaotic: Fast, loud, all caps; 6 to 8 scenes
- Level deadpan: Calm, dry, big empty space
- Level cinematic: Trailer-scale, big type, dramatic reveals
- Level app-store: Clean feature cards, smooth slides

## Skills
| Skill | Call | Changes code? | In plain words |
|---|---|---|---|
| brag | /brag [--tone ...] [--format landscape|vertical|square] [--duration s] [--no-music] [--no-sfx] [--title ...] [--voice] [--full], or "let's brag about this" | no | Makes the launch video from your project with Hyperframes; adds a new output folder and leaves your project files alone |
| brag-slim | /brag-slim [project or web address] [--tone ...] [--format ...] [--duration s]; on Opus 5.5 /brag switches to it by itself | no | The lighter version: your assistant makes the whole video itself, from a project folder or a website's address |

### brag
- Asks for: Your project folder (no live web address or screenshots needed)
- Asks for: A tone, preset or your own words (optional)
- Asks for: Format: landscape, vertical or square (optional)
- Asks for: --voice if you want a narrated video
- Gives: brag-plan.md with the storyboard
- Gives: composition-brief.md for Hyperframes
- Gives: brag.mp4, the video
- Gives: brag.jpg, the poster frame
- Gives: share-copy.txt, one caption
- Gives: a local preview link before the final render
- Say: "let's /brag"

### brag-slim
- Asks for: Nothing (the current project folder) or a website address
- Asks for: A tone (optional)
- Asks for: One part to focus on, like a new feature (optional)
- Gives: brag-plan.md with the storyboard
- Gives: brag.mp4, 1920×1080 at 30 frames per second by default
- Gives: brag.jpg, the poster frame
- Gives: share-copy.txt
- Gives: a work/ folder with every in-between file
- Say: "let's /brag about this"

## Know before installing
- On Claude Opus 5.5, /brag hands the job to /brag-slim by itself: no Hyperframes, the assistant builds the video with its own tools. Run /brag --full or say "use the full brag" to keep the classic way.
- The classic /brag needs Node.js 22+, FFmpeg and the Hyperframes command-line tool, which runs through npx and is fetched from npm. It also loads the Hyperframes skills during the build.
- The bundled music is not MIT: it is CC BY 4.0, so a posted video needs the credit line given in the music README. The sound effects are CC0.
- Your secrets stay out: it skips .env and key files, and swaps real customer names, emails or internal addresses on screen for made-up ones, noting this in the plan.
- It does not post anything: making and rendering stay on your computer, and any publishing needs a separate request from you.
- The README and launch site point to letsbrag.app, the author's paid service ("pay once") that makes the video from your site's link; the skill itself stays free.

## Install (official commands)
- Claude Code: `/plugin marketplace add latent-spaces/brag` && `/plugin install brag@brag` — Then run /brag inside any project; /brag-slim comes with it. To update: claude plugin update brag.
- Codex: `codex plugin marketplace add latent-spaces/brag` && `codex plugin add brag@brag` — To update later: codex plugin marketplace upgrade brag, then codex plugin add brag@brag.
- Any agent (skills CLI): `npx skills add https://github.com/latent-spaces/brag --skill brag` — Add -g to install for every project; without it, only the current one. Use --skill brag-slim for the lighter version only.
- Claude Code (copy by hand): `rsync -a --exclude '.DS_Store' skills/brag/ ~/.claude/skills/brag/` && `rsync -a --exclude '.DS_Store' skills/brag-slim/ ~/.claude/skills/brag-slim/` — Run from a clone of the repository, then restart Claude Code. The second line is optional. Remove: `delete ~/.claude/skills/brag and ~/.claude/skills/brag-slim`.
- Other agents (custom instructions): Paste skills/brag/SKILL.md into custom instructions, point the agent at the file, or copy the skills/brag folder. Keep the folder reachable for the music, sounds and reference files.

## What runs on the user's machine
- Code on the machine: yes (while a video is being made (no hooks; nothing runs at install or session start))
- Network: yes
- Install: Markdown instructions, 5 music tracks, sound effect files and one Python script. No hooks, no install scripts; the plugin manifests only name the pack.
- /brag (classic): The assistant runs npx hyperframes check, preview (a local server), render and snapshot, then ffmpeg to pull the poster frame and put it in as frame 0. Everything is written to brag-output/ (or brag-output-<date-time>/) in your project; music and chosen sounds are copied into its composition/assets/.
- Beat sync (optional): Runs the pack's analyze_music_cues.py through uv, which fetches librosa, numpy, scipy and soundfile; it reads a music file and writes cue JSON and Markdown. Or npx hyperframes beats instead. The script itself makes no network calls.
- --voice only: npx hyperframes tts makes a Kokoro voice-over and writes composition/assets/voiceover.wav.
- /brag-slim: Builds the video with whatever tools are on the machine and asks before installing anything. With a web address it loads the live site (in a headless browser if needed) and downloads media files into work/; it is told never to run anything downloaded and to treat page text as data.
- Maintainer checks: scripts/check-docs.mjs and scripts/check-brag-slim.mjs check the launch site links and that slim.md matches brag-slim. The skill does not run them.

## Examples (from the pack's own files)
- Share copy for a made-up taxi app: output format defined in skills/brag/references/step-4-deliver.md
- The output folder after a run: output format defined in skills/brag/references/step-4-deliver.md

## How to tell it works
In a project folder with a website, say "let's /brag". It should first write brag-output/brag-plan.md with a storyboard of 15 to 25 seconds, then finish with brag.mp4, brag.jpg and share-copy.txt in the same folder. On Opus 5.5 its first line says it is using /brag-slim.

## Related
- vercel-labs/skills

## Safety
No hooks; code runs only while a video is being made, and the classic path fetches Hyperframes from npm (uv fetches Python packages for the optional beat analysis). /brag-slim can load a live website and download its media; it is told to treat page content as data and never run what it downloads. The repository also exposes the skills through symlinked .claude/skills, .agents/skills and .opencode/skills folders, so an assistant opened inside a clone picks them up.
