← WidemileCONTENT HISTORY

Update to Widemile

Snapshot Oct 29, 2026 · 00:05 UTC · version 1.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for editor-workflows

Skill instructions — Now says: `prostudio_editor_guide_get`, `prostudio_editor_get`, and the dedicated Editor operation tools. The read returns the resolved timelineId, timeline catalog,...

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

Save Widemile and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 13:07 UTC

`prostudio_surface_contract_get`, `prostudio_editor_get`, and `prostudio_editor_apply`. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability. - Editing one generate...

After

Oct 29, 2026 · 00:05 UTC

`prostudio_editor_guide_get`, `prostudio_editor_get`, and the dedicated Editor operation tools. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability. - Editing one ...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -7,16 +7,20 @@
 
 ## Tool requirements
 
-- **Core timeline work:** `prostudio_surface_contract_get`, `prostudio_editor_get`, and `prostudio_editor_apply`. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability.
+- **Core timeline work:** `prostudio_editor_guide_get`, `prostudio_editor_get`, and the dedicated Editor operation tools. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability.
 - **Conditional full-document operation:** `prostudio_editor_replace` only when the requested workflow genuinely requires replacing the complete timeline rather than applying a bounded batch.
 - **Conditional source and version edits:** `prostudio_generations_list`, `prostudio_generation_get`, `prostudio_video_edit_prepare`, `prostudio_video_edit`, `prostudio_video_upscale_prepare`, `prostudio_video_upscale`, `prostudio_image_edit_prepare`, `prostudio_image_edit`, and `prostudio_job_status`, selecting only the pair required by the requested operation.
 - This declaration does not activate tools. Use only the tools required by the selected branch. If a required tool is absent from the current scoped catalog and `load_prostudio_tools` is available, call it with the missing outcome before claiming the capability is unavailable; do not call it when the tool is already available. If retrieval still exposes no matching tool, report that limitation.
 
-- Editing one generated video version is distinct from assembling the workspace timeline. For trim, crop or aspect ratio, cinematic color, film grain, automatic styled captions, or upscale on one source video, use `prostudio_video_edit_prepare` with every requested change in one `edits` object, then execute the exact `prostudio_video_edit` action. One session creates one new version. Never call `prostudio_editor_apply` for clip-version edits and never create a separate version for each change.
+- Editing one generated video version is distinct from assembling the workspace timeline. For trim, crop or aspect ratio, cinematic color, film grain, automatic styled captions, or upscale on one source video, use `prostudio_video_edit_prepare` with every requested change in one `edits` object, then execute the exact `prostudio_video_edit` action. One session creates one new version. Never call the dedicated Editor operation tools for clip-version edits and never create a separate version for each change.
 - To edit one completed generated image, use `prostudio_image_edit_prepare` followed by the exact approved `prostudio_image_edit` action. It supports percentage-edge crop, 2x or 4x upscale, layer separation at Automatic, 1K, 1.5K or 2K, and crop combined with one AI operation. Layer separation bills the actual generated layer count within the approved ceiling. Upscale and layer separation must run sequentially using the first completed version as the second input. Never represent these tools as generation models.
-- For timeline work, inspect the Editor surface contract when needed, read the latest workspace/editor state, then use `prostudio_editor_apply` with the smallest complete batch and current `expectedVersion`. Use only stable ids from tools or current state, verify the returned timeline, and re-read before retrying a version conflict. Never invent ids or silently replace the whole timeline to recover.
+- For timeline work, read `prostudio_editor_get`, consult `prostudio_editor_guide_get` for grading defaults when needed, then use the dedicated operation tool with flat arguments and current `expectedVersion`. Carry its returned version into dependent edits. Operation schemas are published upfront. Use only stable ids from tools or current state, verify the returned timeline, and re-read before retrying a version conflict. Never invent ids or silently replace the whole timeline to recover.
 
