You finish a project, open the link, and realize the explanation still needs work. What does it do? Which part should someone see first? Why would they care?

Brag is an MIT-licensed skill that helps turn a project's code into a short launch video, with motion, music and sharing copy. There are two routes to understand before installing it: classic Brag and Brag Slim. Official repository.

I would use it to get a first product story on screen, then review every claim and every visible feature before publishing.

What people have actually shared

John Champ posted a Brag test on his CodedVisuals project. His follow-up identifies HyperFrames as the renderer. That is a creator's own test, not my measurement. Original result, follow-up.

Matteo Midena reports a first launch-video take from an AI-managed Obsidian second brain in 12 minutes, using text from his project and a music-synced reveal. That time belongs to his particular run. Matteo's account.

A fresh Opus 5.5 demo from Arjun adds current interest. His “one shot” description is an attributed claim, not a guarantee for your project. Demo post.

The earlier CodedVisuals and second-brain examples are older builds. They help explain the workflow; they should not be presented as launches from this week.

Classic Brag and Brag Slim

Route What to know
Classic Brag Owns the product story and gives HyperFrames a rendering brief
Brag Slim Lean route for Opus 5.5, without HyperFrames or the bundled assets
/brag --full Keeps the classic route when the automatic Slim switch is unwanted

On Opus 5.5, /brag automatically selects Slim. The repo describes a brag-output/ directory containing planning material, sharing copy and the MP4. Review the files produced by the selected route. Current README.

Install the route you want

Inside Claude Code, the documented marketplace route is:

/plugin marketplace add latent-spaces/brag
/plugin install brag@brag

For an agent that supports the skills installer:

npx skills add https://github.com/latent-spaces/brag --skill brag

For Slim only, choose brag-slim as the skill name. The classic route lists Node.js 22+, FFmpeg and the HyperFrames CLI as requirements. Read the selected skill before running it, especially when using another agent. Installation and requirements.

Give it a real product brief

This example brief helps prevent a flashy video from making promises your app cannot keep:

Project: [path and name]
User: [specific person the app helps]
Problem: [what gets difficult without it]
Show these three working features: [list]
Use real interface text and real outputs from the project.
Tone: [calm / playful / polished]
End action: [open the demo / try the app]
Do not invent users, revenue, benchmarks or testimonials.
Show me the story plan and unsupported claims before rendering.

Use a clean demo state. Do not put a private customer name, token or email in the frame just because it appears in the source project.

Review the first take

Watch once without sound: can you understand the product? Then listen without looking: does the pacing help the story? Finally, inspect the text and footage together.

  • Confirm each featured action exists in the app.
  • Check small text at phone size.
  • Read every number and promise against the actual product.
  • Inspect the opening, reveal and final CTA for enough reading time.
  • Check audio levels, music rights and export dimensions.
  • Keep the editable files as well as the final video.

If the story is unclear, correct the product angle before adding more effects. A clearer first sentence can do more than another transition.

FAQ

Does Slim use HyperFrames?

The current README says it does not. Classic Brag uses HyperFrames. Keep the two routes separate in your instructions.

Will my project get the same result as a demo?

That depends on the project, brief, model and render. Use demos to understand the approach, then judge your own output.

Is installing Brag the same as publishing a video?

No. Inspect the generated material and approve the final export before uploading it.

Sources

Checked 1 October 2026. No claim here implies I personally reproduced the cited creator runs.