← PicsartCONTENT HISTORY

Update to Picsart

Snapshot Nov 3, 2026 · 18:14 UTC · version 2.3.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for scene-building-basics

Skill instructions — Now says: ## Overlays **An overlay never blinks.** When a caption, a title or a sticker follows another in the same place, start it where the last one ends, and never...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Picsart and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 27, 2026 · 06:06 UTC

No removed lines (ordering may have changed)

After

Nov 3, 2026 · 18:14 UTC

## Overlays **An overlay never blinks.** When a caption, a title or a sticker follows another in the same place, start it where the last one ends, and never let an overlay's opacity drop to 0 for a frame or two: a gap that short reads as...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -47,6 +47,12 @@
 it. Then prove it on the first frame that carries the rarest characters; if any is missing, pick
 another face, build again, and tell the user which face you used.
 
+## Overlays
+
+**An overlay never blinks.** When a caption, a title or a sticker follows another in the same
+place, start it where the last one ends, and never let an overlay's opacity drop to 0 for a frame
+or two: a gap that short reads as a blink.
+
 ## Transitions
 
 When a panel replaces the one before it, a hard cut is fine and keeps the energy; a soft seam
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\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## 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"
AFTER
"---\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"
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"
}

SHA-256 of public snapshot: ff950d8e53151148bca3e7747b51a960ce5d7dc0c53d8f36048e6226d2957417