image-generatelisted

Generates an image from a text prompt via a pluggable provider backend, writing the image plus a `<image>.meta.json` sidecar to an operator-chosen path. Backends are swappable via `--provider`: cloudflare (Cloudflare Workers AI FLUX.1-schnell, real free tier, DEFAULT), pollinations (auth-free, but public-feed/undocumented-licence — the tool forces private=true and shows a disclaimer), gemini (gemini-2.5-flash-image, requires billing). Wraps the bundled, stdlib-only `scripts/image_generate.py`. Invoke when the user asks to "generate an image", "create a hero image or icon from a prompt", "render this prompt to a PNG", "turn a graphic-prompt-generator document into an image", or equivalent German-language requests. Don't use for image editing, in-painting, or multi-turn refinement; for batch pipelines; or to author the prompt itself (use graphic-prompt-generator). Supports resume is not applicable: a generation is a single terminal call.
nolte/claude-shared · ★ 0 · Data & Documents · score 74

Install: claude install-skill nolte/claude-shared

# Image Generate Turns a text prompt into an image file on disk — no chat UI, scriptable into any pipeline — by driving the bundled, stdlib-only `scripts/image_generate.py`. Backends are **swappable via `--provider`** so the capability is not locked to one vendor's pricing or availability. Implements `spec/tools/image-generation/<canonical_language>.md`, resolved in the *target repository* (the plugin ships no `spec/` tree). When the target repo carries no such spec — a consumer install without the hub corpus — apply the provider-neutral requirements inlined in this body (provider swappability, consent gate, deterministic file output) as the fallback baseline. Per-provider details live in the hub's `spec/design/flux-image-generation/` and `spec/design/gemini-image-generation/`. Where this skill and a resolvable spec disagree, the spec wins. ## Why this is a skill, not an agent - **Operator-invoked slash command.** Reached as `/nolte-media:image-generate` with a prompt, a provider, and a target path; the operator drives it directly rather than a parent dispatching a fire-and-forget worker. - **Mid-flow confirmation is part of the contract.** Some providers surface a one-time data/licence notice the operator must acknowledge, and an existing target file must not be overwritten without confirmation. Those are interactive gates an agent's structured-report shape can't carry. - **The result flows back into the conversation.** Written image and sidecar paths land in the operato