Use when an agent needs registry-backed image model discovery or single-route image generation from this repo's CLI, including choosing canonical models, resolving provider routes, and using text, JSON, or file-save output modes.
Use this skill to inspect available image models and providers or generate images through the local
image-gen-cli.
pnpm dev -- ... during development.image-gen-cli ....generate needs the provider credential for the selected route:
OPENAI_API_KEY, GOOGLE_API_KEY, TOGETHER_API_KEY, or REPLICATE_API_TOKEN.models list to discover canonical ids and aliases.routes list --model <model> before generate when provider routing is unclear.Canonical families currently shipped by the CLI:
gpt-imagegemini-imageimagenfluxklingopenai, google.together, replicate.routes list --model <model> shows more than one provider, pass --provider explicitly to generate.These currently require --provider together or --provider replicate:
flux-1-schnellflux-1-kontext-proflux-2-proflux-2-devflux-2-flexpnpm dev -- providers list
pnpm dev -- models list
pnpm dev -- models list --family flux
pnpm dev -- models list --provider google
pnpm dev -- routes list --model imagen-4-fast
pnpm dev -- routes list --model flux-2-pro --provider replicate
pnpm dev -- generate --model imagen-4-fast --prompt "A studio product shot"
pnpm dev -- generate --model flux-2-pro --provider together --prompt "A studio product shot"
--json when another tool, agent step, or test needs deterministic structured output, including provider, canonical model, provider model, raw response, and output references.--output-dir <dir> when generated assets must be persisted to deterministic local file paths for later steps.--json and --output-dir can be combined when both machine-readable metadata and saved files are needed.generate always requires --model and --prompt.routes list over guessing when a provider route may be ambiguous.