{"id":85171,"plugin_id":"plugin_asdk_app_6a18d4c190a0819186e6b129a09e931e","kind":"skill","collection_source":"plugin_package","comparison_source":"plugin_package","observed_at":"2026-11-07T00:09:12.104Z","digest":"8c3624fe898f3e516831be12e36fd2f64eb4d35429d091f63dc95d909e57c674","against":78710,"payload":{"description":"The shortest path from media URLs to a rendered file - merge or concatenate several videos into one with the montage template, sample frames from a scene into a contact sheet, and export any valid scene to a file. Use when asked to merge, join or concatenate clips, to preview a scene as frames, or to render a scene, and no other skill covers the job.","included_files":[{"relative_path":"scripts/montage_params.py","size_in_bytes":5236}],"name":"quick-merge-and-export","skill_md_contents":"---\nname: quick-merge-and-export\ndescription: The shortest path from media URLs to a rendered file - merge or concatenate several videos into one with the montage template, sample frames from a scene into a contact sheet, and export any valid scene to a file. Use when asked to merge, join or concatenate clips, to preview a scene as frames, or to render a scene, and no other skill covers the job.\nmetadata:\n  category: authoring\n  version: '1'\n---\n\n# Scene quickstart\n\nThree short jobs, each a fixed chain of tools. Every tool takes media by URL. None reads a local\npath, a `file://` URI or inlined file bytes, and such a source is refused before anything renders.\nFor a file the user has only on their device, call `picsart_drive_upload_ask`: it opens a\ndrag-and-drop upload. The call itself returns no URL; the file's URL arrives on the user's next\nturn, as widget context (or in their message), so read it there before going on. Pass `detected_files` when you can see the file\nname, and `known_urls` to offer URLs already made in this conversation.\n\n## Merge several videos into one\n\nThe montage template plays its clips one after another and renders one file.\n\n1. **Probe each clip.** Call `picsart_media_probe` once per clip URL for its width, height\n   and duration. Skip a clip whose exact size and duration an earlier tool result already gave. A\n   missing `durationSeconds` means the duration is unknown, not zero: follow the probe's own note\n   on that field.\n2. **Build the parameters.** Write the clips as JSON, one object per clip with `uri`, `width`,\n   `height`, `duration` from the probe, and optionally `in` and `out` (the trim, in seconds),\n   `fit` (`cover`, `contain` or `fill`) and `align` (one of nine positions such as `top left` or `center`, the default).\n   Then run `scripts/montage_params.py`:\n\n   ```bash\n   python3 scripts/montage_params.py --transition crossfade --transition-duration 0.4 clips.json\n   ```\n\n   It prints the complete `picsart_scene_apply_template` arguments: `uri:\n   \"scene://montage\"`, `mode: \"bootstrap\"`, and `parameters` with `transition`,\n   `transitionDuration` and `clips`. Omit `--width` and `--height`: the canvas matches the largest\n   clip and the frame rate follows the clips. Pass both only to deliberately change the aspect\n   or size. For a smaller output file, use `picsart_scene_export`'s `resolution`. Pass\n   `--transition \"\"` for a hard cut. Use `fit` and `align` when a clip's shape differs from the\n   output's, as with portrait and landscape clips in one montage.\n\n   **Without a shell, write the script's output yourself.** The template's clips do not take the\n   input shape above. Each clip becomes `duration` (`out` minus `in`) plus a `content` object\n   that carries the probed asset, the trim, `fit` and `align`. A hard cut is `transition: \"\"` with\n   `transitionDuration: 0`. Here clip 1 is trimmed to 0–4 s of a 12 s clip, then a hard cut to\n   all 8 s of clip 2:\n\n   ```json\n   {\"uri\": \"scene://montage\", \"mode\": \"bootstrap\", \"parameters\": {\n     \"transition\": \"\", \"transitionDuration\": 0,\n     \"clips\": [\n       {\"duration\": 4, \"content\": {\"kind\": \"media\",\n         \"asset\": {\"type\": \"video\", \"uri\": \"https://…/a.mp4\", \"width\": 1080, \"height\": 1920, \"duration\": 12},\n         \"trim\": {\"in\": 0, \"out\": 4}, \"fit\": \"cover\", \"align\": \"center\"}},\n       {\"duration\": 8, \"content\": {\"kind\": \"media\",\n         \"asset\": {\"type\": \"video\", \"uri\": \"https://…/b.mp4\", \"width\": 1080, \"height\": 1920, \"duration\": 8},\n         \"trim\": {\"in\": 0, \"out\": 8}, \"fit\": \"cover\", \"align\": \"center\"}}]}}\n   ```\n3. **Bootstrap the scene.** Call `picsart_scene_apply_template` with those arguments,\n   unchanged. These arguments are complete, so this job needs no schema or template lookup. The\n   composition's duration is the sum of the clip durations: never set it by hand.\n4. **Validate.** Call `picsart_scene_validate` on the returned `scene`.\n5. **Render.** Call `picsart_scene_export` with the scene and `mediaType: \"mp4\"`. It replies with a job\n   receipt: follow it as picsart-video-rules says until it reports `urls`, one merged file.\n\nThe montage is sequential: each clip starts where the one before it ends. For layers that play at\nthe same time, as in picture-in-picture, write overlapping layers with\n`picsart_scene_patch` instead.\n\nThe rendered length is not snapped to the frame grid, so a montage of exact decimal trims can land\na frame or two short of the target. That is expected, not an error.\n\n## Sample frames from a scene\n\n1. Have a valid scene: one a template returned, or one written with `picsart_scene_patch`.\n2. Call `picsart_scene_validate` on it.\n3. Call `picsart_scene_contact_sheet` with either `times` (exact timestamps) or `frames` (that many\n   evenly spaced), never both, and optionally `resolution`. It returns `frames`, each a `time` and\n   a `url`: low-resolution previews, not the deliverable.\n\n## Render a scene to a file\n\n1. Have a valid scene, as above. A scene this skill's merge job built needs no other check.\n   Otherwise confirm its shape with `picsart_scene_capabilities`, sections `[\"schemaSummary\"]` then `[\"schema:<Name>\"]`, or\n   `[\"template:<uri>\"]` for a template.\n2. Call `picsart_scene_validate` on it.\n3. Call `picsart_scene_export` with `mediaType` (`mp4`, `png` and the others it lists), and\n   optionally `resolution`, `fps`, `duration` and `startTime`. Pass `fileName`, a short name from\n   the scene's subject, so a file saved to Drive gets a real name. It replies with a job receipt\n   by default; follow it as picsart-video-rules says until it reports `urls`.\n\nExport renders on a server and needs a signed-in user. Follow picsart-video-rules's rule on cost before you\ncall it.\n"},"changes":[{"path":"/skill_md_contents","type":"changed","before":"---\nname: quick-merge-and-export\ndescription: The shortest path from media URLs to a rendered file - merge or concatenate several videos into one with the montage template, sample frames from a scene into a contact sheet, and export any valid scene to a file. Use when asked to merge, join or concatenate clips, to preview a scene as frames, or to render a scene, and no other skill covers the job.\nmetadata:\n  category: authoring\n  version: '1'\n---\n\n# Scene quickstart\n\nThree short jobs, each a fixed chain of tools. Every tool takes media by URL. None reads a local\npath, a `file://` URI or inlined file bytes, and such a source is refused before anything renders.\nFor a file the user has only on their device, call `picsart_drive_upload_ask`: it opens a\ndrag-and-drop upload. The call itself returns no URL; the file's URL arrives on the user's next\nturn, as widget context (or in their message), so read it there before going on. Pass `detected_files` when you can see the file\nname, and `known_urls` to offer URLs already made in this conversation.\n\n## Merge several videos into one\n\nThe montage template plays its clips one after another and renders one file.\n\n1. **Probe each clip.** Call `picsart_media_probe` once per clip URL for its width, height\n   and duration. Skip a clip whose exact size and duration an earlier tool result already gave. A\n   missing `durationSeconds` means the duration is unknown, not zero: follow the probe's own note\n   on that field.\n2. **Build the parameters.** Write the clips as JSON, one object per clip with `uri`, `width`,\n   `height`, `duration` from the probe, and optionally `in` and `out` (the trim, in seconds),\n   `fit` (`cover`, `contain` or `fill`) and `align` (one of nine positions such as `top left` or `center`, the default).\n   Then run `scripts/montage_params.py`:\n\n   ```bash\n   python3 scripts/montage_params.py --transition crossfade --transition-duration 0.4 clips.json\n   ```\n\n   It prints the complete `picsart_scene_apply_template` arguments: `uri:\n   \"scene://montage\"`, `mode: \"bootstrap\"`, and `parameters` with `transition`,\n   `transitionDuration` and `clips`. Omit `--width` and `--height`: the canvas matches the largest\n   clip and the frame rate follows the clips. Pass both only to deliberately change the aspect\n   or size. For a smaller output file, use `picsart_scene_export`'s `resolution`. Pass\n   `--transition \"\"` for a hard cut. Use `fit` and `align` when a clip's shape differs from the\n   output's, as with portrait and landscape clips in one montage.\n\n   **Without a shell, write the script's output yourself.** The template's clips do not take the\n   input shape above. Each clip becomes `duration` (`out` minus `in`) plus a `content` object\n   that carries the probed asset, the trim, `fit` and `align`. A hard cut is `transition: \"\"` with\n   `transitionDuration: 0`. Here clip 1 is trimmed to 0–4 s of a 12 s clip, then a hard cut to\n   all 8 s of clip 2:\n\n   ```json\n   {\"uri\": \"scene://montage\", \"mode\": \"bootstrap\", \"parameters\": {\n     \"transition\": \"\", \"transitionDuration\": 0,\n     \"clips\": [\n       {\"duration\": 4, \"content\": {\"kind\": \"media\",\n         \"asset\": {\"type\": \"video\", \"uri\": \"https://…/a.mp4\", \"width\": 1080, \"height\": 1920, \"duration\": 12},\n         \"trim\": {\"in\": 0, \"out\": 4}, \"fit\": \"cover\", \"align\": \"center\"}},\n       {\"duration\": 8, \"content\": {\"kind\": \"media\",\n         \"asset\": {\"type\": \"video\", \"uri\": \"https://…/b.mp4\", \"width\": 1080, \"height\": 1920, \"duration\": 8},\n         \"trim\": {\"in\": 0, \"out\": 8}, \"fit\": \"cover\", \"align\": \"center\"}}]}}\n   ```\n3. **Bootstrap the scene.** Call `picsart_scene_apply_template` with those arguments,\n   unchanged. These arguments are complete, so this job needs no schema or template lookup. The\n   composition's duration is the sum of the clip durations: never set it by hand.\n4. **Validate.** Call `picsart_scene_validate` on the returned `scene`.\n5. **Optional: the editable project.** `picsart_scene_translate` returns the scene as a full\n   engine project, with each transition wired at its seam. Skip it when only the file is wanted.\n6. **Render.** Call `picsart_scene_export` with the scene and `mediaType: \"mp4\"`. It replies with a job\n   receipt: follow it as picsart-video-rules says until it reports `urls`, one merged file.\n\nThe montage is sequential: each clip starts where the one before it ends. For layers that play at\nthe same time, as in picture-in-picture, write overlapping layers with\n`picsart_scene_patch` instead.\n\nThe rendered length is not snapped to the frame grid, so a montage of exact decimal trims can land\na frame or two short of the target. That is expected, not an error.\n\n## Sample frames from a scene\n\n1. Have a valid scene: one a template returned, or one written with `picsart_scene_patch`.\n2. Call `picsart_scene_validate` on it.\n3. Call `picsart_scene_contact_sheet` with either `times` (exact timestamps) or `frames` (that many\n   evenly spaced), never both, and optionally `resolution`. It returns `frames`, each a `time` and\n   a `url`: low-resolution previews, not the deliverable.\n\n## Render a scene to a file\n\n1. Have a valid scene, as above. A scene this skill's merge job built needs no other check.\n   Otherwise confirm its shape with `picsart_scene_capabilities`, sections `[\"schemaSummary\"]` then `[\"schema:<Name>\"]`, or\n   `[\"template:<uri>\"]` for a template.\n2. Call `picsart_scene_validate` on it.\n3. Call `picsart_scene_export` with `mediaType` (`mp4`, `png` and the others it lists), and\n   optionally `resolution`, `fps`, `duration` and `startTime`. Pass `fileName`, a short name from\n   the scene's subject, so a file saved to Drive gets a real name. It replies with a job receipt\n   by default; follow it as picsart-video-rules says until it reports `urls`.\n\nExport renders on a server and needs a signed-in user. Follow picsart-video-rules's rule on cost before you\ncall it.\n","after":"---\nname: quick-merge-and-export\ndescription: The shortest path from media URLs to a rendered file - merge or concatenate several videos into one with the montage template, sample frames from a scene into a contact sheet, and export any valid scene to a file. Use when asked to merge, join or concatenate clips, to preview a scene as frames, or to render a scene, and no other skill covers the job.\nmetadata:\n  category: authoring\n  version: '1'\n---\n\n# Scene quickstart\n\nThree short jobs, each a fixed chain of tools. Every tool takes media by URL. None reads a local\npath, a `file://` URI or inlined file bytes, and such a source is refused before anything renders.\nFor a file the user has only on their device, call `picsart_drive_upload_ask`: it opens a\ndrag-and-drop upload. The call itself returns no URL; the file's URL arrives on the user's next\nturn, as widget context (or in their message), so read it there before going on. Pass `detected_files` when you can see the file\nname, and `known_urls` to offer URLs already made in this conversation.\n\n## Merge several videos into one\n\nThe montage template plays its clips one after another and renders one file.\n\n1. **Probe each clip.** Call `picsart_media_probe` once per clip URL for its width, height\n   and duration. Skip a clip whose exact size and duration an earlier tool result already gave. A\n   missing `durationSeconds` means the duration is unknown, not zero: follow the probe's own note\n   on that field.\n2. **Build the parameters.** Write the clips as JSON, one object per clip with `uri`, `width`,\n   `height`, `duration` from the probe, and optionally `in` and `out` (the trim, in seconds),\n   `fit` (`cover`, `contain` or `fill`) and `align` (one of nine positions such as `top left` or `center`, the default).\n   Then run `scripts/montage_params.py`:\n\n   ```bash\n   python3 scripts/montage_params.py --transition crossfade --transition-duration 0.4 clips.json\n   ```\n\n   It prints the complete `picsart_scene_apply_template` arguments: `uri:\n   \"scene://montage\"`, `mode: \"bootstrap\"`, and `parameters` with `transition`,\n   `transitionDuration` and `clips`. Omit `--width` and `--height`: the canvas matches the largest\n   clip and the frame rate follows the clips. Pass both only to deliberately change the aspect\n   or size. For a smaller output file, use `picsart_scene_export`'s `resolution`. Pass\n   `--transition \"\"` for a hard cut. Use `fit` and `align` when a clip's shape differs from the\n   output's, as with portrait and landscape clips in one montage.\n\n   **Without a shell, write the script's output yourself.** The template's clips do not take the\n   input shape above. Each clip becomes `duration` (`out` minus `in`) plus a `content` object\n   that carries the probed asset, the trim, `fit` and `align`. A hard cut is `transition: \"\"` with\n   `transitionDuration: 0`. Here clip 1 is trimmed to 0–4 s of a 12 s clip, then a hard cut to\n   all 8 s of clip 2:\n\n   ```json\n   {\"uri\": \"scene://montage\", \"mode\": \"bootstrap\", \"parameters\": {\n     \"transition\": \"\", \"transitionDuration\": 0,\n     \"clips\": [\n       {\"duration\": 4, \"content\": {\"kind\": \"media\",\n         \"asset\": {\"type\": \"video\", \"uri\": \"https://…/a.mp4\", \"width\": 1080, \"height\": 1920, \"duration\": 12},\n         \"trim\": {\"in\": 0, \"out\": 4}, \"fit\": \"cover\", \"align\": \"center\"}},\n       {\"duration\": 8, \"content\": {\"kind\": \"media\",\n         \"asset\": {\"type\": \"video\", \"uri\": \"https://…/b.mp4\", \"width\": 1080, \"height\": 1920, \"duration\": 8},\n         \"trim\": {\"in\": 0, \"out\": 8}, \"fit\": \"cover\", \"align\": \"center\"}}]}}\n   ```\n3. **Bootstrap the scene.** Call `picsart_scene_apply_template` with those arguments,\n   unchanged. These arguments are complete, so this job needs no schema or template lookup. The\n   composition's duration is the sum of the clip durations: never set it by hand.\n4. **Validate.** Call `picsart_scene_validate` on the returned `scene`.\n5. **Render.** Call `picsart_scene_export` with the scene and `mediaType: \"mp4\"`. It replies with a job\n   receipt: follow it as picsart-video-rules says until it reports `urls`, one merged file.\n\nThe montage is sequential: each clip starts where the one before it ends. For layers that play at\nthe same time, as in picture-in-picture, write overlapping layers with\n`picsart_scene_patch` instead.\n\nThe rendered length is not snapped to the frame grid, so a montage of exact decimal trims can land\na frame or two short of the target. That is expected, not an error.\n\n## Sample frames from a scene\n\n1. Have a valid scene: one a template returned, or one written with `picsart_scene_patch`.\n2. Call `picsart_scene_validate` on it.\n3. Call `picsart_scene_contact_sheet` with either `times` (exact timestamps) or `frames` (that many\n   evenly spaced), never both, and optionally `resolution`. It returns `frames`, each a `time` and\n   a `url`: low-resolution previews, not the deliverable.\n\n## Render a scene to a file\n\n1. Have a valid scene, as above. A scene this skill's merge job built needs no other check.\n   Otherwise confirm its shape with `picsart_scene_capabilities`, sections `[\"schemaSummary\"]` then `[\"schema:<Name>\"]`, or\n   `[\"template:<uri>\"]` for a template.\n2. Call `picsart_scene_validate` on it.\n3. Call `picsart_scene_export` with `mediaType` (`mp4`, `png` and the others it lists), and\n   optionally `resolution`, `fps`, `duration` and `startTime`. Pass `fileName`, a short name from\n   the scene's subject, so a file saved to Drive gets a real name. It replies with a job receipt\n   by default; follow it as picsart-video-rules says until it reports `urls`.\n\nExport renders on a server and needs a signed-in user. Follow picsart-video-rules's rule on cost before you\ncall it.\n"}],"summary":"Fields changed: 1. /skill_md_contents.","summary_kind":"deterministic","summary_metadata":{}}