AB digital-human
Create script- or audio-driven talking-head videos with a user's saved character, portrait, or a representative still from video. Use for 数字人、角色口播、数字分身、 照片开口说话、人像口播, AI avatar, talking photo, AI presenter, or digital twin. Choose between direct-to-camera speech and short character performances by the requested shot. Do not use for static avatars, game or 3D characters, video translation, existing talking-head editing, lip-sync dubbing alone, or TTS alone.
Create script- or audio-driven talking-head videos with a user's saved character, portrait, or a representative still from video.
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, running it twice
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 17 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4048 tokens
- 85Steps. 16 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 459: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.