---
name: avatar-video-production
description: "Prepare and verify avatar videos using approved likenesses, scripts and provider access. Use when the user requests avatar video production. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Avatar Video Production

Prepare and verify avatar videos using approved likenesses, scripts and provider access.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Authorized avatar and voice
- Exact script
- Aspect ratio and language
- Approved video provider

## Methods

### Confirm likeness and voice rights

Confirm the right to use the supplied likeness and voice. Preserve exact required copy and do not imply the speaker recorded words they did not authorize.

### Plan script delivery

Map script sections to pacing, pronunciation and on-screen material. Use a short pronunciation test when names or specialist terms are uncertain.

### Track generation to completion

Submit through the approved provider route, track the returned job identity and inspect terminal state. Never count a queued generation as a delivered video.

### Inspect the final video

Check lip sync, pronunciation, captions, brand identity and exports. Disclose synthetic presentation where required and never use generated footage as proof of a real product action.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.