Media Heavy Workflows
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.
Install
npx skills add swyxio/skills --skill media-heavy-workflowsgit clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/media-heavy-workflows ~/.claude/skills/media-heavy-workflowsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the 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
Details
- Skill name
media-heavy-workflows- Repository
- swyxio/skills
- Path
media-heavy-workflows/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Media Heavy Workflows skill do?
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.
How do I install the Media Heavy Workflows skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill media-heavy-workflows. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Media Heavy Workflows popular?
It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.
Related skills
Accelevents API
201swyxio/skills
Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.
Accelevents Speaker Sync
201swyxio/skills
Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.
Agents SDK
201swyxio/skills
Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.
Next Steps
201swyxio/skills
Turn an ongoing task or conversation into evidence-informed opportunities and an actionable decision workspace. Use when the user asks what next, invokes $next-steps, or wants to explore, compare, combine, and prioritize possible directions. Adapt from a short conversational recommendation to a richer interactive exploration when the decision warrants it.
Marketplace Search Recsys Planning
228pproenca/dot-skills
Search and recommendation system planning for a two-sided trust marketplace built on OpenSearch — user-intent framing, product-surface architecture, index design, query understanding, retrieval strategy, ranking, search-plus-recs blending, measurement, and a dashboard-and-alerting layer for ongoing decision making. Triggers on tasks involving marketplace search, homefeeds, ranking, relevance tuning, OpenSearch query DSL, analyzers, synonyms, golden sets, NDCG, A/B testing, or diagnosing an existing retrieval system. Use this skill BEFORE marketplace-personalisation when planning new work; hand
Outbound Sequencer
150guia-matthieu/clawfu-skills
Design multi-touch outbound sequences with optimal timing, channel mix, and messaging progression for SDR campaigns
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.