BB viral-reels-creator
Full-featured viral Reels creator and editor powered by ffmpeg. Use this skill whenever the user wants to create, edit, find, or produce viral Instagram Reels, TikTok videos, YouTube Shorts, or any vertical short-form video content. Triggers include: "create a reel", "make a viral video", "make a short video", "Instagram reel", "TikTok video", "YouTube Shorts", "vertical video", "reels editor", "video editor", "add subtitles to video", "auto captions", "merge clips", "slideshow video", "add music to video", "beat sync video", "sync cuts to music", "video transitions", "caption video", "color grade video", "slow motion", "speed ramp", "text animation on video", "video effects", "video overlay", "ken burns effect", "video filter", "find best moments in video", "find highlights", "scene detection", "export for TikTok", "export for multiple platforms", "batch export video", "viral hook", "viral opening", "make my video go viral", or any request involving ffmpeg-based video editing for social media. Also trigger when the user uploads video/image/audio files and asks to combine, trim, stylize, color grade, beat-sync, or export them as a reel. Supports all formats: mp4, mov, avi, mkv, webm, jpg, png, gif, mp3, wav, aac, and more.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1243 chars, limit 1024
Process rating: all ten parameters 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 25 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3296 tokens
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1242: 120–800 characters recommended
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 35 example trigger phrases
- +4Structure: 21 headings
- +3Step-by-step instructions: 25 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.