A screenshot can show what you built. A screen recording can show how it works. But making a short, polished launch video usually means opening another set of tools—and spending time editing instead of sharing.

/brag is an open-source agent skill designed to help with that last step. Point an agent at a project, and it can inspect the code, plan a short video, and prepare the output for sharing.

Watch the examples and see the project

What is /brag?

/brag reads a project’s source code to understand what the product does, what it looks like, and which details are worth showing. It then creates a video plan and hands a focused composition brief to Hyperframes, which handles the composition and rendering workflow.

The output includes the rendered video, a poster image, and a share caption—along with the plan and composition files.

From project code to video

The classic /brag workflow has four steps:

  1. Inspect the project. Read relevant files to identify the product, audience, visual identity, and user flow.
  2. Plan the story. Choose a creative angle, write a hook, and lay out the video scene by scene.
  3. Build the composition. Give Hyperframes the brief, including the visual direction and storyboard.
  4. Validate and deliver. Check the composition, render the video, select a poster frame, and write share copy.

The story usually follows a simple shape:

Hook → product reveal → highlights → close

That shape is a guide, not a rigid template. The video is meant to show the actual product—not just string together generic marketing claims.

A typical output folder looks like this:

brag-output/ brag-plan.md composition-brief.md brag.mp4 brag.jpg share-copy.txt composition/

The plan and brief document the creative direction, while the video, poster, and caption are the pieces ready to share.

What makes a good brag video?

The project’s instructions set a few useful creative constraints:

  • Keep it short: usually 15–25 seconds.
  • Make the hook count: the opening seconds should give people a reason to keep watching.
  • Show the product: include real UI, copy, or other recognizable project details.
  • Keep text readable: use motion and cuts to create pace, not text that disappears before it can be read.
  • Stay specific: avoid claims and phrases that could describe any product.
  • Make it shareable: choose a strong poster frame and write a caption that works outside the video.

The workflow also includes a validation step before rendering. In the classic path, Hyperframes’ check helps catch issues such as text overflow and contrast problems.

Two workflows: /brag and /brag-slim

The repository includes two approaches:

  • /brag uses Hyperframes to build and render the composition.
  • /brag-slim is a lean, single-file workflow. The agent builds the video with tools already available on the machine, without Hyperframes or bundled assets.

On Claude Opus 5.5, /brag switches to /brag-slim by default. Use /brag --full to request the classic Hyperframes workflow instead.

Try it

Install the skill with the skills CLI:

 bash npx skills add https://github.com/latent-spaces/brag --skill brag MASHRAF AIMAN CTO and Co-founder Ennovat Studio