Codex Ppt
Generate presentation slides with images by choosing the right backend—built-in image_gen/image_generate versus local scripts/image_gen.py.
Overview
Codex PPT is an agent skill for the Build phase that generates presentation slides and picks between built-in image tools and local image_gen.py fallback.
Install
npx skills add https://github.com/ningzimu/codex-ppt-skill --skill codex-pptWhat is this skill?
- Two image backends: built-in agent image tool (e.g. Codex image_gen, OpenClaw image_generate) and local CLI/API via scri
- Actively probes whether the built-in image tool is callable—do not assume from subscription alone
- gpt-image-2 requests stay on the built-in path in Codex when available; do not default to CLI for model naming
- CLI/API fallback only when built-in tool is missing, failed, or user demands API/proxy
- Backend selection must be read before confirming backend or generating the first sample slide
- Two image backends: built-in image tool and local scripts/image_gen.py
Adoption & trust: 988 installs on skills.sh; 1.2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need AI-generated slides but agents often pick the wrong image backend and waste runs on unavailable CLI paths.
Who is it for?
Indie builders using Codex or OpenClaw who want PPT-style decks with generated art and a clear built-in-vs-CLI decision tree.
Skip if: Builders who only need markdown outlines with zero image generation or who already standardized on one host-only API script with no agent image tool.
When should I use this skill?
Before confirming the image backend or generating the first sample slide for a presentation workflow.
What do I get? / Deliverables
You get slides generated through the correct image backend with explicit rules for Codex, OpenClaw, and API fallback before the first sample slide.
- Sample slides
- Generated slide images
- PPT or export artifacts under output paths
Recommended Skills
Journey fit
Slide decks and pitch artifacts are documentation-style deliverables produced while building narrative and specs. Docs is the shelf for agent-produced presentations, export paths, and visual slide assets tied to the product story.
How it compares
Slide generator skill with dual image backends—not a generic markdown exporter or static theme pack.
Common Questions / FAQ
Who is codex-ppt for?
Solo builders and agents automating visual presentations in Codex-, OpenClaw-, or API-backed environments.
When should I use codex-ppt?
During Build → docs when you are producing a deck or sample slides and must lock image backend choice before the first render.
Is codex-ppt safe to install?
Check the Security Audits panel on this page; image backends may use network and API keys—review scripts/image_gen.py and .env handling locally.
SKILL.md
READMESKILL.md - Codex Ppt
.DS_Store .venv/ __pycache__/ *.pyc *.pyo *.pyd .pytest_cache/ .mypy_cache/ .env output/ temp/ test_output/ examples/ *.png *.jpg *.jpeg *.gif *.bmp *.pptx *.pdf # Backend Selection Read this before confirming the image backend or generating the first sample slide. This skill supports two image backends: 1. Built-in image tool, preferred when available. Example tool names: Codex `image_gen`; OpenClaw `image_generate`. 2. Local API/CLI fallback, using `scripts/image_gen.py`. ## Decision Rules - Before recommending CLI/API fallback, actively check whether the built-in image generation tool is callable in the current environment. Do not infer availability only from the agent name or subscription context. - Prefer the built-in image tool when available. In Codex, this usually means the built-in `image_gen` tool. In OpenClaw, this may be `image_generate`. Resolution, quality, aspect ratio, slide-edit requests, or the user saying "use `gpt-image-2`" do not require CLI/API fallback. - In Codex, treat the built-in image tool as the preferred `gpt-image-2` path when it is available. If the user has a GPT subscription / Codex environment and asks for `gpt-image-2`, do not switch to `scripts/image_gen.py` only to satisfy the model name. - Use CLI/API fallback only when the built-in tool is unavailable, the built-in tool failed for a required capability, the user explicitly asks for API/CLI or a third-party OpenAI-compatible proxy, or the requested capability is unavailable in the built-in tool. - Do not recommend CLI/API fallback merely because it provides direct `--out` file paths, easier local file management, local config reuse, batch generation convenience, or simpler automation. - Before generating the first image, tell the user which tool availability you checked, which backend you plan to use, why fallback is or is not needed, and ask for confirmation. Do not treat being in a specific agent environment as proof that the built-in image tool is available. - CLI/API fallback loads `~/.codex-ppt-skill/.env` automatically. Run the CLI normally; do not manually parse `.env` or ask for configuration before an error. - Ask for `OPENAI_API_KEY` configuration only after you have intentionally selected CLI/API fallback and that fallback reports missing config, after authentication/base URL/model errors, or when the user explicitly wants to change API settings. Do not mention missing `OPENAI_API_KEY` while the Codex built-in image tool is available. Configure provided values with `scripts/codex_ppt_runtime.py config --api-key`. If CLI/API fallback is selected, read `cli-api-fallback.md` before generating images. For API key, base URL, model, and `.env` configuration, read `image-model-configuration.md` only after the fallback CLI reports missing or invalid configuration, or when the user explicitly wants to change those settings. ## Confirmation Text Built-in backend: ```text 我检查到当前环境可调用内置图片生成工具（Codex 通常是 image_gen，OpenClaw 通常是 image_generate），因此准备优先用内置工具生成样张，不切到本地 API/CLI fallback。可以开始生成 1 页样张吗？ ``` CLI/API fallback: ```text 我检查后没有可用的内置图片生成工具，或内置工具缺少本页必需能力，因此准备使用本地 API/CLI fallback 生成样张，读取 ~/.codex-ppt-skill/.env 中的 OPENAI_BASE_URL / CODEX_PPT_IMAGE_MODEL 配置。可以开始生成 1 页样张吗？ ``` Wait for confirmation before generating the sample slide. If the user questions the backend, resolve that before continuing. # CLI/API Fallback Use this reference only after CLI/API fallback has been selected and confirmed with the user. The main `SKILL.md` owns the backend decision rules; this document owns fallback commands, runtime setup, image-input limits, editing, transparency, and troubleshooting. Let `{skill_root}` mean the directory containing `SKILL.md`. ## Runtime Setup CLI/API fallback commands use the shared runtime environment. Before running `scripts/assemble_ppt.py` or fallback image commands, make sure the shared runtime exists. If `~/.codex-ppt-skill/.venv/bin/python` is missing, or if importing script dependencies fails, create or