Menu

Individual skill

media-heavy-workflows

0upvotes

Design or revise a multi-candidate AI media-generation workspace with reference attachment, model/provider capability routing, generation history, or explicit draft-to-publish flows. Use when those workflow concerns are central to the requested product. Do not use for individual canvas tools, ordinary image editing, one-off provider integrations, inference-runtime work, or simple image/video generation without a media workspace.

media-heavy-workflows/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
197
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Media Heavy Workflows

Apply only the patterns required by the requested product; a media operation is
not automatically a media studio.

## Behavioral core

1. Inspect the existing media entrypoint, ownership, provider route, and final
   insertion path. Preserve working behavior and the requested interaction.
2. Distinguish saved references from references actually sent to a model. Honor
   the selected endpoint's supported tasks, input schema, and reference limits.
3. When users compare multiple generated candidates, keep batches and selection
   with their owning artifact; snapshot the prompt, model, and references needed
   to explain each result.
Back to top