/gloat — by Qbyx

You built it. Don't just brag. Gloat.

▶ Watch the full launch video (with sound) — it was made by /gloat itself, from this repo, in one command: brand DNA from the Qbyx site, a hardstyle drop beat-locked to the wordmark, and an impact ending. What you see is literally the product.

/gloat is a Claude/ChatGPT skill that turns the project you're sitting in into a short, brand-faithful, hard-hitting promo or announcement video — music, motion, share copy, and a music-candidates listening kit included. One command, rendered by HyperFrames.

It is the battle-hardened successor to /brag: same great skeleton, plus everything a real multi-round production cycle taught us about what actually gets a video approved — not just generated.

Why gloat, when brag exists?

/brag makes a good first draft. /gloat encodes the revision meeting.

	/brag	/gloat
Reads your product	✅	✅
Reads your brand system first (theme, grids/washes, fonts, mascots, logo variants)	—	✅ Step 0, gated
Music	bundled corporate loops	audio engine: genre-mapped sourcing, loudness profiling, drop-aligned trimming, beat-locking, final-render audio verification
Music taste iterations	re-render and hope	candidates kit — aligned preview cuts the user auditions by ear ("use candidate 2")
Announcement videos (launches, partnerships, milestones)	—	✅ --announce mode with claim-truth tables (no "live now" until it's live)
Partner logos	—	recolor-don't-container rules, alpha-bbox cropping, balanced lockups
Endings	fade out	impact outro: anticipation dip → flash → punch-scale → shockwave → shake → smash cut, beat-locked, music still playing
Producer craft	—	craft.md: continuous micro-motion & parallax, match cuts, kinetic type, accelerating cut rhythm, grain/vignette/light-sweep, layered sound, loop & vertical recomposition — pick 2-3 per video, never all
Hero frame / thumbnail	—	one poster-worthy frame designed in the plan and exported as hero-frame.png with every render
Render QA	validates the composition	also verifies the MP4: per-2s audio sweep, frame extraction, stream checks
Edge cases	—	pitfalls.md: 20+ real production bugs with fixes

Every rule in gloat traces to a real failure: the plain-white "boring" background, the music that silently died at 0:14, the partner logo in an "ugly container", the four rejected soundtracks, the mascot that never appeared. Gloat is the skill that ships the video those revisions were asking for — on the first pass.

Install

/plugin marketplace add QbyxStudio/gloat
/plugin install gloat@gloat

No plugin system? Install the skill directly.

macOS / Linux:

rsync -a skills/gloat/ ~/.claude/skills/gloat/

Windows (PowerShell):

Copy-Item -Recurse -Force skills\gloat "$env:USERPROFILE\.claude\skills\gloat"

Restart Claude Code after copying.

Use it

From any project directory:

/gloat

Steer it:

/gloat --announce "v2.0 launches today" --music "hype aggressive powerful"
/gloat --tone drop --format vertical
/gloat this, but make it feel like a stadium reveal

You get a gloat-output/ folder:

gloat.mp4              ← the video
hero-frame.png         ← the poster frame / social thumbnail
brand-dna.md           ← your project's extracted visual identity
gloat-plan.md          ← concept, storyboard, craft picks, taste changelog
share-copy.txt         ← postable caption
music-candidates/      ← aligned alternate soundtracks + README
composition/           ← the HyperFrames project (fully editable)

How it works

Step 0  Brand DNA     — theme polarity, tokens, background recipes, verified
                        fonts, logo variants, mascots. Gated: no brand, no video.
Step 1  Inspect       — the product (9 questions) or the announcement (6 + claim
                        truth table).
Step 2  Plan          — storyboard with reading-time floors, brand & copy
                        compliance per scene, the drop moment, the bang moment,
                        2-3 producer-craft picks + the hero-frame timestamp.
Step 3  Audio engine  — energy words → genre → real tracks → loudness profiling →
                        trim so the drop detonates on your reveal → beat-lock →
                        cut the candidates kit.
Step 4  Compose       — HyperFrames build with seek-safe motion, partner-logo
                        rules, layout-audit markers, the impact ending.
Step 5  Verify & ship — validate the composition AND the rendered MP4; deliver
                        with revision protocol armed.

Gloat owns the story, brand, copy, and audio direction; HyperFrames owns the implementation and rendering — the same clean boundary /brag pioneered.

The three laws

1. The brand ships the video. A plain background never ships. A dark "generic trailer" on a light-branded product never ships.
2. The music is a deliverable. Profiled, aligned, verified in the final render — with alternates the user can audition instead of re-rolling blind.
3. Claims must be exactly true. "Soon" stays "soon". No invented dates. No invented numbers or implied results.

Requirements

• Claude Code (with skill/plugin support)
• Node.js 22+
• FFmpeg on PATH
• HyperFrames CLI — npx hyperframes (check with npx hyperframes doctor)
• SFX: reuses /brag's bundled Kenney library if installed; any CC0 UI/impact set works

What's in this repo

• skills/gloat/ — the skill: SKILL.md + 9 reference docs
• docs/ — README assets
• evals/ — test prompts for iterating on the skill itself
• .claude-plugin/ — plugin manifest + marketplace catalog

Credits

• Built on /brag by latent-spaces — the step structure, tone system, and reading-time discipline originate there. Thank you. 🙏
• Video generation — HyperFrames
• Music sourcing — Pixabay (Content License)
• Sound effects — Kenney (CC0, via brag)

License

MIT © Qbyx

Contributions, war stories, and new pitfalls welcome — open an issue or a PR.