agentleFS
swyxioswyxio/skills/media-heavy-workflows/SKILL.md

media-heavy-workflows

Skill176 starsChanged 7 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When users compare multiple generated candidates, keep batches and selection with their owning artifact.

    line 17
  2. Distinctive:

    Verify only the changed behavior and risks: capability/reference handling, intended insertion or publish semantics, privacy, and secret …

    line 27
  3. Very specific:

    Read references/media-studio-lessons.md only when the user actually requests cast boards, public/celebrity references, multi-provider …

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.
  4. Separate generation from publishing only when the product requests a draft or review workflow. Direct image-edit actions may update their target immediately when undo and existing state semantics are preserved.
  5. Make external uploads and material cost visible. Keep provider credentials server-side, and require authorization before paid or irreversible actions.
  6. Show useful progress or failure state for slow operations. Preserve original dimensions and source ownership when the requested operation requires them.
  7. Verify only the changed behavior and risks: capability/reference handling, intended insertion or publish semantics, privacy, and secret protection.

Optional specialist guidance

Read references/media-studio-lessons.md only when the user actually requests cast boards, public/celebrity references, multi-provider studios, structured prompt authoring, specialized media-workspace layouts, or broader studio QA. Those patterns are recommendations, not prerequisites for unrelated work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.