Ugc

UGC

Use this skill to plan UGC-style creator ads, talking-head scripts, social proof concepts, direct-response hooks, objection handling, and creator-read copy while keeping claims honest and provider-neutral.

Language Policy

Public instructions and installation guidance stay in English. After verified installation, resolve the working language from an explicit user preference, then the user's own conversation, then a reliably exposed host locale, otherwise English. Copied English setup prompts and source files are not language preferences; do not infer hidden account settings. Keep explicit deliverable-language requests and exact supplied artwork copy separate from conversation language. Do not translate or rewrite public source files to localize a session.

When To Use

Use this skill when:

• The user asks for creator-style ads, social proof, talking-head scripts, hooks, or short-form direct response.
• A product, offer, or ecommerce workflow needs human-feeling script structure.
• Claims, proof, objection handling, and CTA need to be kept within evidence boundaries.

Do not use this skill to fake testimonials, identities, personal experience, or results.

Inputs

Required:

• brief_contract: objective, audience, deliverable, and constraints.
• offer_or_product_facts: verified features, benefits, proof points, and limits.
• platform_context: channel, duration, format, and creator style.

Optional:

• voice_notes: desired creator tone or brand voice.
• objections: known hesitations or buying barriers.
• copy_locks: required CTA, legal copy, or banned phrasing.

Outputs

Produce a UGC Script Pack with:

• hook options
• creator angle and setup
• proof point framing
• objection handling
• CTA variants
• platform fit notes
• claim boundaries

Process

1. Identify the audience problem and credible angle.
2. Build hooks that do not rely on fake experience.
3. Use only verified proof points or clearly labeled assumptions.
4. Keep script variants distinct by angle, not just wording.
5. Route final polish through humanizer when the script should sound more natural.
6. Before delivering a ready-to-use creator script, use copy-voice to record author context, claim and copy locks, and the bounded Copy Delivery Loop.

Decision Rules

• If proof is missing, write softer framing instead of inventing authority.
• Use first-person only when the user authorizes that voice and facts support it.
• Keep short-form scripts tight and concrete.
• If visual production is needed, hand off to direction or storyboard roles.

Guardrails

• Do not fabricate testimonials, reviews, identities, outcomes, or before-after claims.
• Do not create deceptive social proof.
• Do not execute video generation or choose external providers.
• Do not change legal copy or required disclaimers.
• Do not write a first-person experience, result, or recommendation unless the user supplied the speaker and supporting facts for this task.

Handoff

Review gate: copy_fit.

Hand off to copy-voice, motion-direction, storyboard-architect, or video-prompting with:

• ugc_script_pack
• claim_boundaries
• creator_angle
• copy_locks
• platform_notes

QA Checklist

• Claims are supported or softened.
• Hooks are distinct and plausible.
• CTA matches the brief.
• No fake testimonial or identity is implied.
• Script can be read naturally by a creator.
• A ready-to-use script does not add a hook, CTA, fake informality, or controlled imperfection unless the brief and channel support it.