← ClaudeAtlas

identity-and-likenesslisted

Use when a real or recurring person must appear in generated video - choosing between a consent-gated avatar, reference photos, reference-to-video, or a trained LoRA; writing prompts that preserve likeness instead of fighting it; and applying the consent and policy rules. Covers the zero-shot gate that tells you whether training is needed at all.
raphaelbgr/ai-video-prompting · ★ 0 · AI & Automation · score 70
Install: claude install-skill raphaelbgr/ai-video-prompting
# Identity, likeness and consent Getting a specific person on screen is the hardest part of AI video, and the part with real legal and ethical weight. This skill covers the four routes, the prompt rule that decides likeness quality, and the consent rules that are not optional. --- ## 1. Consent comes first - **Never** generate a real person's likeness without that person's explicit, informed permission. This is the platform policy on every major provider *and* the bar to hold yourself to regardless of platform. - **Never** depict real, named politicians or celebrities. Use fictional personas for political content. Beyond the ethics, prominent-figure filters will block you anyway. - **Never** train an identity model on someone who has not agreed to it, and gate publication on their approval, not just their approval to be photographed. - **Label output as AI-generated** wherever the platform requires it. Google's video models embed a **SynthID** watermark in every frame with no opt-out, and it survives cropping, filters, frame-rate changes and re-encoding — so it is detectable whether or not you label it. --- ## 2. Route picker | Situation | Route | |---|---| | Yourself on camera, need dialogue + audio, fast | **A — consent-gated avatar** (Google Flow `@me` + Omni Flash) | | Another consenting person, fast | **B — reference images / character upload**, or their own consented avatar | | Portable identity, offline, or a character you own | **C — trained LoR