CC embedded-captions
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
Add captions or subtitles to an existing single-subject talking-head video without editing the footage.
As a process C 57/100 · Has gaps — References files that are not bundled: ../hyperframes/references/plugin-installation.md, themes/README.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 0
✓ No critical or high findings
Files scanned: 79. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8404 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../hyperframes/references/plugin-installation.md - warning
missing-refreference to a missing file: themes/README.md - note
edit-residuethe text marks something as outdated (lines 28, 192): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 57/100
- 0Tools and files. 2 referenced file(s) missing: ../hyperframes/references/plugin-installation.md, themes/README.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 8404 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 57 steps, 2 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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)
- +3Output format is not stated: the model decides each time
- -35 of 9 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 557: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (13 of 14)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.