Update to Widemile
Snapshot Oct 29, 2026 · 00:05 UTC · version 1.2.0
Collection source: downloaded plugin package.
Instructions updated for widemile
Skill instructions — Now says: charge in the account’s configured unit (EUR or credits) → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently...
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
Oct 24, 2026 · 13:07 UTC
credits → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost. - Storyboarding is optional. Use `prostudio_storyboard_get`, `prostudio_storyboar...
Oct 29, 2026 · 00:05 UTC
charge in the account’s configured unit (EUR or credits) → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost. - Storyboarding is optional. Use...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -22,9 +22,9 @@ - Keep durable creative facts in Widemile production memory and category-free canonical references instead of relying on chat history alone. References may contain ordered images, videos, or both; tags are organization only. - Use stable Widemile IDs in tool calls. Assign a reference's semantic purpose at each storyboard cut or generation binding, and resolve the selected media before preparing generation. - For uploaded user media, follow the server's consent flow and convert temporary host attachments into durable Widemile assets before referencing them. -- Treat every paid generation as `prepare → show exact plan and credits → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost. +- Treat every paid generation as `prepare → show exact plan and charge in the account’s configured unit (EUR or credits) → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost. - For Previs when exposed by the host, read live capabilities and the saved scene revision, then use native Blender jobs with the exact scene ID, expectedVersion and a fresh idempotency key. Use the existing authorization scope and reload after a revision conflict; do not require a storyboard or Brief. -- Storyboarding is optional. Use `prostudio_storyboard_get`, `prostudio_storyboard_replace` or `prostudio_storyboard_apply` only when requested or useful to the current objective. A missing storyboard never blocks other production work. Use `prostudio_storyboard_preview` to show it inline and `prostudio_storyboard_export` for PDF; neither preview nor PDF is a prerequisite to generation or editing. +- Storyboarding is optional. Use `prostudio_storyboard_get`, `prostudio_storyboard_replace` or the dedicated `prostudio_storyboard_scene_*` and `prostudio_storyboard_shot_*` tools only when requested or useful to the current objective. A missing storyboard never blocks other production work. Use `prostudio_storyboard_preview` to show it inline and `prostudio_storyboard_export` for PDF; neither preview nor PDF is a prerequisite to generation or editing. - For storyboard-driven video, each scene is one video generation and its ordered shots are the cuts inside that scene prompt. Bind their selected images as visual generation references through `continuityGenerationIds`, resolve their actual tokens, and use the stable scene ID as the generation workflow label. Preserve all chosen cuts and references within model limits; keep this workflow optional. - Use `preview` when the host supports MCP Apps. If it does not, present the durable media URLs, resource links, and structured results already returned by the standard MCP tools. Never make completion depend on a ChatGPT-only UI bridge. - Describe partial or unavailable capabilities exactly as reported by discovery tools. Do not imply that Widemile performed an operation the server did not confirm.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: widemile\ndescription: Plan and operate complete creative productions with Widemile. Use for production briefs, workspaces, assets, references, generative image/video/audio/music, editing or Previs work through the Widemile MCP server.\n---\n\n# Widemile\n\nUse the connected Widemile MCP server for production state and media operations. The host model remains responsible for reasoning, writing, critique, and tool sequencing.\n\n## Source of truth\n\nAt the start of an operational request, use the MCP server instructions and, when the host exposes resources, read `widemile://prostudio/workflow`. Those server-published instructions are authoritative and may contain newer capabilities or constraints than this skill.\n\nIn Codex and ChatGPT plugin runtimes, use the matching specialized skill bundled under `plugins/widemile/skills/`. In other MCP hosts, use `prostudio_skills_list` when discovery is needed and call `load_prostudio_skills` with the smallest semantic match before the first domain-specific operation. A loaded skill supplies instructions only: it does not enable operation tools, grant permissions, or change approval requirements.\n\nDo not recreate Widemile operations through browser automation or private HTTP calls. Use only the MCP tools and resources exposed by the connected server.\n\n## Portable workflow\n\n- Start from a listed or newly created workspace and read its production context before changing it.\n- Treat the saved Brief as one canonical Markdown document. Read it with `prostudio_brief_get` and save the complete Markdown with `prostudio_brief_replace`, using the current revision and preserving unrelated prose. The Brief is optional and never binds technical references or blocks production.\n- Keep durable creative facts in Widemile production memory and category-free canonical references instead of relying on chat history alone. References may contain ordered images, videos, or both; tags are organization only.\n- Use stable Widemile IDs in tool calls. Assign a reference's semantic purpose at each storyboard cut or generation binding, and resolve the selected media before preparing generation.\n- For uploaded user media, follow the server's consent flow and convert temporary host attachments into durable Widemile assets before referencing them.\n- Treat every paid generation as `prepare → show exact plan and credits → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost.\n- For Previs when exposed by the host, read live capabilities and the saved scene revision, then use native Blender jobs with the exact scene ID, expectedVersion and a fresh idempotency key. Use the existing authorization scope and reload after a revision conflict; do not require a storyboard or Brief.\n- Storyboarding is optional. Use `prostudio_storyboard_get`, `prostudio_storyboard_replace` or `prostudio_storyboard_apply` only when requested or useful to the current objective. A missing storyboard never blocks other production work. Use `prostudio_storyboard_preview` to show it inline and `prostudio_storyboard_export` for PDF; neither preview nor PDF is a prerequisite to generation or editing.\n- For storyboard-driven video, each scene is one video generation and its ordered shots are the cuts inside that scene prompt. Bind their selected images as visual generation references through `continuityGenerationIds`, resolve their actual tokens, and use the stable scene ID as the generation workflow label. Preserve all chosen cuts and references within model limits; keep this workflow optional.\n- Use `preview` when the host supports MCP Apps. If it does not, present the durable media URLs, resource links, and structured results already returned by the standard MCP tools. Never make completion depend on a ChatGPT-only UI bridge.\n- Describe partial or unavailable capabilities exactly as reported by discovery tools. Do not imply that Widemile performed an operation the server did not confirm.\n\nAsk only for decisions the user must make, especially consent, paid execution, destructive changes, and revision restore. Continue autonomously through safe read-only discovery and preparation.\n"
"---\nname: widemile\ndescription: Plan and operate complete creative productions with Widemile. Use for production briefs, workspaces, assets, references, generative image/video/audio/music, editing or Previs work through the Widemile MCP server.\n---\n\n# Widemile\n\nUse the connected Widemile MCP server for production state and media operations. The host model remains responsible for reasoning, writing, critique, and tool sequencing.\n\n## Source of truth\n\nAt the start of an operational request, use the MCP server instructions and, when the host exposes resources, read `widemile://prostudio/workflow`. Those server-published instructions are authoritative and may contain newer capabilities or constraints than this skill.\n\nIn Codex and ChatGPT plugin runtimes, use the matching specialized skill bundled under `plugins/widemile/skills/`. In other MCP hosts, use `prostudio_skills_list` when discovery is needed and call `load_prostudio_skills` with the smallest semantic match before the first domain-specific operation. A loaded skill supplies instructions only: it does not enable operation tools, grant permissions, or change approval requirements.\n\nDo not recreate Widemile operations through browser automation or private HTTP calls. Use only the MCP tools and resources exposed by the connected server.\n\n## Portable workflow\n\n- Start from a listed or newly created workspace and read its production context before changing it.\n- Treat the saved Brief as one canonical Markdown document. Read it with `prostudio_brief_get` and save the complete Markdown with `prostudio_brief_replace`, using the current revision and preserving unrelated prose. The Brief is optional and never binds technical references or blocks production.\n- Keep durable creative facts in Widemile production memory and category-free canonical references instead of relying on chat history alone. References may contain ordered images, videos, or both; tags are organization only.\n- Use stable Widemile IDs in tool calls. Assign a reference's semantic purpose at each storyboard cut or generation binding, and resolve the selected media before preparing generation.\n- For uploaded user media, follow the server's consent flow and convert temporary host attachments into durable Widemile assets before referencing them.\n- Treat every paid generation as `prepare → show exact plan and charge in the account’s configured unit (EUR or credits) → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost.\n- For Previs when exposed by the host, read live capabilities and the saved scene revision, then use native Blender jobs with the exact scene ID, expectedVersion and a fresh idempotency key. Use the existing authorization scope and reload after a revision conflict; do not require a storyboard or Brief.\n- Storyboarding is optional. Use `prostudio_storyboard_get`, `prostudio_storyboard_replace` or the dedicated `prostudio_storyboard_scene_*` and `prostudio_storyboard_shot_*` tools only when requested or useful to the current objective. A missing storyboard never blocks other production work. Use `prostudio_storyboard_preview` to show it inline and `prostudio_storyboard_export` for PDF; neither preview nor PDF is a prerequisite to generation or editing.\n- For storyboard-driven video, each scene is one video generation and its ordered shots are the cuts inside that scene prompt. Bind their selected images as visual generation references through `continuityGenerationIds`, resolve their actual tokens, and use the stable scene ID as the generation workflow label. Preserve all chosen cuts and references within model limits; keep this workflow optional.\n- Use `preview` when the host supports MCP Apps. If it does not, present the durable media URLs, resource links, and structured results already returned by the standard MCP tools. Never make completion depend on a ChatGPT-only UI bridge.\n- Describe partial or unavailable capabilities exactly as reported by discovery tools. Do not imply that Widemile performed an operation the server did not confirm.\n\nAsk only for decisions the user must make, especially consent, paid execution, destructive changes, and revision restore. Continue autonomously through safe read-only discovery and preparation.\n"
Full snapshot data
{
"description": "Plan and operate complete creative productions with Widemile. Use for production briefs, workspaces, assets, references, generative image/video/audio/music, editing or Previs work through the Widemile MCP server.",
"included_files": [],
"name": "widemile",
"skill_md_contents": "---\nname: widemile\ndescription: Plan and operate complete creative productions with Widemile. Use for production briefs, workspaces, assets, references, generative image/video/audio/music, editing or Previs work through the Widemile MCP server.\n---\n\n# Widemile\n\nUse the connected Widemile MCP server for production state and media operations. The host model remains responsible for reasoning, writing, critique, and tool sequencing.\n\n## Source of truth\n\nAt the start of an operational request, use the MCP server instructions and, when the host exposes resources, read `widemile://prostudio/workflow`. Those server-published instructions are authoritative and may contain newer capabilities or constraints than this skill.\n\nIn Codex and ChatGPT plugin runtimes, use the matching specialized skill bundled under `plugins/widemile/skills/`. In other MCP hosts, use `prostudio_skills_list` when discovery is needed and call `load_prostudio_skills` with the smallest semantic match before the first domain-specific operation. A loaded skill supplies instructions only: it does not enable operation tools, grant permissions, or change approval requirements.\n\nDo not recreate Widemile operations through browser automation or private HTTP calls. Use only the MCP tools and resources exposed by the connected server.\n\n## Portable workflow\n\n- Start from a listed or newly created workspace and read its production context before changing it.\n- Treat the saved Brief as one canonical Markdown document. Read it with `prostudio_brief_get` and save the complete Markdown with `prostudio_brief_replace`, using the current revision and preserving unrelated prose. The Brief is optional and never binds technical references or blocks production.\n- Keep durable creative facts in Widemile production memory and category-free canonical references instead of relying on chat history alone. References may contain ordered images, videos, or both; tags are organization only.\n- Use stable Widemile IDs in tool calls. Assign a reference's semantic purpose at each storyboard cut or generation binding, and resolve the selected media before preparing generation.\n- For uploaded user media, follow the server's consent flow and convert temporary host attachments into durable Widemile assets before referencing them.\n- Treat every paid generation as `prepare → show exact plan and charge in the account’s configured unit (EUR or credits) → explicit user approval → execute`. Reuse the prepared plan ID and exact arguments; never silently substitute a prompt, model, reference, or cost.\n- For Previs when exposed by the host, read live capabilities and the saved scene revision, then use native Blender jobs with the exact scene ID, expectedVersion and a fresh idempotency key. Use the existing authorization scope and reload after a revision conflict; do not require a storyboard or Brief.\n- Storyboarding is optional. Use `prostudio_storyboard_get`, `prostudio_storyboard_replace` or the dedicated `prostudio_storyboard_scene_*` and `prostudio_storyboard_shot_*` tools only when requested or useful to the current objective. A missing storyboard never blocks other production work. Use `prostudio_storyboard_preview` to show it inline and `prostudio_storyboard_export` for PDF; neither preview nor PDF is a prerequisite to generation or editing.\n- For storyboard-driven video, each scene is one video generation and its ordered shots are the cuts inside that scene prompt. Bind their selected images as visual generation references through `continuityGenerationIds`, resolve their actual tokens, and use the stable scene ID as the generation workflow label. Preserve all chosen cuts and references within model limits; keep this workflow optional.\n- Use `preview` when the host supports MCP Apps. If it does not, present the durable media URLs, resource links, and structured results already returned by the standard MCP tools. Never make completion depend on a ChatGPT-only UI bridge.\n- Describe partial or unavailable capabilities exactly as reported by discovery tools. Do not imply that Widemile performed an operation the server did not confirm.\n\nAsk only for decisions the user must make, especially consent, paid execution, destructive changes, and revision restore. Continue autonomously through safe read-only discovery and preparation.\n"
}SHA-256 of public snapshot: 1d6fa416fa88317ff60c6a5a9d724c1c6128455d9628c73686e6056769131dbc