MelvynxMelvynx/ai-maxxing-skills/skills/codex-images/SKILL.md

codex-images

Skill32 starsChanged 24 days agoMITView on GitHub

Batch-generate raster images through Codex CLI and its built-in image_gen. Use when the user needs several images at once, prompt arrays, catalog variants, or images built from reference pictures (YouTube thumbnails, product shots).

1 other project uses a version of this.

Adopted by

Most recently taken up by

Melvynx/video-agent-skillstheir own version, first seen Oct 15, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
Melvynx/video-agent-skills★ 126same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- skills/setup-my-hermes-dashboard/template/AGENTS.mdAGENTS.md
- audit-safetySkill
- betterSkill
- cleanupSkill
- create-projectSkill
- doneSkill
- dreamSkill
- projectsSkill
- setup-brainSkill
- cloudflareSkill
- code-debugSkill
- connect-googleSkill
- connect-instagram-developer-platformSkill
- connect-toolSkill
- connect-vpsSkill
- connect-youtube-developer-platformSkill
- convexSkill
- create-internal-appSkill
- create-landingSkill
- create-softwareSkill
- dev-browserSkill
- grill-meSkill
- initializeSkill
- install-skillsSkill
- lumailSkill
- safe-shipSkill
- setup-cloudflareSkill
- setup-convexSkill
- setup-dev-browserSkill
- setup-githubSkill
- setup-lumailSkill
- dashboardSkill
- setup-my-hermes-dashboardSkill
- setup-nodeSkill
- setup-stripeSkill
- setup-vpsSkill
- show-meSkill
- skill-managerSkill
- stripe-checkoutSkill
- use-styleSkill
- verifySkill
- wait-whatSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Default output: .codex/scripts/output/<batch-name>-<timestamp>/ with NNN-clean-name.png, logs/job-NNN.log, and manifest.json (copied[]: …
line 16
Very specific:
Keep upload/import in the target repo.
line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Needs the Codex CLI installed and signed in: check codex --version and codex login status. If either fails, read references/setup-codex.md and guide the user through it before going on.

Install the bundled CLI at the target repo root (scripts/image_gen is in this skill's folder). If .codex/scripts/image_gen already exists, inspect it before replacing.

mkdir -p .codex/scripts
cp <this-skill-folder>/scripts/image_gen .codex/scripts/image_gen
chmod +x .codex/scripts/image_gen

Default output: .codex/scripts/output/<batch-name>-<timestamp>/ with NNN-clean-name.png, logs/job-NNN.log, and manifest.json (copied[]: path, promptIndex, prompt, name). Prefer { "name", "prompt" } objects for stable names.

.codex/scripts/image_gen --name hats --prompts '["prompt one", "prompt two"]'
.codex/scripts/image_gen --out .codex/scripts/output/tshirts --prompts '[{"name":"men-white-crew-tee","prompt":"..."}]'
.codex/scripts/image_gen --name catalog --prompts prompts.json --concurrency 3
.codex/scripts/image_gen --name cap-variants --prompt "..." --count 3
.codex/scripts/image_gen --prompts prompts.json --dry-run

--prompts accepts a JSON string array, a {name,prompt} array, a file of either, or newline prompts.

Reference images (thumbnails, a face, a product): keep the source images read-only and copy the ones you need locally first. One named prompt object per final image; never pack multiple concepts into one job or one --count. Every prompt must list absolute local paths and tell the nested Codex job to pass them to image_gen as referenced_image_paths. Dry-run, then run; manifest.json must have one successful copy per prompt.

Catalog prompts: inspect the app taxonomy/filters first. No person, mannequin, face, text, logo, or checkerboard unless asked. Closed shirts: full front, closed neckline, no open placket.

Keep upload/import in the target repo. After generation, verify prompt count == copied images, usable dimensions, and unique hashes. Stop after returning the output dir and manifest.json path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free