Update to Picsart
Snapshot Nov 11, 2026 · 00:08 UTC · version 2.5.0
Collection source: downloaded plugin package.
Instructions updated for scene-building-basics
Skill instructions — Now says: ## Coordinates A scene built by hand goes wrong first in its coordinates: - **A shape layer inside a composition starts at that composition's centre.** Set...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 7, 2026 · 00:09 UTC
No removed lines (ordering may have changed)
Nov 11, 2026 · 00:08 UTC
## Coordinates A scene built by hand goes wrong first in its coordinates: - **A shape layer inside a composition starts at that composition's centre.** Set its position to `[0, 0]` and draw the shape in the composition's own pixels, or...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -59,6 +59,26 @@ (`'crossfade'`, 0.3–0.5 s) suits a change of layout. Check the live catalog with `picsart_scene_capabilities` (`sections: ["transitions"]`) before naming any other transition. +## Coordinates + +A scene built by hand goes wrong first in its coordinates: +- **A shape layer inside a composition starts at that composition's centre.** Set its position to + `[0, 0]` and draw the shape in the composition's own pixels, or it lands half a frame off. +- **A mask is in the pixels of the composition that holds its layer**, not the layer's own: draw it + where it shows, never shifted by the layer's position, and it does not follow the layer when the + layer moves. A photo inside a card is masked in the card's pixels; a title wipe, in the frame's. +- **A composition placed as a layer needs its `bounds`** (`[width, height]` of its own pixels), or + it is fitted to its host: a 1000×1500 card comes out 1080×1620. `picsart_scene_validate` warns + `composition_fitted_to_host`. +- **A group's `scale` is a ratio**: 1 is full size, never 100. + +Check the first build with `picsart_scene_query_layout` at a few times before you export: a +layer 76,000 px wide or half a frame off shows there. + +**A scene written as a file** can go directly to tools that accept an inline `scene`: read the +file's JSON and pass that object. When an actual scene edit returns a `sceneUrl`, use that URL +for later calls. Do not make an unchanged edit just to obtain a URL. + ## Reusable parts When you build a custom character or a part the user may want to adjust, declare root `parameters` for the knobs they will want (pose, expression, timing, strength): plain names in their terms, tight `min`/`max` (not 0..4000), a `default`, a `group` per body part or concern, a `description`. A draggable point is `type: "vec2"` with `frame: "composition"`, or `frame: {"layer": "<id>"}`. Motion goes in root `actions` whose `parameters` tracks key only number, boolean, text, color, vec2 or vec3 parameters, with no `$eval` (`scene-animation-reference`, `references/named-actions.md`). `picsart_scene_tune` (see `motion-design-craft`) tunes what is declared, plus root layers' position.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: scene-building-basics\ndescription: Build and edit a scene with the scene tools - declaring media, audio and fonts as assets, layer trims, audio layers and transitions, reading the schema once before patching. Use whenever a use case composes or changes a scene document.\n---\n\n# Composing a scene\n\nRead the scene schema once before your first edit (`picsart_scene_capabilities` with sections\n`[\"schemaSummary\"]`, then `[\"schema:<Name>\"]` for each definition you need, never `[\"schema\"]` whole), then build and change the scene with `picsart_scene_patch`. For a first scene,\nthe `quick-merge-and-export` recipe (`picsart_scene_recipe`) holds a working tool-call sequence to start\nfrom.\n\n## Media\n\nA layer declares its file once in `assets` as `{ id, type: \"video\", uri: <url> }` and points at it\nby id: `content: { kind: \"media\", assetId: \"<id>\", fit, trim }`. The scene document has no\n`assetType` field and no `video` kind, and an `assetId` holding a URL is `unknown_asset_ref`. Keep\neach layer's `trim` in its own source's seconds, with BOTH `in` and `out`. Skip dead ranges: trim\naround them rather than speeding through them.\n\n## Audio\n\nVoice-over plays as `audio` layers (`content: { kind: \"audio\", assetId, trim: { in, out } }`), each\nwith its layer's `start` at the moment it is heard. A step's line starts 0.15 s after its panel\nappears, so the picture lands first. Every `trim` needs BOTH `in` and `out`; a trim\nwith only `in` is a `missing_field` error. Mute a recording's own track (`muted: true` on its media\ncontent) unless its sound is being kept. **If the scene schema ever lists no audio\nlayer, say so and stop** — do not export a silent video and do not invent a mix.\n\n## Fonts\n\n**Fonts are declared assets.** Declare the font once in `assets` (`{ id, type: \"font\", uri }`) and\nreference that `id` as `font.family` in every text and caption style; a family name the scene does\nnot declare fails to resolve at export. If a font cannot be found or does not resolve, name it to\nthe user; never swap in another font without saying so.\n\n**Name the weight in the face, not in `font.weight`.** `font.weight` renders only where the scene\nis resolved natively; a runtime that draws a translated scene ignores it and draws the face\n`font.family` names at its own weight (`validate_scene` warns `font_weight_no_op`). For bold text,\nuse a bold face, such as a catalog key like `acumin-pro-bold`, or a declared font asset of that\nweight, and leave `weight` out.\n\n**The face must draw every character.** A face that lacks a character draws nothing or a box in\nits place, and no font tool says which scripts a face covers. For words in basic Latin, most faces\nwill do. For accents or another script (Cyrillic, Greek, Arabic, Devanagari, Chinese, Japanese,\nKorean …), prefer a face whose name names that script, or search by the name of a family made for\nit. Then prove it on the first frame that carries the rarest characters; if any is missing, pick\nanother face, build again, and tell the user which face you used.\n\n## Overlays\n\n**An overlay never blinks.** When a caption, a title or a sticker follows another in the same\nplace, start it where the last one ends, and never let an overlay's opacity drop to 0 for a frame\nor two: a gap that short reads as a blink.\n\n## Transitions\n\nWhen a panel replaces the one before it, a hard cut is fine and keeps the energy; a soft seam\n(`'crossfade'`, 0.3–0.5 s) suits a change of layout. Check the live catalog with\n`picsart_scene_capabilities` (`sections: [\"transitions\"]`) before naming any other transition.\n\n## Reusable parts\n\nWhen you build a custom character or a part the user may want to adjust, declare root `parameters` for the knobs they will want (pose, expression, timing, strength): plain names in their terms, tight `min`/`max` (not 0..4000), a `default`, a `group` per body part or concern, a `description`. A draggable point is `type: \"vec2\"` with `frame: \"composition\"`, or `frame: {\"layer\": \"<id>\"}`. Motion goes in root `actions` whose `parameters` tracks key only number, boolean, text, color, vec2 or vec3 parameters, with no `$eval` (`scene-animation-reference`, `references/named-actions.md`). `picsart_scene_tune` (see `motion-design-craft`) tunes what is declared, plus root layers' position.\n""---\nname: scene-building-basics\ndescription: Build and edit a scene with the scene tools - declaring media, audio and fonts as assets, layer trims, audio layers and transitions, reading the schema once before patching. Use whenever a use case composes or changes a scene document.\n---\n\n# Composing a scene\n\nRead the scene schema once before your first edit (`picsart_scene_capabilities` with sections\n`[\"schemaSummary\"]`, then `[\"schema:<Name>\"]` for each definition you need, never `[\"schema\"]` whole), then build and change the scene with `picsart_scene_patch`. For a first scene,\nthe `quick-merge-and-export` recipe (`picsart_scene_recipe`) holds a working tool-call sequence to start\nfrom.\n\n## Media\n\nA layer declares its file once in `assets` as `{ id, type: \"video\", uri: <url> }` and points at it\nby id: `content: { kind: \"media\", assetId: \"<id>\", fit, trim }`. The scene document has no\n`assetType` field and no `video` kind, and an `assetId` holding a URL is `unknown_asset_ref`. Keep\neach layer's `trim` in its own source's seconds, with BOTH `in` and `out`. Skip dead ranges: trim\naround them rather than speeding through them.\n\n## Audio\n\nVoice-over plays as `audio` layers (`content: { kind: \"audio\", assetId, trim: { in, out } }`), each\nwith its layer's `start` at the moment it is heard. A step's line starts 0.15 s after its panel\nappears, so the picture lands first. Every `trim` needs BOTH `in` and `out`; a trim\nwith only `in` is a `missing_field` error. Mute a recording's own track (`muted: true` on its media\ncontent) unless its sound is being kept. **If the scene schema ever lists no audio\nlayer, say so and stop** — do not export a silent video and do not invent a mix.\n\n## Fonts\n\n**Fonts are declared assets.** Declare the font once in `assets` (`{ id, type: \"font\", uri }`) and\nreference that `id` as `font.family` in every text and caption style; a family name the scene does\nnot declare fails to resolve at export. If a font cannot be found or does not resolve, name it to\nthe user; never swap in another font without saying so.\n\n**Name the weight in the face, not in `font.weight`.** `font.weight` renders only where the scene\nis resolved natively; a runtime that draws a translated scene ignores it and draws the face\n`font.family` names at its own weight (`validate_scene` warns `font_weight_no_op`). For bold text,\nuse a bold face, such as a catalog key like `acumin-pro-bold`, or a declared font asset of that\nweight, and leave `weight` out.\n\n**The face must draw every character.** A face that lacks a character draws nothing or a box in\nits place, and no font tool says which scripts a face covers. For words in basic Latin, most faces\nwill do. For accents or another script (Cyrillic, Greek, Arabic, Devanagari, Chinese, Japanese,\nKorean …), prefer a face whose name names that script, or search by the name of a family made for\nit. Then prove it on the first frame that carries the rarest characters; if any is missing, pick\nanother face, build again, and tell the user which face you used.\n\n## Overlays\n\n**An overlay never blinks.** When a caption, a title or a sticker follows another in the same\nplace, start it where the last one ends, and never let an overlay's opacity drop to 0 for a frame\nor two: a gap that short reads as a blink.\n\n## Transitions\n\nWhen a panel replaces the one before it, a hard cut is fine and keeps the energy; a soft seam\n(`'crossfade'`, 0.3–0.5 s) suits a change of layout. Check the live catalog with\n`picsart_scene_capabilities` (`sections: [\"transitions\"]`) before naming any other transition.\n\n## Coordinates\n\nA scene built by hand goes wrong first in its coordinates:\n- **A shape layer inside a composition starts at that composition's centre.** Set its position to\n `[0, 0]` and draw the shape in the composition's own pixels, or it lands half a frame off.\n- **A mask is in the pixels of the composition that holds its layer**, not the layer's own: draw it\n where it shows, never shifted by the layer's position, and it does not follow the layer when the\n layer moves. A photo inside a card is masked in the card's pixels; a title wipe, in the frame's.\n- **A composition placed as a layer needs its `bounds`** (`[width, height]` of its own pixels), or\n it is fitted to its host: a 1000×1500 card comes out 1080×1620. `picsart_scene_validate` warns\n `composition_fitted_to_host`.\n- **A group's `scale` is a ratio**: 1 is full size, never 100.\n\nCheck the first build with `picsart_scene_query_layout` at a few times before you export: a\nlayer 76,000 px wide or half a frame off shows there.\n\n**A scene written as a file** can go directly to tools that accept an inline `scene`: read the\nfile's JSON and pass that object. When an actual scene edit returns a `sceneUrl`, use that URL\nfor later calls. Do not make an unchanged edit just to obtain a URL.\n\n## Reusable parts\n\nWhen you build a custom character or a part the user may want to adjust, declare root `parameters` for the knobs they will want (pose, expression, timing, strength): plain names in their terms, tight `min`/`max` (not 0..4000), a `default`, a `group` per body part or concern, a `description`. A draggable point is `type: \"vec2\"` with `frame: \"composition\"`, or `frame: {\"layer\": \"<id>\"}`. Motion goes in root `actions` whose `parameters` tracks key only number, boolean, text, color, vec2 or vec3 parameters, with no `$eval` (`scene-animation-reference`, `references/named-actions.md`). `picsart_scene_tune` (see `motion-design-craft`) tunes what is declared, plus root layers' position.\n"Full snapshot data
{
"description": "Build and edit a scene with the scene tools - declaring media, audio and fonts as assets, layer trims, audio layers and transitions, reading the schema once before patching. Use whenever a use case composes or changes a scene document.",
"included_files": [],
"name": "scene-building-basics",
"skill_md_contents": "---\nname: scene-building-basics\ndescription: Build and edit a scene with the scene tools - declaring media, audio and fonts as assets, layer trims, audio layers and transitions, reading the schema once before patching. Use whenever a use case composes or changes a scene document.\n---\n\n# Composing a scene\n\nRead the scene schema once before your first edit (`picsart_scene_capabilities` with sections\n`[\"schemaSummary\"]`, then `[\"schema:<Name>\"]` for each definition you need, never `[\"schema\"]` whole), then build and change the scene with `picsart_scene_patch`. For a first scene,\nthe `quick-merge-and-export` recipe (`picsart_scene_recipe`) holds a working tool-call sequence to start\nfrom.\n\n## Media\n\nA layer declares its file once in `assets` as `{ id, type: \"video\", uri: <url> }` and points at it\nby id: `content: { kind: \"media\", assetId: \"<id>\", fit, trim }`. The scene document has no\n`assetType` field and no `video` kind, and an `assetId` holding a URL is `unknown_asset_ref`. Keep\neach layer's `trim` in its own source's seconds, with BOTH `in` and `out`. Skip dead ranges: trim\naround them rather than speeding through them.\n\n## Audio\n\nVoice-over plays as `audio` layers (`content: { kind: \"audio\", assetId, trim: { in, out } }`), each\nwith its layer's `start` at the moment it is heard. A step's line starts 0.15 s after its panel\nappears, so the picture lands first. Every `trim` needs BOTH `in` and `out`; a trim\nwith only `in` is a `missing_field` error. Mute a recording's own track (`muted: true` on its media\ncontent) unless its sound is being kept. **If the scene schema ever lists no audio\nlayer, say so and stop** — do not export a silent video and do not invent a mix.\n\n## Fonts\n\n**Fonts are declared assets.** Declare the font once in `assets` (`{ id, type: \"font\", uri }`) and\nreference that `id` as `font.family` in every text and caption style; a family name the scene does\nnot declare fails to resolve at export. If a font cannot be found or does not resolve, name it to\nthe user; never swap in another font without saying so.\n\n**Name the weight in the face, not in `font.weight`.** `font.weight` renders only where the scene\nis resolved natively; a runtime that draws a translated scene ignores it and draws the face\n`font.family` names at its own weight (`validate_scene` warns `font_weight_no_op`). For bold text,\nuse a bold face, such as a catalog key like `acumin-pro-bold`, or a declared font asset of that\nweight, and leave `weight` out.\n\n**The face must draw every character.** A face that lacks a character draws nothing or a box in\nits place, and no font tool says which scripts a face covers. For words in basic Latin, most faces\nwill do. For accents or another script (Cyrillic, Greek, Arabic, Devanagari, Chinese, Japanese,\nKorean …), prefer a face whose name names that script, or search by the name of a family made for\nit. Then prove it on the first frame that carries the rarest characters; if any is missing, pick\nanother face, build again, and tell the user which face you used.\n\n## Overlays\n\n**An overlay never blinks.** When a caption, a title or a sticker follows another in the same\nplace, start it where the last one ends, and never let an overlay's opacity drop to 0 for a frame\nor two: a gap that short reads as a blink.\n\n## Transitions\n\nWhen a panel replaces the one before it, a hard cut is fine and keeps the energy; a soft seam\n(`'crossfade'`, 0.3–0.5 s) suits a change of layout. Check the live catalog with\n`picsart_scene_capabilities` (`sections: [\"transitions\"]`) before naming any other transition.\n\n## Coordinates\n\nA scene built by hand goes wrong first in its coordinates:\n- **A shape layer inside a composition starts at that composition's centre.** Set its position to\n `[0, 0]` and draw the shape in the composition's own pixels, or it lands half a frame off.\n- **A mask is in the pixels of the composition that holds its layer**, not the layer's own: draw it\n where it shows, never shifted by the layer's position, and it does not follow the layer when the\n layer moves. A photo inside a card is masked in the card's pixels; a title wipe, in the frame's.\n- **A composition placed as a layer needs its `bounds`** (`[width, height]` of its own pixels), or\n it is fitted to its host: a 1000×1500 card comes out 1080×1620. `picsart_scene_validate` warns\n `composition_fitted_to_host`.\n- **A group's `scale` is a ratio**: 1 is full size, never 100.\n\nCheck the first build with `picsart_scene_query_layout` at a few times before you export: a\nlayer 76,000 px wide or half a frame off shows there.\n\n**A scene written as a file** can go directly to tools that accept an inline `scene`: read the\nfile's JSON and pass that object. When an actual scene edit returns a `sceneUrl`, use that URL\nfor later calls. Do not make an unchanged edit just to obtain a URL.\n\n## Reusable parts\n\nWhen you build a custom character or a part the user may want to adjust, declare root `parameters` for the knobs they will want (pose, expression, timing, strength): plain names in their terms, tight `min`/`max` (not 0..4000), a `default`, a `group` per body part or concern, a `description`. A draggable point is `type: \"vec2\"` with `frame: \"composition\"`, or `frame: {\"layer\": \"<id>\"}`. Motion goes in root `actions` whose `parameters` tracks key only number, boolean, text, color, vec2 or vec3 parameters, with no `$eval` (`scene-animation-reference`, `references/named-actions.md`). `picsart_scene_tune` (see `motion-design-craft`) tunes what is declared, plus root layers' position.\n"
}SHA-256 of public snapshot: 287ab9a56f22772ed788ecc4f18f5c00df2ce5f738004168e4292cc32adfecfb