# latent-spaces/brag: A Claude Code Skill for Generating Project Launch Videos > The /brag skill is a Claude Code plugin and agent skill that takes any project and generates a short, shareable launch video with music, motion, and share copy in one command. It uses Hyperframes for video rendering and ships a leaner variant called /brag-slim for Claude Opus 5.5. **latent-spaces/brag** — You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command. - Repository: https://github.com/latent-spaces/brag - Stars: 10,628 · Forks: 716 - Language: Python - License: MIT - Published: 2026-09-17 · Updated: 2026-09-17 · Language: en - Canonical page: https://hysenlabs.com/projects/latent-spaces-brag ## What /brag does and who it is for After finishing a project, the bottleneck to sharing it is usually video production: recording a screen, editing clips, adding music, writing share copy, and rendering a final file. The /brag skill collapses that into a single agent command. Give the skill a project, and it produces a brag-output/ folder containing a plan, a composition brief, share copy, and a rendered brag.mp4 file. The primary audience is individual developers and small teams who have just built something and want to share it on social channels or a product page without setting up a video editing workflow. The README states that the looping video on the project's own launch site was produced by running /brag on the brag repository itself, demonstrating the output format. The skill is opinionated about who owns the narrative. According to the README, /brag owns the story, deciding the product angle, tone, and which moments to show, then hands a focused brief to Hyperframes, which builds, times, and renders the video. The developer's role is to run the command and optionally steer the tone with a flag. ## How /brag works: the division between the skill and Hyperframes The /brag skill and the Hyperframes service handle different parts of the pipeline. The skill is responsible for analyzing the project, determining the narrative angle, writing a composition brief, and producing share copy. Hyperframes takes that brief, builds the timed sequence of frames, handles motion effects, and renders the mp4 file. This means /brag has two dependencies beyond the agent itself: Hyperframes CLI (npx hyperframes) and FFmpeg on PATH. The README specifies that narration is off by default and uses Kokoro through Hyperframes when enabled with the --voice flag. The skill offers tone control through the --tone flag, for example: ```text /brag --tone "fake Series A launch from 2016" ``` Voiceover can be added explicitly: ```text /brag --voice ``` These flags are passed directly to the skill as text prompts. The underlying brief to Hyperframes changes based on the tone. The /brag-slim variant removes the Hyperframes dependency entirely and runs on Opus 5.5 directly. It is a single-file skill that produces a launch video without bundled assets or Hyperframes. On Opus 5.5, the skill automatically routes to /brag-slim; running /brag --full forces the classic Hyperframes workflow. ## Installing /brag on Claude Code and other agents On Claude Code, the plugin marketplace install is: ```text /plugin marketplace add latent-spaces/brag /plugin install brag@brag ``` For other agents (Cursor, Codex CLI, opencode, Gemini CLI, and similar tools that support agent skills), the npx skills CLI works: ```bash npx skills add https://github.com/latent-spaces/brag --skill brag ``` Add `-g` to the npx command to install globally across all projects; without it, the skill installs into the current project only. The README notes that the repository also exposes the skill at each agent's standard discovery path through symlinks, so no extra configuration is needed after install. To install only /brag-slim (the lean version for Opus 5.5): ```bash npx skills add https://github.com/latent-spaces/brag --skill brag-slim ``` For agents without an installer, the README provides a manual copy option using rsync: ```bash rsync -a --exclude '.DS_Store' skills/brag/ ~/.claude/skills/brag/ ``` Restart Claude Code after the manual copy. The skill version that includes /brag-slim starts at version 0.4.0; run `claude plugin update brag` if the installed version is earlier. ## Multi-agent discovery and the symlink structure The repository is structured so that each supported agent platform finds the skill through its own expected directory path. According to the README, Claude Code reads .claude/skills/brag/, Codex CLI reads .agents/skills/brag/ walking up to the repository root, opencode reads .opencode/skills/brag/, and Google's Antigravity framework auto-detects from .agents/skills/brag/ at the project root or ~/.gemini/config/skills/brag/ globally. All of these paths resolve to the same underlying skill directory through symlinks. The README notes a Windows caveat: Git requires core.symlinks = true or a Developer Mode or Administrator privilege level for symlinks to work. Windows users who cannot create symlinks can copy the skills/brag/ directory manually to their agent's skill location instead. The skills.sh platform lists the skill at latent-spaces/brag/brag for agents that use that discovery mechanism. Custom agent configurations can also point directly at skills/brag/SKILL.md. ## What /brag cannot do: limitations and prerequisites The /brag workflow requires four things outside the skill itself: an agent that supports skills (Claude Code, opencode, Codex CLI, or a custom agent with instructions), Node.js 22 or higher, FFmpeg available on PATH, and access to the Hyperframes CLI via npx. If any of these are absent, the video rendering step will fail. The README provides a diagnostic command: npx hyperframes doctor. The skill is not a screen recorder and does not capture live application sessions. It analyzes the project repository and produces a composed video brief, not a direct recording of the application running. A developer who wants to show specific UI interactions must use a screen recording tool separately. The skill is also not a general-purpose video editor. It produces one format: a short launch video. It cannot generate tutorial videos, walkthroughs, or long-form demos. The tone flag provides some control over the narrative angle, but the creative decisions about framing are made by the skill itself. The output quality depends on what the skill can infer about the project. A repository with a clear README, a PRODUCT.md, and example output gives the skill more material to work with. A nearly-empty repository will produce a less specific brief. ## Repository contents and the example benchmark suite The repository layout is described in the README: skills/brag/ holds the skill itself with bundled music and sound effects, skills/brag-slim/ holds the single-file Opus 5.5 variant, examples/ contains fake product sites used as a benchmark suite, docs/ holds the launch site for GitHub Pages, and .claude-plugin/ contains the plugin manifest. The examples directory includes five fake product directories: bicycles-for-snakes, fish-flight-school, horse-tinder, psychologists-for-chatbots, and taxi-for-taxis. These are intentionally absurd product concepts used to test whether the skill produces coherent launch videos from thin premises, which serves as a form of quality benchmark for the skill's narrative judgment. The music credits in the README attribute the bundled tracks to ende.app under the 'Happy Beats / Business Moves' category, sound effects to Kenney, and video generation to Hyperframes. The license for the repository itself is MIT. The project has no GitHub releases tagged, which means there is no formal version history to review for breaking changes. The README notes that /brag-slim is included from version 0.4.0 and that existing users should run `claude plugin update brag` to get it. ## Maintenance and the /brag-slim direction The last push to the repository was on 2026-09-24. The repository is not archived and has no formal release tags. The /brag-slim variant represents the project's stated direction for the Opus 5.5 agent. The README describes it as 'the same /brag, rebuilt lean for Opus 5.5', without Hyperframes and without bundled assets. For new users on Opus 5.5, /brag-slim is the default path; the Hyperframes workflow remains available with the --full flag. The MIT license permits commercial and private use, modification, and distribution without restriction. The music bundled in skills/brag/ has its own attribution: the README credits ende.app and Kenney, and those credits should be preserved when the bundled assets are redistributed. ## Conclusion The /brag skill is for developers who want to produce a launch video immediately after building something without spending time on video editing. It is not a general-purpose screen recorder or a presentation tool. The output depends on Hyperframes, which means a Hyperframes API account and CLI access are required for the full workflow; /brag-slim removes that dependency for Opus 5.5. Confirm FFmpeg is on PATH and Node.js 22+ is installed before running the first /brag. Projects on Claude Code can install with the marketplace command; projects on other agents use the npx skills CLI. ## FAQ ### What does the /brag skill do in Claude Code? The /brag skill analyzes the current project and generates a short, shareable launch video with music, motion effects, and share copy. It produces a brag-output/ folder containing a plan, a composition brief, and a rendered brag.mp4 file. ### What are the system requirements for running /brag? The README lists Node.js 22 or higher, FFmpeg available on PATH, and the Hyperframes CLI (npx hyperframes) as requirements, plus an agent that supports agent skills such as Claude Code, opencode, or Codex CLI. The /brag-slim variant removes the Hyperframes dependency. ### Does /brag work with coding agents other than Claude Code? Yes. The repository exposes the skill at the standard discovery path for Claude Code, Codex CLI, opencode, and Google Antigravity through symlinks, and any agent with custom instruction support can point at skills/brag/SKILL.md directly. The npx skills CLI installs it for Cursor, Codex, Copilot, Gemini CLI, and opencode. ## Sources - [Issues](https://github.com/latent-spaces/brag/issues) - [latent-spaces/brag on GitHub](https://github.com/latent-spaces/brag) - [License: MIT](https://github.com/latent-spaces/brag/blob/main/LICENSE) - [README](https://github.com/latent-spaces/brag/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/latent-spaces-brag