-- **Multiple timelines:** read the catalog with `prostudio_editor_get`, then use `prostudio_editor_project_update` and the current expectedVersion to create, select, rename or remove a timeline. Duplicate with action `{type:"create",id,name,duplicateId}`. Use only existing IDs from the catalog, except a newly chosen creation ID. Always carry the exact timelineId through reads, apply, replace, export and history. Omitting it operates on the active timeline and must not be used to guess another named timeline.
-- **Local timeline adjustments:** the live surface contract describes grading, opacity, curves, embedded LUTs, visual/audio fades, text/caption styling and group move/duplicate/split commands. Use `set_clip_properties.patch.adjustments` with the complete current grade or published defaults, preserving unrelated values; use null to reset. Opacity belongs inside adjustments. Never invent property names or use clip-version generation merely to apply these non-destructive timeline changes.
+- **Multiple timelines:** read the catalog with `prostudio_editor_get`, then use `prostudio_editor_timeline_create`, `prostudio_editor_timeline_select`, `prostudio_editor_timeline_rename` or `prostudio_editor_timeline_remove` with current expectedVersion. Duplicate with `prostudio_editor_timeline_duplicate` and `{id,name,sourceTimelineId}`. Use only existing IDs from the catalog, except a newly chosen creation ID. Always carry the exact timelineId through reads, apply, replace, export and history. Omitting it operates on the active timeline and must not be used to guess another named timeline.
+- **Local timeline adjustments:** each dedicated tool schema describes grading, opacity, curves, embedded LUTs, visual/audio fades, text/caption styling and group move/duplicate/split commands. Use `prostudio_editor_set_clip_properties` with `patch.adjustments` containing the complete current grade or published defaults, preserving unrelated values; use null to reset. Opacity belongs inside adjustments. Never invent property names or use clip-version generation merely to apply these non-destructive timeline changes.
 - **Saved undo/redo:** `prostudio_editor_history` uses direction undo/redo, timelineId and current expectedVersion. Check history.canUndo/canRedo from the read first. It restores one persisted batch, including saved UI edits, and survives restarts. The version always increases. Unsaved browser gestures are not part of this journal. A new edit clears redo.
 - **Export:** call `prostudio_editor_export` with the exact timelineId and the version returned by the last successful edit, plus a fresh UUID idempotencyKey. Poll `prostudio_job_status` and preview the durable result before claiming delivery.
