Image provider routing

Skill event4u-app/agent-config/dist/agent-src/skills/image-provider-routing

Universal AI Agent OS — audited skills, governance rules, replayable state. One contract, every host agent.

Install

npx -y skills add event4u-app/agent-config --skill image-provider-routing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Select the right image-generation provider from job shape — text-in-image to Ideogram, photoreal to Flux, vector/logo to Recraft, general to Gemini/GPT.

SKILL.md

4.5 KB, as published. Nobody here has run it

image-provider-routing

Route an image generation job to the right provider based on job shape. Adapters are scaffold-tier (dry-run only) — selection produces a plan; execution waits on promotion per provider-lifecycle-discipline.

When to use

Choosing which image model fits a brief (logo, banner, photo, icon, general art).
Before calling any src/scripts/ai-image/adapters/*.sh adapter.
When the user asks "which image model should I use?" or "route this image job."

Provider decision table

Job shape	Provider	Why
Text-in-image (logo, banner, typographic art)	Ideogram	Best glyph rendering; raster models garble text
Photoreal (product shot, portrait, scene)	Flux	Photorealism specialist; routed via fal/Replicate
Vector / SVG logo or icon	Recraft	Produces genuine `<path>` SVG; raster cannot
General art / edit / multimodal	Gemini-image or GPT Image 2	Broad capability; natural-language prompts
Budget-conscious 4K upscale	Flux via Replicate	Cost-competitive at high resolution

Decision order: text-in-image → Ideogram; must-be-vector → Recraft; photoreal → Flux; everything else → Gemini-image (default) or GPT Image 2 (when OpenAI key available and editing an existing image).

Procedure

Extract job shape from the brief: does it need embedded text? vector output? photorealistic rendering? or general illustration?
Apply table — match the dominant shape to the provider row above.
Check lifecycle tier — all adapters are experimental (scaffold). Surface this before any live invocation.
Confirm with the user when shape is ambiguous (e.g., logo that could be vector OR raster typographic art → ask once).
Emit the routing decision in the Output format below.

Output format

Chosen provider — name + one-line rationale citing the job-shape match.
Lifecycle-tier caveat — "adapter is experimental (scaffold tier); dry-run only until a smoke trace is captured per provider-lifecycle-discipline."
Fallback — if the primary adapter is unavailable or the smoke trace is missing, name the next best provider and what changes.

Gotcha

Routing a text-in-image job to a photoreal model is the #1 failure — send a logo/banner with embedded text to Flux and the text renders as garbled glyphs; it must go to Ideogram. Likewise a vector logo sent to Ideogram/Flux returns a raster PNG, not the editable <path> SVG a brand mark needs (→ Recraft).
All four adapters (ideogram.sh, flux.sh, recraft.sh, gemini-image.sh) are scaffold-tier — dry-run plumbing only, no live generation yet. Routing produces a selection + plan; actual API calls require promotion to stable first (maintainer-captured smoke trace under agents/reference/ai-image/smoke-traces/). Surfacing a provider without its experimental tier caveat misleads the caller into expecting a rendered asset that won't come.

Good example: "Text logo for a bakery → Ideogram (text-in-image); lifecycle: experimental — dry-run plan only."

Bad example: "Use Recraft for the product photo" — Recraft is the vector path; photoreal jobs go to Flux.

Do NOT

Do NOT invoke an adapter without surfacing its lifecycle tier (all are experimental).
Do NOT route a text-in-image job to Flux — Flux has no glyph renderer; text garbles.
Do NOT route a vector/SVG job to Ideogram or Flux — neither outputs genuine <path> SVG.
Do NOT skip image-likeness-and-rights when the brief names a real person or brand mark.
Do NOT promote an adapter from experimental to stable — that is maintainer-only via smoke trace.