BC ai-avatar-video-runcomfy
AI avatar video on RunComfy. This RunComfy avatar video skill creates talking-head and lip-sync videos via the `runcomfy` CLI. Routes across ByteDance OmniHuman (RunComfy's lip-sync feature pick — audio-driven full-body avatar from one portrait + audio file), Wan-AI Wan 2-7 (open-weights audio-driven lip-sync via `audio_url` on a portrait), HappyHorse 1.0 (Arena #1 t2v / i2v with in-pass audio from prompt — no audio file needed), Seedance v2 Pro (multi-modal cinematic with reference audio + reference subject), and community Wan 2-2 Animate (stylized character animation). The RunComfy avatar video skill picks the right model for intent — UGC voiceover, virtual presenter, dubbed product demo, lip-synced character, dialog scene — and ships each model's documented prompting patterns plus the minimal `runcomfy run` invoke. Triggers on "talking head", "lip sync", "avatar video", "make X speak", "audio to video", "audio driven avatar", "virtual presenter", "AI spokesperson", "dubbed video", "UGC avatar", "HeyGen alternative", "Synthesia alternative", "digital human", "make this portrait talk", "video from voiceover", or any explicit ask to put words in a face with RunComfy.
AI avatar video on RunComfy.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1186 chars, limit 1024 - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "clawdis"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3810 tokens
- 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
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 1185: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 15 example trigger phrases
- +4Structure: 29 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.