+
+## Dedicated timeline operations
+
+Use `prostudio_editor_add_track`, `prostudio_editor_remove_track`, `prostudio_editor_add_clips`, `prostudio_editor_move_clip`, `prostudio_editor_move_clips`, `prostudio_editor_duplicate_clips`, `prostudio_editor_set_clip_duration`, `prostudio_editor_set_clip_properties`, `prostudio_editor_set_track_properties`, `prostudio_editor_split_clip`, `prostudio_editor_split_clips`, `prostudio_editor_remove_clips`, `prostudio_editor_remove_audio_companion`, `prostudio_editor_replace_clip_media`, `prostudio_editor_reorder_track`, `prostudio_editor_reorder_tracks`, `prostudio_editor_set_sequence`, `prostudio_editor_correct_media_duration` or `prostudio_editor_remove_silent_audio` for the matching action. Pass flat fields; do not send `commands`, `action` or a `type` selector. Group tools atomically update multiple clips. Use the full-document replacement tool only for an explicitly intended complete-document rewrite.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: editor-workflows\ndescription: Edit a generated clip or image version and assemble the versioned ProStudio timeline using the correct distinct workflows.\n---\n\n# Editor workflows\n\n## Tool requirements\n\n- **Core timeline work:** `prostudio_surface_contract_get`, `prostudio_editor_get`, and `prostudio_editor_apply`. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability.\n- **Conditional full-document operation:** `prostudio_editor_replace` only when the requested workflow genuinely requires replacing the complete timeline rather than applying a bounded batch.\n- **Conditional source and version edits:** `prostudio_generations_list`, `prostudio_generation_get`, `prostudio_video_edit_prepare`, `prostudio_video_edit`, `prostudio_video_upscale_prepare`, `prostudio_video_upscale`, `prostudio_image_edit_prepare`, `prostudio_image_edit`, and `prostudio_job_status`, selecting only the pair required by the requested operation.\n- This declaration does not activate tools. Use only the tools required by the selected branch. If a required tool is absent from the current scoped catalog and `load_prostudio_tools` is available, call it with the missing outcome before claiming the capability is unavailable; do not call it when the tool is already available. If retrieval still exposes no matching tool, report that limitation.\n\n- Editing one generated video version is distinct from assembling the workspace timeline. For trim, crop or aspect ratio, cinematic color, film grain, automatic styled captions, or upscale on one source video, use `prostudio_video_edit_prepare` with every requested change in one `edits` object, then execute the exact `prostudio_video_edit` action. One session creates one new version. Never call `prostudio_editor_apply` for clip-version edits and never create a separate version for each change.\n- To edit one completed generated image, use `prostudio_image_edit_prepare` followed by the exact approved `prostudio_image_edit` action. It supports percentage-edge crop, 2x or 4x upscale, layer separation at Automatic, 1K, 1.5K or 2K, and crop combined with one AI operation. Layer separation bills the actual generated layer count within the approved ceiling. Upscale and layer separation must run sequentially using the first completed version as the second input. Never represent these tools as generation models.\n- For timeline work, inspect the Editor surface contract when needed, read the latest workspace/editor state, then use `prostudio_editor_apply` with the smallest complete batch and current `expectedVersion`. Use only stable ids from tools or current state, verify the returned timeline, and re-read before retrying a version conflict. Never invent ids or silently replace the whole timeline to recover.\n\n- **Multiple timelines:** read the catalog with `prostudio_editor_get`, then use `prostudio_editor_project_update` and the current expectedVersion to create, select, rename or remove a timeline. Duplicate with action `{type:\"create\",id,name,duplicateId}`. Use only existing IDs from the catalog, except a newly chosen creation ID. Always carry the exact timelineId through reads, apply, replace, export and history. Omitting it operates on the active timeline and must not be used to guess another named timeline.\n- **Local timeline adjustments:** the live surface contract describes grading, opacity, curves, embedded LUTs, visual/audio fades, text/caption styling and group move/duplicate/split commands. Use `set_clip_properties.patch.adjustments` with the complete current grade or published defaults, preserving unrelated values; use null to reset. Opacity belongs inside adjustments. Never invent property names or use clip-version generation merely to apply these non-destructive timeline changes.\n- **Saved undo/redo:** `prostudio_editor_history` uses direction undo/redo, timelineId and current expectedVersion. Check history.canUndo/canRedo from the read first. It restores one persisted batch, including saved UI edits, and survives restarts. The version always increases. Unsaved browser gestures are not part of this journal. A new edit clears redo.\n- **Export:** call `prostudio_editor_export` with the exact timelineId and the version returned by the last successful edit, plus a fresh UUID idempotencyKey. Poll `prostudio_job_status` and preview the durable result before claiming delivery.\n"
AFTER
"---\nname: editor-workflows\ndescription: Edit a generated clip or image version and assemble the versioned ProStudio timeline using the correct distinct workflows.\n---\n\n# Editor workflows\n\n## Tool requirements\n\n- **Core timeline work:** `prostudio_editor_guide_get`, `prostudio_editor_get`, and the dedicated Editor operation tools. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability.\n- **Conditional full-document operation:** `prostudio_editor_replace` only when the requested workflow genuinely requires replacing the complete timeline rather than applying a bounded batch.\n- **Conditional source and version edits:** `prostudio_generations_list`, `prostudio_generation_get`, `prostudio_video_edit_prepare`, `prostudio_video_edit`, `prostudio_video_upscale_prepare`, `prostudio_video_upscale`, `prostudio_image_edit_prepare`, `prostudio_image_edit`, and `prostudio_job_status`, selecting only the pair required by the requested operation.\n- This declaration does not activate tools. Use only the tools required by the selected branch. If a required tool is absent from the current scoped catalog and `load_prostudio_tools` is available, call it with the missing outcome before claiming the capability is unavailable; do not call it when the tool is already available. If retrieval still exposes no matching tool, report that limitation.\n\n- Editing one generated video version is distinct from assembling the workspace timeline. For trim, crop or aspect ratio, cinematic color, film grain, automatic styled captions, or upscale on one source video, use `prostudio_video_edit_prepare` with every requested change in one `edits` object, then execute the exact `prostudio_video_edit` action. One session creates one new version. Never call the dedicated Editor operation tools for clip-version edits and never create a separate version for each change.\n- To edit one completed generated image, use `prostudio_image_edit_prepare` followed by the exact approved `prostudio_image_edit` action. It supports percentage-edge crop, 2x or 4x upscale, layer separation at Automatic, 1K, 1.5K or 2K, and crop combined with one AI operation. Layer separation bills the actual generated layer count within the approved ceiling. Upscale and layer separation must run sequentially using the first completed version as the second input. Never represent these tools as generation models.\n- For timeline work, read `prostudio_editor_get`, consult `prostudio_editor_guide_get` for grading defaults when needed, then use the dedicated operation tool with flat arguments and current `expectedVersion`. Carry its returned version into dependent edits. Operation schemas are published upfront. Use only stable ids from tools or current state, verify the returned timeline, and re-read before retrying a version conflict. Never invent ids or silently replace the whole timeline to recover.\n\n- **Multiple timelines:** read the catalog with `prostudio_editor_get`, then use `prostudio_editor_timeline_create`, `prostudio_editor_timeline_select`, `prostudio_editor_timeline_rename` or `prostudio_editor_timeline_remove` with current expectedVersion. Duplicate with `prostudio_editor_timeline_duplicate` and `{id,name,sourceTimelineId}`. Use only existing IDs from the catalog, except a newly chosen creation ID. Always carry the exact timelineId through reads, apply, replace, export and history. Omitting it operates on the active timeline and must not be used to guess another named timeline.\n- **Local timeline adjustments:** each dedicated tool schema describes grading, opacity, curves, embedded LUTs, visual/audio fades, text/caption styling and group move/duplicate/split commands. Use `prostudio_editor_set_clip_properties` with `patch.adjustments` containing the complete current grade or published defaults, preserving unrelated values; use null to reset. Opacity belongs inside adjustments. Never invent property names or use clip-version generation merely to apply these non-destructive timeline changes.\n- **Saved undo/redo:** `prostudio_editor_history` uses direction undo/redo, timelineId and current expectedVersion. Check history.canUndo/canRedo from the read first. It restores one persisted batch, including saved UI edits, and survives restarts. The version always increases. Unsaved browser gestures are not part of this journal. A new edit clears redo.\n- **Export:** call `prostudio_editor_export` with the exact timelineId and the version returned by the last successful edit, plus a fresh UUID idempotencyKey. Poll `prostudio_job_status` and preview the durable result before claiming delivery.\n\n## Dedicated timeline operations\n\nUse `prostudio_editor_add_track`, `prostudio_editor_remove_track`, `prostudio_editor_add_clips`, `prostudio_editor_move_clip`, `prostudio_editor_move_clips`, `prostudio_editor_duplicate_clips`, `prostudio_editor_set_clip_duration`, `prostudio_editor_set_clip_properties`, `prostudio_editor_set_track_properties`, `prostudio_editor_split_clip`, `prostudio_editor_split_clips`, `prostudio_editor_remove_clips`, `prostudio_editor_remove_audio_companion`, `prostudio_editor_replace_clip_media`, `prostudio_editor_reorder_track`, `prostudio_editor_reorder_tracks`, `prostudio_editor_set_sequence`, `prostudio_editor_correct_media_duration` or `prostudio_editor_remove_silent_audio` for the matching action. Pass flat fields; do not send `commands`, `action` or a `type` selector. Group tools atomically update multiple clips. Use the full-document replacement tool only for an explicitly intended complete-document rewrite.\n"
Full snapshot data
{
  "description": "Edit a generated clip or image version and assemble the versioned ProStudio timeline using the correct distinct workflows.",
  "included_files": [],
  "name": "editor-workflows",
  "skill_md_contents": "---\nname: editor-workflows\ndescription: Edit a generated clip or image version and assemble the versioned ProStudio timeline using the correct distinct workflows.\n---\n\n# Editor workflows\n\n## Tool requirements\n\n- **Core timeline work:** `prostudio_editor_guide_get`, `prostudio_editor_get`, and the dedicated Editor operation tools. The read returns the resolved timelineId, timeline catalog, version, complete current timeline and saved-history availability.\n- **Conditional full-document operation:** `prostudio_editor_replace` only when the requested workflow genuinely requires replacing the complete timeline rather than applying a bounded batch.\n- **Conditional source and version edits:** `prostudio_generations_list`, `prostudio_generation_get`, `prostudio_video_edit_prepare`, `prostudio_video_edit`, `prostudio_video_upscale_prepare`, `prostudio_video_upscale`, `prostudio_image_edit_prepare`, `prostudio_image_edit`, and `prostudio_job_status`, selecting only the pair required by the requested operation.\n- This declaration does not activate tools. Use only the tools required by the selected branch. If a required tool is absent from the current scoped catalog and `load_prostudio_tools` is available, call it with the missing outcome before claiming the capability is unavailable; do not call it when the tool is already available. If retrieval still exposes no matching tool, report that limitation.\n\n- Editing one generated video version is distinct from assembling the workspace timeline. For trim, crop or aspect ratio, cinematic color, film grain, automatic styled captions, or upscale on one source video, use `prostudio_video_edit_prepare` with every requested change in one `edits` object, then execute the exact `prostudio_video_edit` action. One session creates one new version. Never call the dedicated Editor operation tools for clip-version edits and never create a separate version for each change.\n- To edit one completed generated image, use `prostudio_image_edit_prepare` followed by the exact approved `prostudio_image_edit` action. It supports percentage-edge crop, 2x or 4x upscale, layer separation at Automatic, 1K, 1.5K or 2K, and crop combined with one AI operation. Layer separation bills the actual generated layer count within the approved ceiling. Upscale and layer separation must run sequentially using the first completed version as the second input. Never represent these tools as generation models.\n- For timeline work, read `prostudio_editor_get`, consult `prostudio_editor_guide_get` for grading defaults when needed, then use the dedicated operation tool with flat arguments and current `expectedVersion`. Carry its returned version into dependent edits. Operation schemas are published upfront. Use only stable ids from tools or current state, verify the returned timeline, and re-read before retrying a version conflict. Never invent ids or silently replace the whole timeline to recover.\n\n- **Multiple timelines:** read the catalog with `prostudio_editor_get`, then use `prostudio_editor_timeline_create`, `prostudio_editor_timeline_select`, `prostudio_editor_timeline_rename` or `prostudio_editor_timeline_remove` with current expectedVersion. Duplicate with `prostudio_editor_timeline_duplicate` and `{id,name,sourceTimelineId}`. Use only existing IDs from the catalog, except a newly chosen creation ID. Always carry the exact timelineId through reads, apply, replace, export and history. Omitting it operates on the active timeline and must not be used to guess another named timeline.\n- **Local timeline adjustments:** each dedicated tool schema describes grading, opacity, curves, embedded LUTs, visual/audio fades, text/caption styling and group move/duplicate/split commands. Use `prostudio_editor_set_clip_properties` with `patch.adjustments` containing the complete current grade or published defaults, preserving unrelated values; use null to reset. Opacity belongs inside adjustments. Never invent property names or use clip-version generation merely to apply these non-destructive timeline changes.\n- **Saved undo/redo:** `prostudio_editor_history` uses direction undo/redo, timelineId and current expectedVersion. Check history.canUndo/canRedo from the read first. It restores one persisted batch, including saved UI edits, and survives restarts. The version always increases. Unsaved browser gestures are not part of this journal. A new edit clears redo.\n- **Export:** call `prostudio_editor_export` with the exact timelineId and the version returned by the last successful edit, plus a fresh UUID idempotencyKey. Poll `prostudio_job_status` and preview the durable result before claiming delivery.\n\n## Dedicated timeline operations\n\nUse `prostudio_editor_add_track`, `prostudio_editor_remove_track`, `prostudio_editor_add_clips`, `prostudio_editor_move_clip`, `prostudio_editor_move_clips`, `prostudio_editor_duplicate_clips`, `prostudio_editor_set_clip_duration`, `prostudio_editor_set_clip_properties`, `prostudio_editor_set_track_properties`, `prostudio_editor_split_clip`, `prostudio_editor_split_clips`, `prostudio_editor_remove_clips`, `prostudio_editor_remove_audio_companion`, `prostudio_editor_replace_clip_media`, `prostudio_editor_reorder_track`, `prostudio_editor_reorder_tracks`, `prostudio_editor_set_sequence`, `prostudio_editor_correct_media_duration` or `prostudio_editor_remove_silent_audio` for the matching action. Pass flat fields; do not send `commands`, `action` or a `type` selector. Group tools atomically update multiple clips. Use the full-document replacement tool only for an explicitly intended complete-document rewrite.\n"
}

SHA-256 of public snapshot: c6bcb9b35c74edc7528b747dcb082878e2eb2c7c89c229954635bd167225c7e0