Update to Creative Claw

{
  "name": "creativeclaw-add-video-intro-outro",
  "description": "Add an intro, outro, or both to an existing video with Creative Claw. Use when the user wants title cards, logo stings, opening copy, closing calls to action, or supplied bookend clips merged around a main video.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 558
    },
    {
      "relative_path": "references/job-recovery.md",
      "size_in_bytes": 3786
    },
    {
      "relative_path": "references/media-assembly.md",
      "size_in_bytes": 3876
    },
    {
      "relative_path": "references/platform-upload.md",
      "size_in_bytes": 1416
    },
    {
      "relative_path": "references/workflow-basics.md",
      "size_in_bytes": 7159
    }
  ],
  "skill_md_contents": "---\nname: creativeclaw-add-video-intro-outro\ndescription: \"Add an intro, outro, or both to an existing video with Creative Claw. Use when the user wants title cards, logo stings, opening copy, closing calls to action, or supplied bookend clips merged around a main video.\"\n---\n\n# Add Video Intro and Outro\n\nRead [shared execution guidance](references/workflow-basics.md) once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.\n\nCreate or reuse opening and closing segments, then concatenate them around the main video. This skill owns the bookend workflow and final merge; it does not assume the intro or outro must be HTML-rendered.\n\n## Choose the segment source\n\n- If the user supplies intro or outro clips, import them and use those clips.\n- If the user explicitly asks for HTML, HyperFrames, or code-rendered title cards, use `creativeclaw-render-html-video` for the requested segments.\n- If the user asks for an intro/outro but has not chosen how to create it, suggest HTML rendering as a strong option for exact text, fonts, colors, and logos. Wait for explicit acceptance before calling `render_html_video`.\n- If the user wants generative cinematic footage, use `creativeclaw-generate-video` instead.\n\nThis boundary matters: an intro/outro request alone does not authorize the HTML video tool.\n\n## Workflow\n\n1. Identify the main video's durable URL, dimensions, aspect ratio, frame rate, audio, and intended platform. Import local or attached files before editing.\n2. Use the requested segments, copy, logo, duration, audio, and transition choices. Infer minor styling defaults; ask only about missing copy or a material unresolved choice, and do not repeat earlier approvals.\n3. Create or load the intro and outro. Prefer the main video's dimensions and frame rate. For existing mismatched frames, use merge fit controls rather than extra scale jobs. Trim only when requested.\n4. Resolve every queued segment job with `check_job` and inspect each clip before merging.\n5. Call `merge_media` with `operation:\"merge_videos\"` in exact playback order: intro when present, main video, then outro when present. Set `canvas_video_index` to the main video's zero-based index and `video_fit:\"pad\"` to preserve mismatched frames, unless cropping is authorized. Read [assembly guidance](references/media-assembly.md) for fit and audio limitations.\n6. Resolve the merge job with `check_job`, inspect the cut points, audio, dimensions, and total duration, then give the final asset a useful name and tags when supported.\n\n## Example: explicit HTML bookends\n\nFor “Use HTML to add a 2-second logo intro and a 3-second CTA outro to this video”:\n\n1. Render the intro with `creativeclaw-render-html-video` at the main video's dimensions and FPS.\n2. Render the outro the same way.\n3. Resolve both jobs.\n4. Merge in order:\n\n```text\nmerge_media({\n  operation: \"merge_videos\",\n  video_urls: [\"<intro-url>\", \"<main-video-url>\", \"<outro-url>\"],\n  canvas_video_index: 1,\n  video_fit: \"pad\",\n  pad_color: \"black\"\n})\n```\n\n5. Resolve the returned merge job with `check_job`.\n\nIf only one bookend is requested, omit the other URL. If finished intro/outro clips were supplied, skip HTML rendering and merge them directly.\n\n## Gotchas\n\n- `merge_videos` is a hard concatenation; it does not create dissolves, crossfades, or audio transitions. Design the last frames of the intro and first frames of the outro to meet the main clip cleanly, or explain when the requested transition needs a different editing path.\n- Preserve the main canvas with explicit fit controls. Normalize incompatible codecs only through an available tool exposing that control.\n- Preserve exact visible copy and logo treatment. Keep bookends short unless the user specifies otherwise; do not invent a slogan or call to action.\n- HTML-rendered segments and the merge are asynchronous. A job ID is not a finished clip.\n- If the main video's audio must continue under a bookend or fade across a cut, simple concatenation is insufficient. Surface that limitation before rendering segments.\n"
}