genmedia-workflow
Design and execute multi-step media workflows with genmedia. Use this for pipelines that combine planning, generation, editing, image or video utilities, audio, subtitles, batching, and final delivery manifests.
What this skill does
# Genmedia workflow production
> **Runtime:** All endpoint calls run via the [genmedia CLI](https://github.com/fal-ai-community/genmedia-cli). See the `genmedia` skill for command syntax; run `genmedia init` once if not yet installed.
Use this skill when a single model call is not enough. A workflow is a planned
sequence of genmedia calls with clear inputs, outputs, dependencies, and
quality checks.
Load references as needed:
- `references/pipeline-patterns.md`
- `references/node-rules.md`
- `references/utility-endpoints.md`
- `references/recipes.md`
- `model-routing` for creative model defaults
Use `model-routing` for default creative model choices. Still inspect schemas,
check pricing when cost matters, and use exact endpoint fields.
## Inputs to collect
Ask only for missing information that changes the pipeline:
- Final deliverable: image set, video, clips, audio, subtitles, dataset, social
batch, product campaign, storyboard, style exploration.
- Source assets: product images, character references, first frames, video,
audio, logo, transcript, brand guide.
- Runtime limits: quality target, cost sensitivity, number of variants,
duration, aspect ratios, deadline.
- Continuity requirements: product identity, character face, scene layout,
voice, color grade.
- Model preference: ask the user only when quality, speed, cost, or audio
tradeoffs are not clear from the brief.
## Core workflow
1. Write a short pipeline graph before running anything.
```text
input assets -> planner -> generation nodes -> utility nodes -> QA -> final outputs
```
2. Resolve endpoints for each role. Check known endpoint IDs first.
```bash
genmedia models --endpoint_id openai/gpt-image-2 --json
genmedia models --endpoint_id fal-ai/nano-banana-pro/edit --json
genmedia models --endpoint_id bytedance/seedance-2.0/image-to-video --json
genmedia models --endpoint_id xai/grok-imagine-video/image-to-video --json
genmedia models --endpoint_id veed/fabric-1.0 --json
```
Use text search only as fallback discovery for roles not covered by
`model-routing` or the utility reference:
```bash
genmedia models "image generation product photography" --json
genmedia models "image editing reference preservation" --json
genmedia models "image to video" --json
genmedia models "subtitle video utility" --json
genmedia docs "fal.ai workflow utility endpoints" --json
```
3. Inspect every endpoint before use.
```bash
genmedia schema <endpoint_id> --json
genmedia pricing <endpoint_id> --json
```
4. Upload local files once and reuse returned URLs.
```bash
genmedia upload ./input.png --json
genmedia upload ./voiceover.wav --json
```
5. Run each node with JSON output. Use async for slow generation.
```bash
genmedia run <endpoint_id> --<field> "<value>" --json
genmedia run <endpoint_id> --<field> "<value>" --async --json
genmedia status <endpoint_id> <request_id> --download "./outputs/workflow/{request_id}_{index}.{ext}" --json
```
6. For downstream nodes, pass the media URL from the previous `result` when it
is available. If you only have a local file path, upload it first.
7. Download final assets with templates that cannot collide.
```bash
--download "./outputs/workflow/{request_id}_{index}.{ext}"
```
8. Return a compact manifest.
```json
{
"goal": "short deliverable description",
"nodes": [
{
"id": "shot_01",
"role": "image_to_video",
"endpoint_id": "...",
"request_id": "...",
"input_urls": ["..."],
"output_urls": ["..."],
"downloaded_files": ["..."],
"notes": "continuity or defect notes"
}
],
"final_files": ["..."]
}
```
## Pipeline rules
- Keep one node responsible for one clear transformation.
- Fan out independent generation, crop, upscale, subtitle, or variation nodes.
- Keep sequential chains only when node B needs node A output.
- For consistency, prefer reference/edit or image-to-video over independent
text-only generations.
- For default creative model choices, follow `model-routing` unless the user
names a model.
- Use utility endpoints for deterministic work: crop, resize, grid, composite,
audio merge, subtitle, speed change, compression.
- Record endpoint, schema-relevant parameters, request ID, and output path for
every node.
- If a 422 error occurs, read `validation_errors`, inspect schema again, then
fix the exact field.
## Quality gate
Before returning, verify:
- The pipeline graph matches the requested deliverable.
- No generation model was chosen from memory alone.
- All local source files were uploaded before use.
- Final files were saved through `--download`.
- Utility endpoints used exact schema fields.
- Continuity anchors were repeated where identity or product fidelity matters.
- Each node output is either accepted, retried, or marked with a defect.
If the workflow becomes too complex, stop expanding and ask the user to choose
between faster iteration, higher fidelity, or broader variation.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.