Communitygithub.com

animation-script

Shows an agent how to plan, build, or cut "animation script" so the concrete output is a logo and a small brand sheet. The procedure moves through Animation Script, 1. Intake (ask before writing), 2. Structure. Use it when a new assignment calls for this craft.

animation-script とは?

animation-script is a Claude Code agent skill that shows an agent how to plan, build, or cut "animation script" so the concrete output is a logo and a small brand sheet. The procedure moves through Animation Script, 1. Intake (ask before writing), 2. Structure. Use it when a new assignment calls for this craft.

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/thinkalim/ai-video-preproduction-skills/tree/HEAD/skills/animation-script

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

Animation Script

The script is the product. The next-steps tab is a bonus that points to the next job. Never let the bonus crowd the script.

1. Intake (ask before writing)

Ask only for what is missing. One short message.

  • Brand and product name, exactly as the client says it.
  • Runtime (15, 30, 60, 90s). Everything scales from it.
  • Audience and the one thing they should do or feel.
  • Brand profile. Accept any of: a brand guide PDF, logo files, screenshots, style frames, a website URL, or typed notes. Read what is given and pull palette (hex codes if shown), type, logo usage rules, tone, tagline, mandatory and banned words. Summarize the profile in 5 to 8 lines and confirm it before writing. Save it as references/brands/<brand>.md from _template.md if the user wants to reuse it. If a saved profile exists, load it and confirm. If nothing is given, offer a neutral default and say so.
  • Logos and images are references. Never redraw a logo. Frames that hold it say [Logo].
  • Legal notes the client already has. Do not wait on them. Step 4 runs a first pass.

The source can be partial. Work from what exists. Flag gaps, never fill them with invention.

2. Structure

  • Frames = runtime / 5, adjusted by 1 or 2 so timecodes land clean. 30s is about 6, 60s about 12.
  • Build an arc before writing lines: hook, problem, turn, proof, product, payoff, lockup. Short spots compress it. Use any section names the brief gives as the spine.

3. House style

VISUAL

  • Motion-graphic direction in present tense: "animates on," "snaps into place," "resolves into."
  • Lead the key element in CAPS: ORANGE SIGNAL NODE, WATERFALL CHART.
  • 2 to 3 full sentences: what animates, how it moves and eases, how it hands off to the next frame. One clear idea per frame. Name the palette only when it carries meaning.
  • Describe something a designer can draw. No abstractions like "innovation flows."
  • Final frame is the logo lockup.

AUDIO (VO)

  • Final copy, read verbatim, written to be spoken: natural, complete sentences that carry a real thought and connect frame to frame. No strings of fragments, no stacked taglines. One fragment at the close, if it earns it.
  • Budget: about 2 words per second. 30s = 50 to 65. 60s = 110 to 130. 90s = 160 to 190. Intro and lockup frames stay light. Trim the densest frames first.
  • Never invent stats, quotes or claims. Use the source as written. Attribute quotes.
  • No em dashes. No filler. No AI phrasing ("unlock," "seamless," "in today's world").

TITLES

  • 2 to 6 words. Echo the VO beat, never repeat it word for word.
  • Product frame: Introducing [Product]. Final: [Logo] plus tagline.
  • Put required legal text in the frame it belongs to, marked LEGAL:.

FRAME

  • {n}\n\n{start}-{end} seconds. Contiguous. No gaps. Ends at runtime.

4. Legal first pass

Clients are often marketers who have not looped in legal. Run a first pass on the finished script so problems surface early. This is a flag list, not legal advice. Always say so once.

Check every frame for:

  • Claims: numbers, "best," "#1," "fastest," "proven," "guaranteed." Each needs a source, date and scope. No source in the brief means flag it.
  • Comparisons to competitors, named or implied.
  • Testimonials and quotes: written approval, real results, disclosure if paid (FTC).
  • Regulated categories: health, supplements, finance, insurance, kids, alcohol, environmental ("green," "sustainable," "recyclable"). Flag any benefit claim.
  • Pricing, offers, free trials: terms and dates on screen.
  • Trademarks: client marks at first use, third-party brands, logos, app UIs.
  • Rights: music, stock, likeness, fonts.
  • Accessibility: on-screen text held long enough to read, captions planned.

For each flag: frame number, the exact words, the risk in one line, a safer rewrite. If a fix is clean and keeps the meaning, offer it. Never change approved copy silently.

5. Next steps (bonus, keep it tight)

Written to the NEXT STEPS tab. Suggestions, clearly labeled as such.

  • Summary: one sentence on what the video says and to whom.
  • Treatment notes: 3 to 5 lines. Look, motion style, pacing, music and VO tone, transitions.
  • Style anchor: one reusable sentence describing the visual world (palette, render style, lighting, texture, aspect ratio). Every frame prompt starts from it so frames match.
  • Frame prompts: one per frame, for image tools. Format: subject, composition and camera, key elements, palette, mood. Concrete nouns. No text inside images unless it is the logo frame. No real people or trademarked characters unless the client owns them.
  • Legal flags: from step 4.
  • Open questions: anything the client must confirm (stats, assets, approvals).

6. Render

Write frames and notes to JSON, then run the builder. The builder owns formatting.

python scripts/build_script.py frames.json outputs/<name>.xlsx \
    --title "<Brand> - <Project>" --runtime "60-seconds" --notes notes.json

Each frame: frame, time, visual, audio, title, prompt. notes.json: summary, treatment (list), style_anchor, legal_flags (list), open_questions (list). Examples: references/frames_example.json, references/notes_example.json.

Filename: use the project code if given (PRJ001_Brand_Project_Script_v1.xlsx), otherwise <Brand>_<Project>_Script_v1.xlsx.

Review pass (always, before presenting)

Every answer runs twice. The user never sees the first draft.

  1. Draft the full answer.
  2. Review it the way a demanding creative director and producer would, against the checklist below and every rule in this skill. Read the copy as if hearing it in a client meeting. Mark every miss.
  3. Fix every miss, then present only the revised version.
  4. End with one line: Review pass: <what changed>, or Review pass: no changes needed.

This applies to every step that produces something: research, options, copy, specs and files. For a file, build it, open or render it, check it, then fix and rebuild before handing it over.

Checklist

  • Timecodes run without gaps and end at the runtime. VO sits inside budget. Builder warnings at zero.
  • VO reads naturally aloud as complete thoughts that connect frame to frame, not stacked taglines.
  • Every VISUAL tells the animator what to build: what animates, how it moves and eases, how it transitions.
  • No invented stats, quotes, names or claims. Legal pass complete. No em dashes, no AI phrasing.

7. Check, then present

  • The builder checks timecodes (gapless, ending at runtime) and prints the VO count against a 2 words per second budget. Fix every warning.
  • No invented numbers. No em dashes. Legal pass done and flags listed.
  • Present the file. Then 2 to 4 lines: the arc, frame count, VO word count, top legal flags.
  • Make nothing extra unless asked.

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

関連スキル