{"id":70004,"plugin_id":"plugin_asdk_app_6a7026f78434819186579d93d20ab38b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:06:00.641Z","digest":"01ef5900ae10642a6d95487ecf92c334bb541f1678a1b05dbab7bb5fdc05367a","against":null,"payload":{"description":"The shared rules for motion graphics in a Tella video, used through the Tella MCP, covering one look per video, graphics timed to the spoken word, placement clear of the speaker, and checking the result. Load it whenever you add text, titles or animated graphics to a video, including a general request to add motion graphics, and before any other graphics skill. Text overlays work everywhere; richer graphics use the Tella Motion tools, which are in beta and not available in every workspace.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":399}],"name":"tella-motion-design","skill_md_contents":"---\nname: tella-motion-design\ndescription: The shared rules for motion graphics in a Tella video, used through the Tella MCP, covering one look per video, graphics timed to the spoken word, placement clear of the speaker, and checking the result. Load it whenever you add text, titles or animated graphics to a video, including a general request to add motion graphics, and before any other graphics skill. Text overlays work everywhere; richer graphics use the Tella Motion tools, which are in beta and not available in every workspace.\n---\n\n# Motion design for Tella videos\n\nGraphics in a Tella video serve someone talking or showing their screen. A good graphic lands on the word it illustrates, says less than the speaker, stays long enough to read, and gets out of the way. Restraint looks designed; effects look like a template.\n\nThis skill needs the Tella MCP. If tools such as `get_timeline` are missing, follow the connection steps in the `tella` skill first.\n\n## Tools\n\nUse text overlays first: they work without Tella Motion and stay editable like any text. Use highlights to point at UI in a screen recording. Use a Tella Motion document (an overlay, or b-roll through `add_layout` with Tella Motion `media`) only when several elements must move together, such as a diagram or a chart. Add a Tella Motion clip only when the user asks, since it changes the video's length. If the Tella Motion tools are missing, say so and do what the rest can.\n\n## A request for the whole video\n\nFor a general request (\"add some motion graphics\"), go through the video stretch by stretch and give each part what it needs, loading the matching skill: the hook and key lines as type, numbers as callouts, a screen demo's steps as screen callouts, an explanation with a shape as a diagram, several things shown at once as a carousel, product screens as redrawn or parallax UI, and the call to action. Leave stretches that need nothing alone.\n\n## One look\n\nDecide the look before building and keep to it: one typeface (reuse the video's text presets or existing overlays when it has them), a few colours with one accent, and a clear hierarchy: the key word or number large and in the accent, supporting text smaller and plainer, the same size for the same role every time. One calm easing. No bouncy, elastic or spring easing. Every graphic has an exit. Check contrast against what is really behind the text, and don't add shadows or outlines it doesn't need.\n\n## Timing\n\nPlace each graphic from the transcript's word timings, not its sentences. Nothing appears before it is said: a graphic starts entering just before its first word, and a word-by-word reveal follows the speaker's pace. Keep each graphic up until its thought ends, and long enough to read (at least about 2 s). Things said in one breath go in one graphic rather than a quick run of swaps. One graphic leaves before the next arrives in the same place.\n\n## Between shots\n\nMotion carries across a cut: the next shot enters on the same axis and in the same direction the last one left, at the same speed, and the cut lands mid-move rather than after both have stopped. Keep one main direction of travel for the video, and use another only when it means something (up for a reveal).\n\n## Words\n\nA graphic is a headline, not a caption: at most seven words on screen, usually one to four. Never put a whole spoken sentence on screen. Use the speaker's words, shortened only when the short form keeps the meaning, including any condition (\"retried within an hour\", not \"auto retry\"). Never add a claim, number, name or link the video doesn't give; check against the transcript and the video's title.\n\n## Placement\n\nPut graphics in the empty part of the frame, clear of the whole person (head, shoulders and body, not just the face), the cursor, the camera bubble and whatever the speaker is showing. Look at a frame of each kind of shot to see where those are. Keep everything well inside the frame, and put the same kind of graphic in the same place each time.\n\n## Build, check, report\n\n1. Read the video: `get_video`, `get_timeline`, `get_transcript` with word timings, frames of each shot, and the existing overlays and presets.\n2. Show a short plan, one row per graphic with its time, words and placement, then build it without asking again; the user can undo or ask for changes.\n3. Build the first graphic of each kind, check it, then make the others from it (the same fields or a saved text preset; `duplicate_motion_document` for Tella Motion) instead of rebuilding each one.\n4. Check every graphic with `get_clip_frame`, then read the overlays back against the transcript: on its words, readable, not overlapping, nothing covered, every name and number right. Then measure:\n   - each line stays at least 0.3 s a word plus 0.5 s, and its text is at least about 28 px tall at 1080p;\n   - `get_filmstrip` at -0.2, -0.1, 0, +0.1 and +0.2 s around every cut and every graphic's entry and exit: no blank, white or black frame, nothing half-built or jumping. Overlay and b-roll times are on their clip's timeline; add the clip's start for video-wide tools.\n\n   Fix everything that is wrong, unreadable or broken before reporting; mention smaller polish.\n5. Report the look and each graphic with its time.\n\nKeep text live: never turn it into an image to work around a rendering problem; report the problem as a Tella bug instead. For text behind the speaker use `depth: \"behind_presenter\"`. If a write's outcome is unclear, read the state back before retrying, and never add the same graphic twice.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}