# Aigc Leadgen Video > Create end-to-end AIGC marketing videos designed to attract leads for B2B or B2C offers. Use when the user wants a lead-generation video, scenario ad, product story, UGC-style ad, AI-generated short video, storyboard, keyframes, post-production package, cover, or publish copy. Supports full-auto, assisted, and planning-only execution across capable agent environments; do not use for ordinary personal talking-head scripts or non-video content. - Skill: `keyzii2024-sys/aigc-leadgen-video` (Agent Skill, multi-file: 9 files) - Install (CLI): `npx skillmds@latest add keyzii2024-sys/aigc-leadgen-video` - Raw SKILL.md: https://api.skillmd.com/api/skills/keyzii2024-sys/aigc-leadgen-video/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Marketing & Growth - Author: keyzii2024-sys (https://skillmd.com/u/keyzii2024-sys) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/keyzii2024-sys/aigc-leadgen-video --- # AIGC Lead-Generation Video Turn one audience problem and one offer into a publishable AIGC video package: strategy, script, storyboard, visual assets, generated clips, post-production, cover, publish copy, and a measurable call to action. ## Start Here 1. Detect the current host and available capabilities before promising execution. 2. Read the matching file under `references/platforms/`. 3. Choose the highest safe execution level: - **Full-auto:** can read/write files, run scripts, control a browser, and access the selected media provider. - **Assisted:** can create plans/assets or run scripts, but the user must perform login, upload, generation, or download steps. - **Planning-only:** can produce the complete production package, prompts, and handoff checklist but cannot operate media tools. 4. State the execution level and any user handoffs in one short sentence. Never imply that an unavailable capability is automated. 5. Read `references/kickoff.md`, ask only the unanswered high-impact questions, and confirm the brief before incurring cost or generating media. If a brand kit is supplied, treat it as the source of truth. If none exists, offer `assets/example-brand-kit/` as a temporary demo only; never invent real claims, customer results, logos, or endorsements. ## Core Decisions Before writing the script, lock these variables: - one audience segment and one buying situation; - one painful or desirable outcome; - one offer and one next action; - one creative format; - one visual style; - one target platform and duration; - one evidence plan for product screens, claims, and proof. Read `references/audience-and-offer.md` for B2B/B2C routing and `references/creative-formats.md` to select among scenario drama, product demonstration, case/result story, and UGC-style content. ## Production Workflow ### 0. Brief and feasibility - Complete the compact kickoff gate in `references/kickoff.md`. - Verify the selected media provider, account access, credits, output limits, and user authorization. - Identify which steps require user login or confirmation. Do not store passwords, cookies, verification codes, or private tokens. ### 1. Strategy and script - Write a one-sentence audience insight, offer promise, and conversion action. - Build a hook that makes the target viewer recognize a relevant problem, desire, or result within the first two seconds. - Use one dominant narrative. Remove details that do not increase attention, belief, or action. - Produce a timed storyboard with shot purpose, visual action, dialogue/voiceover, evidence, audio, and transition notes. - Obtain user confirmation before generating paid media. ### 2. Visual system - Read `references/visual-system.md`. - Reuse confirmed character, product, environment, logo, color, and typography assets. - For recurring characters, build an appropriate reference sheet before multi-shot generation. Do not require a nine-view sheet when a simpler reference is sufficient. - Keep dense text and exact UI out of generative imagery. Use real screenshots or deterministic post-production for information that must be correct. ### 3. Prompts and media generation - Read `references/prompt-patterns.md` and the selected provider adapter under `references/providers/`. - Generate the cheapest useful test first when the provider supports it. - Ask immediately before paid generation if price, retry count, or authorization is not already confirmed. - Save task IDs, prompts, source assets, and output locations for reproducibility. ### 4. Quality gate - Read `references/quality-gates.md`. - Reject factual errors, misleading claims, broken anatomy, unintended character changes, unreadable required text, unusable audio, and mismatched calls to action. - Use the scorecard to guide inspection, not to fabricate confidence. A self-assigned score never overrides an observable defect. - After two similar failures, change the shot, reference, provider setting, or production method instead of repeating the same prompt. ### 5. Post-production - Read `references/postproduction.md` only when local editing is available. - Use scripts under `scripts/` for deterministic composition, overlays, covers, audio mixing, or upscaling. - Preserve source audio when lip sync depends on it. Verify the final file with media inspection tools and visual review. ### 6. Publish package - Read `references/publishing.md`. - Deliver the final video, cover, three title options, platform-specific caption, tags, pinned-comment suggestion, AI-content disclosure note, and the exact CTA. - Keep the CTA consistent with the offer. Do not use fake scarcity, fake customer proof, guaranteed results, or unsupported superlatives. ### 7. Measurement and iteration - Record platform, creative format, audience, hook, CTA, spend, 3-second retention, completion rate, profile visits, inquiries, leads, and qualified conversions when available. - Separate evidence from interpretation. A download or comment proves interest, not successful use or purchase intent. - Add a narrow correction to `references/field-notes.md` only after a repeatable failure or verified improvement. Do not turn one incident into a universal rule. ## Non-Negotiable Rules - One video targets one primary audience and one conversion action. - Show a real buying situation, user problem, product result, or proof; do not lead with unexplained jargon. - Treat business claims, prices, rankings, medical/financial statements, and customer results as facts requiring verification. - Use fictional or authorized identities. Blur or replace personal data, private dashboards, messages, and customer names. - Keep brand assets and account details outside the public skill. Use paths or configuration, never embedded secrets. - The selected platform or provider may change. Preserve the creative intent and quality criteria instead of copying brittle UI steps across environments. ## Reference Routing - Kickoff and inputs: `references/kickoff.md` - B2B/B2C audience and offer logic: `references/audience-and-offer.md` - Creative formats and story structures: `references/creative-formats.md` - Character, product, UI, and visual consistency: `references/visual-system.md` - Prompt patterns: `references/prompt-patterns.md` - Quality gates: `references/quality-gates.md` - Local editing: `references/postproduction.md` - Titles, captions, CTA, and measurement: `references/publishing.md` - Current verified pitfalls: `references/field-notes.md` - Host behavior: `references/platforms/` - Media-provider operation: `references/providers/` Load only the references needed for the chosen execution path.