CF game-trailer
Make a trailer, promo, teaser, sizzle reel, launch or gameplay video for one of our browser games (Road to AEW / ROAD TO THE BIG TIME, 5 Star Booker, or any game built the same way) from the real game: frame-exact 4K capture under a virtual clock, a beat-mapped edit with poster overlays printed in the game's own CSS, a score written in code, the game's own sounds and its crowd engine. Use it whenever someone asks for a trailer, a promo or social video of a game, a YouTube or X cut, a re-cut or recapture of an existing trailer, or just 'make a video that shows the game off'. Carries the pace rules the owner settled on and the capture, edit and audio traps that cost time.
Make a trailer, promo, teaser, sizzle reel, launch or gameplay video for one of our browser games (Road to AEW / ROAD TO THE BIG TIME, 5 Star Booker, or any…
As a process F 26/100 · No process to follow — References files that are not bundled: scripts/promo/, scripts/audio/dsp.py
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash Grep Glob Task Skill
-
low Dangerous commands
cmd-background-processreferences/lessons.md:24Starts a background / autostarted process (documentation table row)| The dev server is gone after a container restart | It ran in the shell that died | `setsid nohup npm run dev -- --port 3000 --strictPort &` |
table -
low Dangerous commands
cmd-background-processreferences/pipeline.md:112Starts a background / autostarted process (documentation table row)| Game dev server | `setsid nohup npm run dev -- --port 3000 --strictPort > tmp/promo/logs/dev.log 2>&1 &`; `PROMO_GAME_URL` overrides the default `http://loca…000/static/game/` |
table
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/promo/ - warning
missing-refreference to a missing file: scripts/audio/dsp.py - note
frontmatter-keyunknown frontmatter key "routing"
Process rating: all ten parameters 26/100
- 0Tools and files. 2 referenced file(s) missing: scripts/promo/, scripts/audio/dsp.py
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 7 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2899 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 678: enough signal without eating the budget
- +4Structure: 16 headings
- +4Has examples (1 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: 78.