AC ai-video-restyler
Restyle one short video into a new visual treatment while carrying forward the source subject, action, composition, and camera intent. This AI video restyler and video style transfer workflow turns live action into anime, illustration, Chinese comic, ink, clay, paper-cut, or cyberpunk looks from one source clip and a chosen art direction, and reviews style match, subject identity, motion continuity, and source-audio result. Use it for live action to anime, brand visual refresh, Chinese-comic looks, fashion films, music visuals, and creator experiments, with one dominant visual change per run and honest post-result review.
Restyle one short video into a new visual treatment while carrying forward the source subject, action, composition, and camera intent.
As a process C 60/100 · Has gaps — weak spots: result and completion, running it twice, 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: 14. 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 60/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2312 tokens
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 629: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.