MusicCAUTION
You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Bundled tracks:
happy-beats-business-moves-vol-1-by-ende-dot-app.mp3(2:44)happy-beats-business-moves-vol-9-by-ende-dot-app.mp3(1:54)happy-beats-business-moves-vol-10-by-ende-dot-app.mp3(1:00)happy-beats-business-moves-vol-11-by-ende-dot-app.mp3(1:28)happy-beats-business-moves-vol-12-by-ende-dot-app.mp3(1:58)
Source: ende.app "Happy Beats / Business Moves" series.
Cue presets live in cues/:
.music-cues.jsoncontains full-track beat and strong-cue metadata..music-cues.mdcontains compact planning guidance for the first 20-25 seconds.
These files are generated by skills/brag/scripts/analyze_music_cues.py and are intended for /brag planning. Normal skill runs should read the presets when present and continue without beat/cue sync when they are missing.
Before publishing or redistributing the skill, verify and document the exact music license terms alongside these files.
d75764317327OBSERVED · 2026-10-20Install
Commands as the repository documents them. They are shown, not run.
uv run --project <skill-dir>/scripts \
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| cursor | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: brag description: Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed. --- # /brag You built it. Now let's brag about it. ## Invocation dispatch (must happen first) **Model check.** If you are Claude Opus 5.5 and the invocation doesn't ask for the full workflow (`--full`, "use the full brag") or for voiceover (`--voice`, which brag-slim doesn't do), switch to brag-slim: read `<skill-dir>/slim.md` (the /brag-slim skill, bundled here) and follow it for the rest of this run instead of this file. Pass along the user's input, and pass any other options (`--no-music`, `--title`, ...) as plain-language direction. Tell the user in one line first, e.g. "You're on Opus 5.5, so I'm using /brag-slim: I build the whole video myself. Say 'use the full brag' to switch back." If you are any other model, or can't tell which model you are, skip this check. Before inspecting the project, parse the complete `/brag` invocation. If the invocation contains `--voice`, set `voice.enabled = true`. Enable narration only for that run. Do not enable narration automatically and do not fall back to the normal no-voice workflow. `/brag` turns the current project website or app into a short, polished, shareable launch video using Hyperframes. It is narrow, opinionated, and fun. ## What this skill does 1. Reads the current project code to understand the app. 2. Plans a short brag concept specific to this project. 3. Scripts and storyboards the video. 4. Hands a focused composition brief to Hyperframes. 5. Validates, renders, and writes share copy. ## Parsing the invocation The user may invoke with natural language or flags: ``` /brag /brag --tone chaotic /brag --tone polished --format vertical /brag this. Make it feel like a ridiculous startup launch. ``` Parse these options: | 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 | | `--voice` | flag | narration off | Voice is opt-in. If `--voice` is present, use Kokoro via Hyperframes and do not add any provider-selection logic. The voice workflow is intentionally single-provider. 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", "museum exhibit", or "overproduced mobile game ad". When the user gives freeform tone direction, map it to the nearest preset for pacing and structure, but preserve the user's direction in the plan and composition brief. ## Narration guidance When `--voice` is enabled, write narration that complements the visuals, does not simply read visible text, matches scene pacing, sounds natural and conversational, and moves smoothly between scenes. Keep the script concise and specific to the product so the voice feels like part of the edit rather than a separate narration track. --- ## Output directory By default, output goes to `brag-output/`. To avoid overwriting previous runs, use a timestamped directory: ``` brag-output-2026-05-04-143022/ ``` Use a timestamp when: - The user explicitly asks for a new run without overriding previous results - A `brag-output/` directory already exists in the project Generate the timestamp at the start of the run (`YYYY-MM-DD-HHmmss`) and use it consistently for all output paths in that run: plan, brief, composition, render, and share copy. ## Skill directory `<skill-dir>` is the directory containing this `SKILL.md`. Claude Code prints it as "Base directory for this skill" when the skill loads; for other agents it's wherever the skill was installed. Bundled assets are under `<skill-dir>/assets/` and scripts under `<skill-dir>/scripts/`. Don't guess an install path: a plugin install, a `~/.claude/skills/` copy, and this repo all put it somewhere different. --- ## Step 1: Inspect the project **Read:** [references/step-1-inspect.md](references/step-1-inspect.md) Scan the project directory and extract the information needed to plan the brag video. **Gate:** You can answer all 9 questions in the brag planning rubric. --- ## Step 2: Plan and storyboard **Read:** [references/step-2-plan.md](references/step-2-plan.md) Write `<output-dir>/brag-plan.md` (where `<output-dir>` is `brag-output/` or the timestamped variant chosen above). Answer the planning rubric. Commit to a creative angle. Write the beat-by-beat storyboard including scenes, text, timing, transitions, and SFX cues. When music is selected, include a compact `Music cue guidance` section: read the bundled track's cue preset from `<skill-dir>/assets/music/cues/` if present, otherwise note cues will be detected at composition time (any track now supports beat sync — see `references/audio.md`). Cue metadata is optional timing guidance only: story, readability, pacing, and product clarity stay primary. **Gate:** `<output-dir>/brag-plan.md` exists with a full storyboard. Scene durations sum to 15–25 seconds. --- ## Step 3: Hand off to Hyperframes **Read:** The Hyperframes domain skills — `hyperframes-core`, `hyperframes-animation`, `hyperframes-creative`, `hyperframes-keyframes`, `hyperframes-cli`. /brag is its own workflow: do not enter the `hyperframes` entry-point intent interview or route into its generic promo / launch-video workflow. **Read:** [references/step-3-compose.md](references/step-3-compose.md) **Read:** [references/audio.md](references/audio.md) Write the composition brief and use Hyperframes to create the video implementation in `<output-dir>/composition/`. `/brag` owns the p
Trust audit
CAUTIONgrade B · trust 85/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (15)
card-fan-1.ogg
card-fan-2.ogg
card-place-1.ogg
card-place-2.ogg
card-place-3.ogg
.agents/skills/brag
.agents/skills/brag-slim
.claude/skills/brag
.claude/skills/brag-slim
.opencode/skills/brag
assets/music/happy-beats-business-moves-vol-1-by-ende-dot-app.mp3
assets/music/happy-beats-business-moves-vol-10-by-ende-dot-app.mp3
assets/music/happy-beats-business-moves-vol-11-by-ende-dot-app.mp3
assets/music/happy-beats-business-moves-vol-12-by-ende-dot-app.mp3
assets/music/happy-beats-business-moves-vol-9-by-ende-dot-app.mp3
Gates applied: no_behavioural_pass.
d75764317327full audit observations/trust-audit/skill/latent-spaces__brag.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-20 | d75764317327 | CAUTION | B | 85 | first audit |
Questions
What does the brag — latent-spaces/brag skill do?
You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command.
Is brag — latent-spaces/brag safe to install?
With care. The audit graded it B (85/100) and found 15 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can brag — latent-spaces/brag access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does brag — latent-spaces/brag work with?
Its documentation mentions claude-code and cursor. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (d75764317327), read on 2026-10-20. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/latent-spaces/brag/)
Not your listing, or something out of date? Claim or update your listing.