agentleFS
YangsonHungYangsonHung/awesome-agent-skills/skills/en/routerbase-media-generation/SKILL.md

routerbase-media-generation

Skill18 starsChanged 8 days agoMITView on GitHub

Use when building image, audio, or video generation workflows through RouterBase with provider selection, retries, asset handling, and safety checks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use routerbase for image, audio, and video generation workflows through one API surface.

    line 10
  2. Distinctive:

    Use this skill when the user asks for:

    line 14
  3. Distinctive:

    Do not use this skill for:

    line 23
  4. Distinctive:

    Use placeholders for API keys and user-specific asset paths.

    line 32
  5. Distinctive:

    Add a safety checklist covering prompt constraints, private data, content rights, and generated asset retention.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

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

  1. Identify the target media type, output format, resolution or duration, latency tolerance, and storage destination.
  2. Choose the endpoint pattern and provider assumptions before writing code.
  3. Use placeholders for API keys and user-specific asset paths.
  4. Include retry, polling, timeout, and failure-state handling for async generation.
  5. Add a safety checklist covering prompt constraints, private data, content rights, and generated asset retention.

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.