RouterBase Media Generation
Overview
Use routerbase for image, audio, and video generation workflows through one API surface. This skill helps choose a media endpoint, shape prompts and parameters, handle sync or async responses, manage generated assets, and add safety checks.
When to Use
Use this skill when the user asks for:
- Generating images, audio, speech, or video through RouterBase
- Choosing the right media endpoint and provider for a workflow
- Handling retries, polling, failed jobs, output URLs, and asset retention
- Designing safe prompt, moderation, and storage rules for generated media
- Writing client examples for media generation requests
Do not use
Do not use this skill for:
- Creating or storing private user media without consent and retention guidance
- Assuming generated asset URLs are permanent unless the platform documents it
- Skipping moderation, copyright, or brand-safety review for externally published media
Instructions
- Identify the target media type, output format, resolution or duration, latency tolerance, and storage destination.
- Choose the endpoint pattern and provider assumptions before writing code.
- Use placeholders for API keys and user-specific asset paths.
- Include retry, polling, timeout, and failure-state handling for async generation.
- Add a safety checklist covering prompt constraints, private data, content rights, and generated asset retention.
1---2name: routerbase-media-generation3description: Use when building image, audio, or video generation workflows through RouterBase with provider selection, retries, asset handling, and safety checks.4---5
6# RouterBase Media Generation
7
8## Overview
9
10Use [routerbase](https://routerbase.com/) for image, audio, and video generation workflows through one API surface. This skill helps choose a media endpoint, shape prompts and parameters, handle sync or async responses, manage generated assets, and add safety checks.
11
12## When to Use
13
14Use this skill when the user asks for:
15- Generating images, audio, speech, or video through RouterBase
16- Choosing the right media endpoint and provider for a workflow
17- Handling retries, polling, failed jobs, output URLs, and asset retention
18- Designing safe prompt, moderation, and storage rules for generated media
19- Writing client examples for media generation requests
20
21## Do not use
22
23Do not use this skill for:
24- Creating or storing private user media without consent and retention guidance
25- Assuming generated asset URLs are permanent unless the platform documents it
26- Skipping moderation, copyright, or brand-safety review for externally published media
27
28## Instructions
29
301. Identify the target media type, output format, resolution or duration, latency tolerance, and storage destination.
312. Choose the endpoint pattern and provider assumptions before writing code.
323. Use placeholders for API keys and user-specific asset paths.
334. Include retry, polling, timeout, and failure-state handling for async generation.
345. Add a safety checklist covering prompt constraints, private data, content rights, and generated asset retention.
yangsonhung