Update to Tella

{
  "description": "Analyze, edit, and visually verify Tella videos through the Tella MCP. Use for understanding a Tella video or improving it with trims, layouts, overlays, and related timeline edits.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 377
    }
  ],
  "name": "tella",
  "skill_md_contents": "---\nname: tella\ndescription: Analyze, edit, and visually verify Tella videos through the Tella MCP. Use for understanding a Tella video or improving it with trims, layouts, overlays, and related timeline edits.\n---\n\n# Tella Video Editor\n\nUse the Tella MCP to understand, edit, and verify a video. Match the user's scope; an analysis request does not imply permission to edit.\n\n## Before you start: connect the Tella MCP\n\nThis skill drives Tella through its MCP server at `https://api.tella.com/mcp` (Streamable HTTP, OAuth). If no Tella MCP tools such as `get_timeline` are available, connect the server first:\n\n- Claude Code: `claude mcp add --transport http --scope user tella https://api.tella.com/mcp`\n- Codex: `codex mcp add tella --url https://api.tella.com/mcp`\n- Cursor, Claude Desktop: add an `mcpServers` entry that runs `npx mcp-remote https://api.tella.com/mcp`\n- Anything else: any Streamable HTTP MCP client; a personal API key (`tella_pk_…`, created at Settings → API Keys in Tella) works as the bearer token\n\nThe first connection opens Tella in the browser to sign in and pick a workspace. The full tool reference is at https://www.tella.com/docs/mcp-server.\n\n## Approach\n\nFor a broad understanding of the video, start with `get_timeline` and one or more `get_storyboard` calls. Use `get_video_frame` for an exact still and `get_video_preview` for motion, audio, transitions, or cut continuity. GIF frames are for thumbnails, not analysis. A returned preview URL counts as verification only after its MP4 has actually been opened and reviewed. Inspect only as much as the task and remaining uncertainty require.\n\nInterpret informal editing terms by their intended outcome, not as rigid presets. When a request such as “fully edit,” “auto edit,” or “rough edit” leaves materially different treatments open, inspect the video and present a recommended edit package plus the relevant options: pacing and how much may be cut; layouts, zooms, or cropping; b-roll, text, or media overlays; audio, captions, or chapters; and, when relevant, format such as aspect ratio. Describe what the plan does, never what it leaves out: publishing details such as metadata, thumbnail, caption delivery, or export are a choice to offer when they seem wanted, not a disclaimer. Clarify ambiguous terms such as “overlay,” then ask the user to approve or adjust the scope before the first write. Translate their choices into tools rather than making them design the edit. Treat the approved package as the scope, and reconfirm before materially departing from its intended pacing, duration, or treatment.\n\nOnce the scope is clear, implement a coherent, watchable first pass while preserving the video's meaning. Treat detected fillers and silences as edit candidates rather than automatic removals: pauses may communicate thought, reaction, waiting, or visible system behavior. To find and remove retakes, false starts, and other recording mistakes, use the `tella-remove-mistakes` skill. When the user asks to auto cut or tighten a whole recording in one go, use the `tella-auto-cut` skill: it cuts mistakes, fillers and silences without asking first, then cleans up the seams. “For YouTube” signals audience-facing pacing and presentation, not a fixed formula.\n\nEach clip has a base layout, addressed as `layoutId: \"base\"`: change it with `update_layout`, and use `add_layout` with a time range to change only a section of the clip. Users name layouts by the editor's picker labels, such as “Split Right Overlap”; use the kind and style the tool descriptions give for that label, not the nearest default variant. To lay out a clip automatically, use the `tella-auto-layouts` skill.\n\nFor motion graphics (animated text, titles, diagrams, number callouts, screen annotations), load the `tella-motion-design` skill for the shared rules, then the skill for the graphic: `tella-kinetic-type`, `tella-title-cards`, `tella-explainer-graphics`, `tella-data-callouts`, `tella-screen-callouts`, `tella-carousels`, `tella-transitions` or `tella-camera-moves`. For product UI in Tella Motion, use `tella-ui-redraw` (rebuilt screens), `tella-ui-interactions` (UI that acts) or `tella-ui-parallax` (depth from a screenshot).\n\nTo plan what to say and show before recording, or to turn a loose take into a script to record again, use the `tella-plan-video` skill. For a launch, promo or feature video, use `tella-launch-video`; for a video from release notes, `tella-changelog-video`.\n\nWhen the video needs footage only the user can give (a talking intro, a retake, a voiceover, a screen walkthrough, or a new video with no clips yet), hand recording over to them instead of describing where to click: `get_recording_link` returns a `url` that opens their own recorder (the browser, or the Tella Mac or Windows app if they record there) and adds the take as a new clip at the end of the video. For a new video, call `create_video` without `sourceId` first and pass its id. Give the user the URL and ask them to tell you when they're done; you get no signal when the recording finishes. Then find the new clip with `list_clips` and carry on editing. If the clip isn't there yet, it may still be uploading: wait a moment and read again rather than asking them to record twice. If you wrote what they should say, give it to them with the link.\n\nTreat “b-roll” as supporting media that usually belongs in a media-bearing layout, taking over or sharing the main visual area. Use an overlay when the media is intended to float over the primary scene.\n\nWhen a different format is requested or clearly suits the intended platform, `update_video` dimensions can change the output canvas and aspect ratio—for example, 1080×1920 for a 9:16 mobile video. Uncommon dimensions can be intentional, including Tella’s Auto ratio, so do not normalize them unless the user asks or the target format requires it. Changing dimensions remaps existing layouts rather than changing the source footage, so inspect and adjust the layouts afterward.\n\nFor event-driven edits, prefer recorded metadata such as mouse events and transcript timing when available, then inspect the surrounding video before placing effects. Create derivative clips or reels from duplicates rather than repurposing the original. To turn a video into a vertical Short, Reel or TikTok, use the `tella-short` skill.\n\nResolve the time domain before editing: video-level inspection uses cumulative video playback time; most clip edits use clip-local playback time with cuts applied; `update_clip` cut definitions use raw recording time. Apply cut ranges measured from one playback state together, and re-read the timeline after a cut before calculating more.\n\nAfter a structural change that affects timing or composition, re-read and inspect the result before placing dependent zooms, overlays, chapters, or thumbnails.\n\nWhere a setting exists at video and clip scope, clip values act as overrides or opt-outs from the video default. Inspect existing values and update the narrowest intended scope instead of writing both reflexively.\n\nIf a write has an unclear outcome, re-read the current state before retrying; never blindly repeat additive or cutting operations. Some changes process asynchronously, so wait for the rendered result before evaluating them.\n\nWhen the user wants to watch the video change while you edit it, or before a long run of edits, offer a live preview: `get_live_preview_link` returns a `url` to a player of the editor's preview that shows each saved edit a moment later, without re-rendering. Give the user that URL exactly as returned (its access token is in the `#token=` fragment), or open it yourself if your host can show web pages. Anyone with the link can watch without signing in until `expiresAt` (24 hours), so share it only with the user, and ask for a fresh one after it expires. It is for the user to watch; it does not replace checking your edits with `get_video_frame` and `get_video_preview`.\n\nAfter editing, re-read the timeline and inspect the affected ranges with the appropriate tools. Iterate until the requested result is present and no obvious problem remains. Report what changed, what the inspection actually verified, and any remaining uncertainty.\n"
}