Skill 详情
explainer-video-production
与供应商无关的解说视频制作,涵盖脚本撰写、分镜、声明审核、本地化和QA。
使用前先检查
自动化审核只检查相关性,不代表安全审查或推荐。使用前请阅读来源中的说明。
SKILL.md
这段内容是审核时保存的快照。外部来源才是完整且最新的版本。
--- name: explainer-video-production description: Provider-independent explainer video production for AI agents creating educational, product, concept, nonprofit/public-service, onboarding, training, animated, mixed-media, and short social explainers. Use when an agent must turn a topic, brief, research corpus, product, process, policy, dataset, or complex idea into a factual, accessible, narrated, captioned, storyboarded, generated-media-ready explainer video with claim review, localization, pacing, variants, and QA. --- # Explainer video production Produce an explainer only after defining what the audience should understand, believe, decide, or do differently after watching. Treat the video as a learning and decision artifact, not as a sequence of pretty scenes. This skill is provider-independent. Use the available generation, editing, composition, captioning, and review tools in the host environment, but keep the explainer logic, factual discipline, accessibility, and QA standards intact across providers. ## Non-negotiables - Start from audience, prior knowledge, and a measurable learning or decision objective. - Separate documented facts, source-backed inferences, production heuristics, and creative inventions. - Maintain a claim log for factual, commercial, comparative, health, safety, legal, financial, scientific, and public-service claims. - Escalate high-risk claims to the client, subject-matter expert, legal/compliance reviewer, medical reviewer, financial reviewer, or policy owner. Do not provide legal, medical, or financial advice. - Build accessibility into script, storyboard, captions, audio, data visuals, and delivery variants. Retrofitting is weaker and more expensive. - Re-check volatile provider/platform facts at production time: social aspect ratios, maximum lengths, safe areas, caption behavior, model inputs, model limits, pricing, regional availability, disclosure rules, and rights/licensing terms. - Never ask an image or video generation model to invent evidence, render precise charts, preserve exact legal/medical/scientific statements, or create readable fine text. Use deterministic layout/composition for facts, citations, captions, tables, UI text, labels, and charts. ## Intake: define the learning contract Before writing or generating, answer: - Audience: Who is this for, what do they already know, what do they misunderstand, what language/register do they use, and what accessibility/localization needs are known? - Objective: What single sentence should the viewer be able to say, do, or decide after watching? - Use case: education, product, onboarding, training, public-service, fundraising, policy, sales enablement, social awareness, internal change management, or technical concept. - Success evidence: quiz answer, demo completion, reduced support question, sign-up, policy comprehension, behavior change, stakeholder approval, or share/save. - Constraints: duration, platform, brand, required sources, must-include/must-avoid claims, restricted imagery, voice, captions, languages, review approvers, budget, and tool availability. - Risk tier: - Low: general concept, internal orientation, non-sensitive creative explanation. - Medium: product benefits, nonprofit/public-service behavior guidance, data claims, employment/training requirements. - High: health, safety, legal, financial, regulated products, children, political persuasion, crisis guidance, comparative advertising, public statistics with policy implications. Write the objective as an observable outcome, not a vague topic: - Weak: "Explain carbon offsets." - Strong: "After 90 seconds, a first-time buyer can tell the difference between reducing emissions and buying offsets, and knows to look for project verification before trusting a claim." ## Research and citation discipline Create a claim matrix before scripting. The matrix prevents persuasive polish from outrunning the evidence. | Field | Use | |---|---| | Claim | The exact stat在 GitHub 阅读完整来源 (打开外部页面)