Update to Widemile
Snapshot Oct 29, 2026 · 00:05 UTC · version 1.2.0
Collection source: downloaded plugin package.
Payment or plan references changed
Skill instructions — Now says: the dedicated Editor operation tools only when assembling finished episodes. - Billing display is controlled by the authenticated account. When...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 24, 2026 · 13:07 UTC
`prostudio_editor_apply` only when assembling finished episodes.
Oct 29, 2026 · 00:05 UTC
the dedicated Editor operation tools only when assembling finished episodes. - Billing display is controlled by the authenticated account. When `billingDisplay.unit` is `EUR`, present the returned euro charge and balances; otherwise pres...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -9,7 +9,7 @@ - **Creative Brief, when saving an approved direction:** `prostudio_brief_get` and `prostudio_brief_replace`. - **Conditional continuity:** `prostudio_references_list`, `prostudio_references_resolve`, and `inspect_prostudio_media` when cast, locations, props, or supplied footage need stable visual identity. -- **Conditional production:** `prostudio_models_list`, `prostudio_generation_prepare`, `prostudio_video_generate`, `prostudio_job_status`, and `prostudio_generation_get` only when the user requests generated footage; `prostudio_editor_get` and `prostudio_editor_apply` only when assembling finished episodes. +- **Conditional production:** `prostudio_models_list`, `prostudio_generation_prepare`, `prostudio_video_generate`, `prostudio_job_status`, and `prostudio_generation_get` only when the user requests generated footage; `prostudio_editor_get` and the dedicated Editor operation tools only when assembling finished episodes. - This declaration does not activate tools. Use only the tools needed for the requested deliverable. 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 unavailable. A story outline or prepared generation is not a finished episode. ## Shape the series @@ -32,3 +32,5 @@ - If the user requests generated footage, load `reference-management` for identity-bearing assets and `generation-planning` for the live model catalog. Plan supported clip durations and the episode's actual cut points; bind exact references for recurring people, wardrobe, products, props, and locations. Carry the series bible into every prompt without changing character identity or story order. Verify completed clips, dialogue, action, visual continuity, and the cliffhanger frame before assembling with `editor-workflows`. - Add exact titles, messages, and subtitles in post-production when possible rather than relying on video generation to spell small text. Keep dialogue intelligible in short mobile viewing sessions. Before paid generation, show the selected script, visual approach, clips and durations, reference strategy, model, and exact known credits; follow the host's required approval for prepared actions. - Deliver the requested artifact at its actual stage. For a produced episode, verify a playable assembled video and its runtime, not only a script or a set of pending clips. For a series, report which episodes are complete and which remain planned. + +- Billing display is controlled by the authenticated account. When `billingDisplay.unit` is `EUR`, present the returned euro charge and balances; otherwise present credits. Preserve prepared execution arguments and `expectedCredits` exactly, without displaying those machine values as prices.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: microdrama-series\ndescription: Develop and, when requested, produce a scripted episodic microdrama for mobile viewing; use for a series premise, episode map, scripts, or finished episodes, not for an unrelated standalone short or ordinary ad.\n---\n\n# Microdrama series\n\n## Tool requirements\n\n- **Creative Brief, when saving an approved direction:** `prostudio_brief_get` and `prostudio_brief_replace`.\n- **Conditional continuity:** `prostudio_references_list`, `prostudio_references_resolve`, and `inspect_prostudio_media` when cast, locations, props, or supplied footage need stable visual identity.\n- **Conditional production:** `prostudio_models_list`, `prostudio_generation_prepare`, `prostudio_video_generate`, `prostudio_job_status`, and `prostudio_generation_get` only when the user requests generated footage; `prostudio_editor_get` and `prostudio_editor_apply` only when assembling finished episodes.\n- This declaration does not activate tools. Use only the tools needed for the requested deliverable. 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 unavailable. A story outline or prepared generation is not a finished episode.\n\n## Shape the series\n\n- Treat a microdrama as **scripted, serialized fiction in short episodes**, usually designed for a phone. A 9:16 frame and roughly one to three minutes per episode are useful starting points, not mandatory specifications. Do not impose 50–100 episodes, a paywall, a particular genre, or a forced cliffhanger on a user who chose a shorter, free, horizontal, or experimental series.\n- Establish the premise, protagonist's desire and obstacle, relationship or secret that can evolve, audience, platform, language, tone, episode count and target duration. Infer harmless defaults where possible. If the user starts with only an idea, offer a compact series direction and a small pilot arc before proposing a whole season. Ask only for choices that materially change the story or delivery.\n- Match the requested stage of work: concept and series bible, episode map, scripts, visual plan, or produced episodes. A request for writing does not authorize media generation. If the user wants a branded microdrama, make the brand's role credible within the characters' choices and story rather than interrupting the episode with a sales pitch; respect supplied brand and product constraints.\n- Build a compact series bible with the logline, emotional engine, character motives and relationships, chronology, recurring locations and props, identity and wardrobe anchors, visual language, and the promised ending. Track what each character knows after every reveal. When the user approves a direction, load `production-planning`, read the current Brief, and save the chosen human creative material while preserving unrelated content. Keep IDs, model choices, jobs, and credit state out of the Brief.\n\n## Write for the episode boundary\n\n- Map every planned episode with its target runtime, opening situation or hook, immediate goal and obstacle, concrete turn, ending question or consequence, and the payoff carried into the next episode. Begin in a legible situation quickly; keep exposition in playable action and concise dialogue. Vary the type and size of reveals so the season escalates instead of repeating the same betrayal or withholding one answer indefinitely.\n- Give each episode a meaningful change, even when it ends on a cliffhanger. Pay off prior promises, preserve cause and effect, and let the final episode resolve the central dramatic question unless the user explicitly wants an open ending. Do not invent arbitrary danger merely to force an end beat.\n- For scripts, use timed beats and production-ready scene descriptions: who wants what, what visibly changes, spoken lines in the requested language, sound, transition, and the exact frame or action at the episode cut. Check that dialogue and action fit the target duration when performed; do not estimate runtime only from word count.\n\n## Direct and produce for mobile\n\n- Compose for the chosen delivery frame from the start. For 9:16, stage actors, gaze, hands, props, and reveals within the portrait frame; use expressive close and medium shots with clear spatial relations, foreground and background depth, motivated camera movement, and room for platform UI or optional captions. Do not merely crop a wide composition. Keep every image and video visually dimensional and at a high cinematic or commercial production standard, never flat or generic.\n- For realistic cinematic or branded footage, specify a plausible camera look and lens or focal length in millimeters when it changes the visual result, along with framing, camera movement, depth of field, lighting, and motion. Treat names such as ARRI ALEXA or IMAX as visual intent, not a claim about actual capture equipment; do not force incompatible camera jargon into animation or stylized work.\n- If the user requests generated footage, load `reference-management` for identity-bearing assets and `generation-planning` for the live model catalog. Plan supported clip durations and the episode's actual cut points; bind exact references for recurring people, wardrobe, products, props, and locations. Carry the series bible into every prompt without changing character identity or story order. Verify completed clips, dialogue, action, visual continuity, and the cliffhanger frame before assembling with `editor-workflows`.\n- Add exact titles, messages, and subtitles in post-production when possible rather than relying on video generation to spell small text. Keep dialogue intelligible in short mobile viewing sessions. Before paid generation, show the selected script, visual approach, clips and durations, reference strategy, model, and exact known credits; follow the host's required approval for prepared actions.\n- Deliver the requested artifact at its actual stage. For a produced episode, verify a playable assembled video and its runtime, not only a script or a set of pending clips. For a series, report which episodes are complete and which remain planned.\n"
"---\nname: microdrama-series\ndescription: Develop and, when requested, produce a scripted episodic microdrama for mobile viewing; use for a series premise, episode map, scripts, or finished episodes, not for an unrelated standalone short or ordinary ad.\n---\n\n# Microdrama series\n\n## Tool requirements\n\n- **Creative Brief, when saving an approved direction:** `prostudio_brief_get` and `prostudio_brief_replace`.\n- **Conditional continuity:** `prostudio_references_list`, `prostudio_references_resolve`, and `inspect_prostudio_media` when cast, locations, props, or supplied footage need stable visual identity.\n- **Conditional production:** `prostudio_models_list`, `prostudio_generation_prepare`, `prostudio_video_generate`, `prostudio_job_status`, and `prostudio_generation_get` only when the user requests generated footage; `prostudio_editor_get` and the dedicated Editor operation tools only when assembling finished episodes.\n- This declaration does not activate tools. Use only the tools needed for the requested deliverable. 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 unavailable. A story outline or prepared generation is not a finished episode.\n\n## Shape the series\n\n- Treat a microdrama as **scripted, serialized fiction in short episodes**, usually designed for a phone. A 9:16 frame and roughly one to three minutes per episode are useful starting points, not mandatory specifications. Do not impose 50–100 episodes, a paywall, a particular genre, or a forced cliffhanger on a user who chose a shorter, free, horizontal, or experimental series.\n- Establish the premise, protagonist's desire and obstacle, relationship or secret that can evolve, audience, platform, language, tone, episode count and target duration. Infer harmless defaults where possible. If the user starts with only an idea, offer a compact series direction and a small pilot arc before proposing a whole season. Ask only for choices that materially change the story or delivery.\n- Match the requested stage of work: concept and series bible, episode map, scripts, visual plan, or produced episodes. A request for writing does not authorize media generation. If the user wants a branded microdrama, make the brand's role credible within the characters' choices and story rather than interrupting the episode with a sales pitch; respect supplied brand and product constraints.\n- Build a compact series bible with the logline, emotional engine, character motives and relationships, chronology, recurring locations and props, identity and wardrobe anchors, visual language, and the promised ending. Track what each character knows after every reveal. When the user approves a direction, load `production-planning`, read the current Brief, and save the chosen human creative material while preserving unrelated content. Keep IDs, model choices, jobs, and credit state out of the Brief.\n\n## Write for the episode boundary\n\n- Map every planned episode with its target runtime, opening situation or hook, immediate goal and obstacle, concrete turn, ending question or consequence, and the payoff carried into the next episode. Begin in a legible situation quickly; keep exposition in playable action and concise dialogue. Vary the type and size of reveals so the season escalates instead of repeating the same betrayal or withholding one answer indefinitely.\n- Give each episode a meaningful change, even when it ends on a cliffhanger. Pay off prior promises, preserve cause and effect, and let the final episode resolve the central dramatic question unless the user explicitly wants an open ending. Do not invent arbitrary danger merely to force an end beat.\n- For scripts, use timed beats and production-ready scene descriptions: who wants what, what visibly changes, spoken lines in the requested language, sound, transition, and the exact frame or action at the episode cut. Check that dialogue and action fit the target duration when performed; do not estimate runtime only from word count.\n\n## Direct and produce for mobile\n\n- Compose for the chosen delivery frame from the start. For 9:16, stage actors, gaze, hands, props, and reveals within the portrait frame; use expressive close and medium shots with clear spatial relations, foreground and background depth, motivated camera movement, and room for platform UI or optional captions. Do not merely crop a wide composition. Keep every image and video visually dimensional and at a high cinematic or commercial production standard, never flat or generic.\n- For realistic cinematic or branded footage, specify a plausible camera look and lens or focal length in millimeters when it changes the visual result, along with framing, camera movement, depth of field, lighting, and motion. Treat names such as ARRI ALEXA or IMAX as visual intent, not a claim about actual capture equipment; do not force incompatible camera jargon into animation or stylized work.\n- If the user requests generated footage, load `reference-management` for identity-bearing assets and `generation-planning` for the live model catalog. Plan supported clip durations and the episode's actual cut points; bind exact references for recurring people, wardrobe, products, props, and locations. Carry the series bible into every prompt without changing character identity or story order. Verify completed clips, dialogue, action, visual continuity, and the cliffhanger frame before assembling with `editor-workflows`.\n- Add exact titles, messages, and subtitles in post-production when possible rather than relying on video generation to spell small text. Keep dialogue intelligible in short mobile viewing sessions. Before paid generation, show the selected script, visual approach, clips and durations, reference strategy, model, and exact known credits; follow the host's required approval for prepared actions.\n- Deliver the requested artifact at its actual stage. For a produced episode, verify a playable assembled video and its runtime, not only a script or a set of pending clips. For a series, report which episodes are complete and which remain planned.\n\n- Billing display is controlled by the authenticated account. When `billingDisplay.unit` is `EUR`, present the returned euro charge and balances; otherwise present credits. Preserve prepared execution arguments and `expectedCredits` exactly, without displaying those machine values as prices.\n"
Full snapshot data
{
"description": "Develop and, when requested, produce a scripted episodic microdrama for mobile viewing; use for a series premise, episode map, scripts, or finished episodes, not for an unrelated standalone short or ordinary ad.",
"included_files": [],
"name": "microdrama-series",
"skill_md_contents": "---\nname: microdrama-series\ndescription: Develop and, when requested, produce a scripted episodic microdrama for mobile viewing; use for a series premise, episode map, scripts, or finished episodes, not for an unrelated standalone short or ordinary ad.\n---\n\n# Microdrama series\n\n## Tool requirements\n\n- **Creative Brief, when saving an approved direction:** `prostudio_brief_get` and `prostudio_brief_replace`.\n- **Conditional continuity:** `prostudio_references_list`, `prostudio_references_resolve`, and `inspect_prostudio_media` when cast, locations, props, or supplied footage need stable visual identity.\n- **Conditional production:** `prostudio_models_list`, `prostudio_generation_prepare`, `prostudio_video_generate`, `prostudio_job_status`, and `prostudio_generation_get` only when the user requests generated footage; `prostudio_editor_get` and the dedicated Editor operation tools only when assembling finished episodes.\n- This declaration does not activate tools. Use only the tools needed for the requested deliverable. 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 unavailable. A story outline or prepared generation is not a finished episode.\n\n## Shape the series\n\n- Treat a microdrama as **scripted, serialized fiction in short episodes**, usually designed for a phone. A 9:16 frame and roughly one to three minutes per episode are useful starting points, not mandatory specifications. Do not impose 50–100 episodes, a paywall, a particular genre, or a forced cliffhanger on a user who chose a shorter, free, horizontal, or experimental series.\n- Establish the premise, protagonist's desire and obstacle, relationship or secret that can evolve, audience, platform, language, tone, episode count and target duration. Infer harmless defaults where possible. If the user starts with only an idea, offer a compact series direction and a small pilot arc before proposing a whole season. Ask only for choices that materially change the story or delivery.\n- Match the requested stage of work: concept and series bible, episode map, scripts, visual plan, or produced episodes. A request for writing does not authorize media generation. If the user wants a branded microdrama, make the brand's role credible within the characters' choices and story rather than interrupting the episode with a sales pitch; respect supplied brand and product constraints.\n- Build a compact series bible with the logline, emotional engine, character motives and relationships, chronology, recurring locations and props, identity and wardrobe anchors, visual language, and the promised ending. Track what each character knows after every reveal. When the user approves a direction, load `production-planning`, read the current Brief, and save the chosen human creative material while preserving unrelated content. Keep IDs, model choices, jobs, and credit state out of the Brief.\n\n## Write for the episode boundary\n\n- Map every planned episode with its target runtime, opening situation or hook, immediate goal and obstacle, concrete turn, ending question or consequence, and the payoff carried into the next episode. Begin in a legible situation quickly; keep exposition in playable action and concise dialogue. Vary the type and size of reveals so the season escalates instead of repeating the same betrayal or withholding one answer indefinitely.\n- Give each episode a meaningful change, even when it ends on a cliffhanger. Pay off prior promises, preserve cause and effect, and let the final episode resolve the central dramatic question unless the user explicitly wants an open ending. Do not invent arbitrary danger merely to force an end beat.\n- For scripts, use timed beats and production-ready scene descriptions: who wants what, what visibly changes, spoken lines in the requested language, sound, transition, and the exact frame or action at the episode cut. Check that dialogue and action fit the target duration when performed; do not estimate runtime only from word count.\n\n## Direct and produce for mobile\n\n- Compose for the chosen delivery frame from the start. For 9:16, stage actors, gaze, hands, props, and reveals within the portrait frame; use expressive close and medium shots with clear spatial relations, foreground and background depth, motivated camera movement, and room for platform UI or optional captions. Do not merely crop a wide composition. Keep every image and video visually dimensional and at a high cinematic or commercial production standard, never flat or generic.\n- For realistic cinematic or branded footage, specify a plausible camera look and lens or focal length in millimeters when it changes the visual result, along with framing, camera movement, depth of field, lighting, and motion. Treat names such as ARRI ALEXA or IMAX as visual intent, not a claim about actual capture equipment; do not force incompatible camera jargon into animation or stylized work.\n- If the user requests generated footage, load `reference-management` for identity-bearing assets and `generation-planning` for the live model catalog. Plan supported clip durations and the episode's actual cut points; bind exact references for recurring people, wardrobe, products, props, and locations. Carry the series bible into every prompt without changing character identity or story order. Verify completed clips, dialogue, action, visual continuity, and the cliffhanger frame before assembling with `editor-workflows`.\n- Add exact titles, messages, and subtitles in post-production when possible rather than relying on video generation to spell small text. Keep dialogue intelligible in short mobile viewing sessions. Before paid generation, show the selected script, visual approach, clips and durations, reference strategy, model, and exact known credits; follow the host's required approval for prepared actions.\n- Deliver the requested artifact at its actual stage. For a produced episode, verify a playable assembled video and its runtime, not only a script or a set of pending clips. For a series, report which episodes are complete and which remain planned.\n\n- Billing display is controlled by the authenticated account. When `billingDisplay.unit` is `EUR`, present the returned euro charge and balances; otherwise present credits. Preserve prepared execution arguments and `expectedCredits` exactly, without displaying those machine values as prices.\n"
}SHA-256 of public snapshot: 8c2ca75b4a2de9327d3bcb1894ff3658d315284f0790d07de7469659970d5b68