REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
GPT-Image-2 PPT Generator Skill for Creating Image-Based PowerPoint Presentations in Codex and Other Skill-Compatible Agents
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/ningzimu-codex-ppt-skill)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 codex-ppt-skill | rea | graphify | archify | security-audit-skill | |
|---|---|---|---|---|---|
| 作者 | ningzimu | morluto | Graphify-Labs | tt-a1i | cloudflare |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 7,911 | 461,751 | 148,352 | 96,757 | 73,156 |
| 最近代码更新 | 2026年10月13日 | 2026年11月16日 | 2026年11月16日 | 2026年11月15日 | 2026年9月15日 |
| 许可证 | MIT | MIT | Apache-2.0 | Apache-2.0 | MIT |
ningzimu 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodex
依据开发者 README 和 repo 中的文件夹
GitHub account ningzimu (person), 9 years old
★ 7,911 stars · code last changed 2026年10月13日
15 scripts that can run on a computer: scripts/prepare_slide_prompts.py, scripts/assemble_ppt.py, scripts/codex_ppt_runtime.py, scripts/image_gen.py and 11 more
Scripts that go online: scripts/image_providers/atlascloud.py, scripts/codex_ppt_runtime.py
Scripts that touch settings folders (~/.claude or settings.json): scripts/image_providers/openai_compatible.py, scripts/codex_ppt_runtime.py, scripts/remove_chroma_key.py, scripts/assemble_ppt.py and 1 more
Checked automatically from the repo files at commit 941dcaf (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Files are byte-for-byte the same as on GitHub at commit 941dcaf · View on GitHub ↗
15 scripts
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
All 41 files · 269 KB
.clawhubignore1 KBSKILL.md10 KBdocs/backend-selection.md4 KBdocs/cli-api-fallback.md5 KBdocs/image-model-configuration.md3 KBdocs/outline-style-and-sample.md9 KBdocs/project-assembly-and-reporting.md8 KBdocs/slide-generation-and-subagents.md14 KBdocs/style-library.md6 KBdocs/user-supplied-assets.md3 KBdocs/workflow-gates-and-progress.md3 KBprompts/slide-worker.md3 KBreferences/党政红风格.md8 KBreferences/创意杂志风.md3 KBreferences/复古扁平插画风.md3 KBreferences/手绘技术解释风.md5 KBreferences/手绘白板风.md3 KBreferences/教学课件风.md10 KBreferences/数据仪表盘风.md3 KBreferences/清爽专业风.md4 KBreferences/温暖手工风.md3 KBreferences/电子墨水杂志风.md5 KBreferences/科研答辩风.md9 KBreferences/麦肯锡风格.md15 KBrequirements.txt1 KBscripts/assemble_ppt.py14 KBscripts/codex_ppt_runtime.py8 KBscripts/image_gen.py34 KBscripts/image_providers/__init__.py1 KBscripts/image_providers/atlascloud.py8 KBscripts/image_providers/base.py1 KBscripts/image_providers/factory.py1 KBscripts/image_providers/openai_compatible.py7 KBscripts/prepare_slide_prompts.py20 KBscripts/record_slide_blocker.py1 KBscripts/record_slide_dispatch.py2 KBscripts/record_slide_result.py7 KBscripts/remove_chroma_key.py14 KBscripts/slide_job_status.py2 KBscripts/slide_run_state.py6 KBLICENSE1 KB+Create skillUpload a skillpick codex-ppt.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /codex-ppt,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/ningzimu/codex-ppt-skill.git /tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf/skills/codex-ppt' ~/.claude/skills/codex-pptChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 codex-ppt 文件夹放到 ~/.agents/skills/codex-ppt
~ 是你的主文件夹($HOME)
不用终端:下载 ZIP,解压后把 codex-ppt 文件夹移到 ~/.agents/skills
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/ningzimu/codex-ppt-skill.git /tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf/skills/codex-ppt' ~/.agents/skills/codex-pptChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/ningzimu/codex-ppt-skill.git /tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf/skills/codex-ppt' ~/.agents/skills/codex-ppt复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 codex-ppt
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/ningzimu/codex-ppt-skill.git /tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-ningzimu-codex-ppt-skill-941dcaf/skills/codex-ppt' ~/.cursor/skills/codex-ppt适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月16日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: codex-ppt
description: Generate visually unified image-based PPT/PPTX decks from articles, reports, papers, notes, or outlines.
metadata:
openclaw:
requires:
bins:
- python3
primaryEnv: OPENAI_API_KEY
envVars:
- name: OPENAI_API_KEY
required: false
description: API key for CLI fallback.
- name: OPENAI_BASE_URL
required: false
description: API base URL.
- name: CODEX_PPT_IMAGE_MODEL
required: false
description: Image model, defaults to gpt-image-2.5-flare.
- name: CODEX_PPT_HOME
required: false
description: Runtime home override.
homepage: https://github.com/ningzimu/codex-ppt-skill
---
# Codex PPT
## Overview
This skill creates image-based PowerPoint decks from source material. Each slide is a complete 16:9 generated image. Final images are assembled into `.pptx` with `scripts/assemble_ppt.py`.
Use this when the user wants a visually unified presentation and accepts full-slide image pages. Do not use it when every textbox, chart, or shape must remain separately editable.
Prefer the built-in image generation/editing tool. Use `scripts/image_gen.py` only when the built-in backend is unavailable, lacks a required capability, or the user explicitly asks for API/CLI mode.
## Hard Constraints
- Read the relevant `Reference Map` files before each phase. This file is the orchestration contract; detailed rules live in `docs/` and worker prompts in `prompts/`.
- Respect approval gates. Do not create final `deck_spec.json`, `speech.md`, prompt jobs, slide images, or `.pptx` before the approvals in `docs/workflow-gates-and-progress.md`.
- After the user approves the sample slide and authorizes full-deck generation, every remaining slide image job must be dispatched to a slide subagent whenever subagents are available.
- The main agent owns orchestration, prompt jobs, state recording, QA, speaker notes, and assembly. Do not silently replace available slide subagents with sequential production.
- Every final `origin_image/slide_XX.png` must be generated by the selected image backend: built-in image generation/editing tool or `scripts/image_gen.py`.
- Local drawing, Pillow, SVG, HTML/CSS/canvas screenshots, python-pptx/PptxGenJS layouts, and manual overlays are failure modes, not fallbacks.
- The selected image backend must stay fixed after backend confirmation. Do not let subagents switch backend for convenience.
- After sample approval, record how the approved sample was generated and pass that exact method to every slide subagent.
- Slide dispatch and result state must be recorded with the bundled scripts. Chat messages alone do not make a slide dispatched or complete.
- If a required subagent, image backend, or required-image path is unavailable, stop and report a blocker with the slide id and evidence. Do not create a lower-quality replacement.
## Visible Progress
For non-trivial decks, keep a user-visible checklist with one active step. Canonical completion evidence is in `docs/workflow-gates-and-progress.md`.
Default visible steps:
1. Prepare source, outline, style, and backend decisions.
2. Generate and approve one sample slide.
3. Prepare slide jobs and slide state.
4. Dispatch slide subagents.
5. Record generated slide results.
6. QA, repair, notes, and PPT assembly.
Do not mark a step complete from chat alone; use real files or script-recorded state.
## Default Workflow
1. Understand the source content.
- Identify topic, audience, goal, page count, style/brand constraints, and sections to include or exclude.
- If no page count is specified, choose a practical count. Typical decks are 8-12 slides.
2. Plan the deck outline.
- Before writing or updating `outline.md`, read `docs/workflow-gates-and-progress.md` and `docs/outline-style-and-sample.md`.
- Draft slide roles and required source images. Ask for confirmation, then stop before style, backend, sample, or downstream artifacts until approved.
3. Confirm a unified visual style.
- Before offering style options or using files from `references/`, read `docs/outline-style-and-sample.md`.
- Offer 2-3 concrete style directions, recommend one, wait for confirmation, then keep one visual identity while varying layouts by page role.
4. Confirm the image backend.
- Before generating any slide image, read `docs/backend-selection.md`.
- Check whether a built-in image tool is callable, state what you checked, name the backend, explain fallback status, and wait for confirmation.
- If CLI/API fallback is selected, read `docs/cli-api-fallback.md`. Read `docs/image-model-configuration.md` only after config errors or explicit API-setting requests.
5. Generate one sample slide for approval.
- Before generating or approving the sample slide, read `docs/outline-style-and-sample.md`.
- Generate exactly one representative sample after outline, style, and backend are confirmed. Do not generate the full deck until approved.
- After approval, record `sample_generation_method` in `deck_spec.json` so jobs and subagents inherit the same path.
6. Create the project directory.
- Before initializing folders or assembling files, read `docs/project-assembly-and-reporting.md`.
- If no destination is specified, use the current working directory or the source file directory.
7. Prepare user-supplied assets.
- Before using paper figures, charts, screenshots, logos, or other required assets, read `docs/user-supplied-assets.md`.
- Treat required assets as strict inputs and confirm slide-to-asset mapping before generation.
8. Generate all slide images.
- Before full-deck image generation, read `docs/slide-generation-and-subagents.md`.
- Create per-slide jobs with `scripts/prepare_slide_prompts.py` or saved `prompts/slide_XX.json` files.
- Every final image must come from the selected backend and be recorded with bundled state scripts.
9. Dispatch slide subagents.
- Before dispatching or replacing slide workers, read `docs/slide-generation-and-subagents.md` and `prompts/slide-worker.md`.
- Use one subagent per remaining slide job whenever possible. If required subagents cannot be spawned, stop and report a blocker unless the user changes the workflow.
10. Quality check and repair.
- Before QA or assembly, read `docs/project-assembly-and-reporting.md`.
- Inspect every slide before assembly: text, outline match, truncation, style, unwanted page numbers, overlaps, and required assets.
- Regenerate severe failures with a tighter prompt. Use backend editing for localized issues when available.
- For CLI/API fallback edit commands, read `docs/cli-api-fallback.md`. Replace the final slide only after validating the edited output.
11. Write speaker notes and assemble the PPT.
- Before writing `speech.md` or running assembly, read `docs/project-assembly-and-reporting.md`.
- Make sure `outline.md` reflects the final confirmed deck outline. Use `speech.md` headings that map to `Slide N`.
- Before assembly, ensure `slide_jobs.json` shows generated slides as `recorded` and approved samples as `accepted`. If any slide is `pending`, `dispatched`, or `blocked`, stop.
12. Report the result.
- Use the final report checklist in `docs/project-assembly-and-reporting.md`.
- Include paths, slide count, backend used, recorded-result status, and any limitations or blockers.
13. Save reusable styles.
- If asked to save the current deck style or a supplied image/PDF/PPT/PPTX style, read `docs/style-library.md`.
- If the final deck used a custom or adapted style, proactively offer to save it in the final report, per `docs/project-assembly-and-reporting.md`. User custom styles are stored in `${CODEX_PPT_HOME:-~/.codex-ppt-skill}/references/`, outside the skill install.
## Subagent Dispatch
Slide subagents are mandatory after sample approval whenever the runtime can spawn them. The main agent prepares jobs and rec提问、分享技巧或报告无法使用。按“有帮助”数量排序。