BB chat-motion-overlay
Generate configurable chat motion overlays from a transcript or screenshot, including plain bubble scenes, app-style chat containers, optional device frames, preset or uploaded avatars, nickname display rules, and transparent-video-ready Remotion bundles. Use when Codex needs to create reusable short-form chat clips for Douyin, demo videos, story reenactments, social-message proof scenes, or embeddable alpha overlays for Hyperframe and Remotion workflows.
Generate configurable chat motion overlays from a transcript or screenshot, including plain bubble scenes, app-style chat containers, optional device frames…
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
How to improve
- 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: 24. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "od"
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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Steps. 48 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 938 tokens
- 100Running it twice. No mutating operations
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)
- +4No input/output examples
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 459: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 48 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (4 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.
In the sandbox The scripts kept to themselves
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Запущено 7 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
Из них 3 не дошли до работы, и об их поведении мы ничего не узнали.
scripts/build_chat_overlay_spec.py | не запустился: build_chat_overlay_spec.py: error: the following arguments are required: --input |
scripts/prepare_chat_overlay_bundle.py | не запустился: prepare_chat_overlay_bundle.py: error: the following arguments are required: --transcript, --output-dir |
scripts/run_test_matrix.py | не запустился: run_test_matrix.py: error: the following arguments are required: --skill-root, --work-dir, --node-modules |
assets/remotion-template/remotion.config.ts | ничего за пределами своей папки |
assets/remotion-template/src/chatSpec.ts | ничего за пределами своей папки |
assets/remotion-template/src/index.ts | ничего за пределами своей папки |
assets/remotion-template/src/components/types.ts | ничего за пределами своей папки |
15 Oct 2026