fal-recipes
Use-case-driven multi-step pipelines on fal.ai. Trigger when the user asks for a specific kind of content production rather than a single endpoint call: "make a commercial", "ad creative", "product photography", "cinematic shot", "film look", "character design", "consistent character", "anchor system", "storyboard", "multi-shot", "narrative video", "talking head", "lip sync", "make this person talk", "virtual try-on", "garment transfer", "restore image", "deblur", "denoise", "fix face", "old photo restore", "add audio to video", "video sound effects", "product shot", "photoreal", "realistic photo", "candid photo", "editorial portrait", "documentary photo", "looks like a real photograph", "iPhone-style photo", "film photo", "archival photo". Each recipe describes inputs, the genmedia call sequence, and quality checks.
What this skill does
# fal.ai Recipes > **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. A recipe is a use-case-driven pipeline. It tells you the inputs to collect, the genmedia calls to chain, and the quality bar to verify before returning. Recipes use `genmedia` for execution and `fal-models-catalog` for endpoint defaults. They differ from `fal-workflow`: - **fal-workflow** = how to *build* a pipeline (JSON authoring or CLI orchestration patterns), generic - **fal-recipes** = how to *produce a specific kind of content*, opinionated by use case ## Available recipes | Reference | Use for | |-----------|---------| | [cinematography.md](references/cinematography.md) | Cinematic stills and video, shot language, lighting, lens, color grade | | [character-design.md](references/character-design.md) | Original characters with consistent identity across shots | | [commercial.md](references/commercial.md) | Product photography, ads, e-commerce batches, hero shots | | [storytelling.md](references/storytelling.md) | Multi-shot narratives, short films, ads, brand films, social stories | | [character-lipsync.md](references/character-lipsync.md) | Talking head / lip-sync video (TTS → animated portrait) | | [image-restoration.md](references/image-restoration.md) | Smart-dispatch restoration, deblur, denoise, dehaze, fix faces, document restore | | [virtual-tryon.md](references/virtual-tryon.md) | Apply a garment onto a person photo (with optional cleanup chain) | | [video-with-audio.md](references/video-with-audio.md) | Add narration / SFX / music to a silent video | | [product-shot.md](references/product-shot.md) | Hero product photography from a packshot reference | | [realism.md](references/realism.md) | Photoreal stills (candid, editorial, documentary, archival, food, nature, architectural) with an anti-AI-look checklist | ## How to choose a recipe 1. Match the user's intent to a use case in the table above. 2. If multiple recipes apply (e.g., "commercial featuring a consistent character"), load both and run the dominant one, usually the more specific one (`character-design` first, then commercial framing). 3. If no recipe matches but the task is multi-step, fall back to `fal-workflow` Mode B (CLI orchestration) and design the pipeline from scratch. 4. If the task is a single endpoint call, skip recipes, go directly to the right `fal-models-catalog` reference. ## Universal recipe structure Every reference follows the same skeleton so the agent knows where to look: 1. **Inputs to collect**: only what changes the pipeline. 2. **Genmedia workflow**: endpoint discovery, schema inspection, upload, run, status, download. 3. **Prompt build order**: domain-specific structure (e.g., SCLCAM for cinema, anchor + variable for character). 4. **Patterns / examples**: concrete prompt templates and finished examples. 5. **Quality bar**: explicit checks before returning. ## Cross-references - For endpoint defaults: [fal-models-catalog](../fal-models-catalog/SKILL.md) - For prompt-craft per model family: [fal-prompting](../fal-prompting/SKILL.md) - For pipeline patterns (fan-out, sequential, frame-bridging, etc.): [fal-workflow](../fal-workflow/SKILL.md) Mode B - For utility endpoints (resize, composite, audio merge, subtitle, etc.): [fal-workflow/references/utility-endpoints.md](../fal-workflow/references/utility-endpoints.md) Information lives in one place. If a recipe needs an endpoint listed in the catalog, it links to the catalog instead of duplicating the list.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".