Image Generation
- 378 installs
- 19 repo stars
- Updated July 27, 2026
- postplusai/postplus-skills
Image Generation is an agent skill that classifies image requests and hands them to image-batch-runner without submitting jobs itself.
About
Image Generation is a PostPlus routing-contract skill that acts as the controller for any agent session where the deliverable is still or batched images. Solo builders and small teams use it when a user asks for text-to-image, edits, persona shots, product renders, banners, thumbnails, or storyboard panels, but the runtime must not fire jobs until inputs are understood and the correct runner payload exists. The skill walks a four-step gate: detect input type, assign a task class, apply model and reference rules, then emit a structured handoff for image-batch-runner. That separation keeps expensive API calls and batch orchestration in one executor while this skill stays deterministic and auditable. It fits Claude Code, Cursor, and Codex flows that chain PostPlus family skills for creative pipelines without mixing video, audio, or edit-plan controllers into the same step.
- Classifies image work into text_to_image, image_edit, reference-driven, product, persona, banner, thumbnail, and storybo
- Enforces a hard boundary: identifies inputs and policies but does not submit generation jobs
- Hands off normalized requests to image-batch-runner after model and reference rules are chosen
- Covers batch variants, product URLs, research handoffs, and uploaded reference images
- Pairs with reference-decode and reference-contract-builder when boundaries need decoding first
Image Generation by the numbers
- 378 all-time installs (skills.sh)
- +42 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #451 of 1,335 Generative Media skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/postplusai/postplus-skills --skill image-generationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 378 |
|---|---|
| repo stars | ★ 19 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | postplusai/postplus-skills ↗ |
What it does
Route text-to-image, edits, and batch variant requests through task classification and model policy before PostPlus executes jobs.
Who is it for?
Best when you're wiring PostPlus image pipelines and need a single gate before batch execution.
Skip if: Sessions where jobs are already normalized, the final asset is video or audio, or you only need hook decoding without generation routing.
When should I use this skill?
User wants text-to-image, image edit, reference-image generation, product or persona images, banners, thumbnails, storyboards, or batch variants and the next step is classification—not execution.
What you get
You get a normalized controller handoff with task class and reference policy so image-batch-runner can execute the batch.
- Classified image task with model and reference policy
- Structured handoff payload for image-batch-runner
By the numbers
- Four-step controller flow: input type, task class, model/reference rules, runner handoff
- Explicit task-class table covering text_to_image, edits, and reference-driven generation paths
Files
Image Generation
Use When
- The desired final asset is an image or image batch.
- The request may include text prompts, uploaded images, previous outputs,
product URLs, research handoffs, product images, persona images, banners, thumbnails, storyboard panels, or batch variants.
- The next decision is task class, model/reference policy, and runner handoff.
Do Not Use When
- The final asset is video, audio, subtitles, transcripts, or an edit plan.
- The image request is already normalized and ready to execute. Use
image-batch-runner.
- The user needs hook decoding or reference boundaries first. Use
reference-decode or reference-contract-builder.
Core Boundary
This is the image generation controller. It does not submit jobs.
It must:
1. identify the input type, 2. classify the image task, 3. select model and reference rules, 4. create the handoff for image-batch-runner.
Task Classes
| Task class | Typical input | Handoff |
|---|---|---|
text_to_image | prompt only | write normalized image brief for image-batch-runner |
image_edit | uploaded image plus change request | bind edit image and preserve/alter rules |
reference_image | benchmark frame or style board | use reference-contract-builder before runner |
product_image | product photo, URL, or product facts | bind product identity and forbid invented claims |
banner_thumbnail | offer, hook, platform | require aspect ratio and text/UI policy |
storyboard_image | panel plan or board spec | hand storyboard panels to image-batch-runner |
batch_variant | many variants or personas | preserve shared rules and vary only declared fields |
Model And Reference Rules
- Text-only drafts may use a text-to-image endpoint.
- Edits require a bound source image and an edit-capable endpoint.
- Persona, product, and brand identity are
bindingreferences unless the user
explicitly marks them inspiration-only.
- Benchmark clips, mood boards, and competitor references are inspiration-only
unless the contract says otherwise.
- Excluded references must not enter the runner request.
Routing Table
| If not image-generation | Send to |
|---|---|
| Needs media understanding first | media-router |
| Needs reference meaning decoded | reference-decode |
| Needs binding/inspiration/excluded contract | reference-contract-builder |
| Needs storyboard panels | storyboard-grid-writer |
| Needs execution with normalized request | image-batch-runner |
| Final output is video | video-generation |
| Final output is audio | audio-generation |
Output Shape
Return:
taskClassinputTypemodelRulereferencePolicyrequiredRunnerInputshandoffSkillmustNotDo
Stop Conditions
- Stop when required user intent, source evidence, or owned input artifacts are
missing and guessing would change the result.
- Do not let
image-batch-runnermake creative classification decisions. - If an owned CLI or script command fails, report the exact error and stop. Do
not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.
Public Command Boundary
- Choose the smallest matching command or workflow from the user input and run
it directly.
- If an owned CLI or script command fails, report the exact error and stop. Do
not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.
- This public skill is instruction-driven. Produce the controller handoff
artifact directly from the available evidence.
- Do not call private provider/runtime paths or unpublished local tools.
- If the CLI returns a quote-confirmation challenge, run
postplus quote confirm --json --challenge-file <challenge.json>and retry with the returned token.
Related skills
Remotion Best PracticesGet Remotion-specific coding guidance that prevents common video rendering mistakes when creating animated React videos.451k4.2k
Ai Video GenerationGenerate videos using 40+ AI models including Veo, Seedance, and others via inference.sh442k665Ai Image GenerationGenerate images using 50+ AI models including FLUX, Gemini, and Replicate via inference.sh441k665Ai Avatar VideoGenerate videos featuring AI avatars for product demos, tutorials, marketing, or explainers441k665Remotion RenderRender videos programmatically using React components and Remotion framework441k665
Remotion RenderGenerate high-quality MP4 videos from React code using Remotion inside an AI coding agent.363k665How it compares
Use as the pre-execution controller, not as a replacement for image-batch-runner or reference-contract-builder.
FAQ
Who is image-generation for?
Developers using PostPlus skills in Claude Code, Cursor, or Codex who generate marketing, product, or creative images through an agent and want classification before any API spend.
When should I use image-generation?
Use it in Build when wiring agent-tooling for creative pipelines; at Launch when producing banners and thumbnails; and in Grow when batching content variants—always before image-batch-runner runs.
Is image-generation safe to install?
It is documentation-style routing logic with no job submission in this skill; review the Security Audits panel on this Prism page before enabling it in a repo with secrets or production keys.