with one click
image-generation
Generate images and iteratively edit saved image artifacts.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Generate images and iteratively edit saved image artifacts.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Search and install agent skills from ClawHub, the public skill registry.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Sustained objectives via long_task / complete_goal — idempotent goal wording, project-style modular work, early web/doc research, Runtime Context metadata.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Based on SOC occupation classification
| name | image-generation |
| description | Generate images and iteratively edit saved image artifacts. |
Use the generate_image tool when the user asks you to create, render, draw, design, generate, or edit an image.
If the generate_image tool is not available in the current tool list, tell the user that image generation is not enabled for this CloakBot instance.
generate_image with a concrete prompt.reference_images.message tool with the artifact paths in the media parameter to deliver them to the user.Write prompts with enough detail for image models:
The tool stores generated images as persistent artifacts under CloakBot's media directory and returns structured metadata:
id: generated image id, such as img_ab12cd34ef56.path: local file path for internal follow-up edits.mime: image MIME type.prompt, model, and source_images: provenance for follow-up edits.In normal user-facing replies, do not expose local filesystem paths. Keep the reply natural, for example "Done, I generated it." You may include the short image id when it helps the user refer to a specific image, but keep raw path internal unless the user explicitly asks for debug details or a local artifact reference. Never paste base64.
For follow-up edits, pass the prior artifact path to reference_images. If the user provides a new uploaded image, use that path as the reference instead.
Do not include internal replay markers such as [Message Time: ...], [image: /local/path], generate_image(...), or message(...) in user-facing replies.
Generate a new image:
generate_image(
prompt="A minimal app icon for CloakBot: friendly robot head, rounded square, soft blue and white palette, clean vector style, no text",
aspect_ratio="1:1",
image_size="1K"
)
Edit the latest generated artifact:
generate_image(
prompt="Use the reference image. Keep the same robot and composition, but change the palette to warm orange and add a subtle sunrise background.",
reference_images=["/home/user/.cloakbot/media/generated/2026-05-08/img_ab12cd34ef56.png"],
aspect_ratio="1:1",
image_size="1K"
)