REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
PPT image-first skill for Codex/Claude Code/Opencode CLI
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/nyxtides-ppt-image-first)在同一工作中把 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 列表相同
| 本项 ppt-image-first | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | NyxTides | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 1,239 | 465,460 | 233,910 | 149,364 | 144,149 |
| 最近代码更新 | 2026年5月8日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月17日 |
| 许可证 | Apache-2.0 | MIT | – | Apache-2.0 | MIT |
NyxTides 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
开发者未说明 · SKILL.md 形式的 Skill 可用于支持 Agent Skills 的应用,如 Claude Code、Codex 和 Cursor
GitHub account NyxTides (person), 1 years old
★ 1,239 stars · code last changed 2026年5月8日
4 scripts that can run on a computer: assets/candidate_picker_shell/build_candidate_picker_html.py, assets/preview_shell/build_preview_html.py, assets/review_shell/build_review_html.py, scripts/render_review_markup.py
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 87a300a (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (401). Use "Let the AI install it" instead
复制这句话,粘贴到 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,输入 /ppt-image-first,或直接提出相关任务,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/nyxtides/ppt-image-first.git /tmp/popnx-skill-nyxtides-ppt-image-first-87a300a && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-nyxtides-ppt-image-first-87a300a/.' ~/.claude/skills/ppt-image-firstChatGPT 桌面应用内置 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
把 ppt-image-first 文件夹放到 ~/.agents/skills/ppt-image-first
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/nyxtides/ppt-image-first.git /tmp/popnx-skill-nyxtides-ppt-image-first-87a300a && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-nyxtides-ppt-image-first-87a300a/.' ~/.agents/skills/ppt-image-firstChecked 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/nyxtides/ppt-image-first.git /tmp/popnx-skill-nyxtides-ppt-image-first-87a300a && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-nyxtides-ppt-image-first-87a300a/.' ~/.agents/skills/ppt-image-first复制这句话,粘贴到 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 聊天中输入 / 并选择 ppt-image-first
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/nyxtides/ppt-image-first.git /tmp/popnx-skill-nyxtides-ppt-image-first-87a300a && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-nyxtides-ppt-image-first-87a300a/.' ~/.cursor/skills/ppt-image-first适用于其他能读取 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月17日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
6,319 个字符 · 在 GitHub 打开完整文件
---
name: ppt-image-first
description: Build presentation plans for PPT / slides / decks through a conversation-first workflow, then propose multiple visual directions with preview images before writing deck specs. Use when the user asks to create a PPT, presentation, deck, 答辩稿, 路演 deck, 产品介绍 PPT, 汇报 PPT, or when the user has only a topic or rough materials and needs help clarifying structure, style, and page planning before generation.
---
# PPT Image First
Use this skill to turn a vague PPT request into a generation-ready, image-first deck plan.
## I/O Contract
- Input: a PPT topic, rough goal, existing notes/materials, or complete report-like narrative.
- Optional anchors: audience, page count or duration, school/company/lab/course/brand identity, use occasion, source files, and style constraints.
- Output: a confirmed content basis, visual style previews, deck specs, generated page visuals, review surface, and final PPT after approval.
- Confirmation gates: `需求确认`, `风格确认`, `生成前确认`, and final review approval.
- Default ratio: generate preview images and final page visuals in `16:9` unless the user explicitly requests another ratio.
## Workflow Phases
Follow these phases in order and do not skip the confirmation gates:
1. Intake: clarify lightly, identify anchors, output a short baseline judgment, then get `需求确认`.
2. Content basis: create or extract `content_report.md` unless the user already supplied complete report-like content; show a synthesized judgment, not the raw file by default.
3. Style preview: align style boundaries, propose directions, generate `首页 / 目录页 / 正文页` previews for each direction, support refinement, then get `风格确认`.
4. Planning lock: run `风格反演确认`, then write `design_spec.md`, `slide_blueprint.md`, and `spec_lock.md` in that order; summarize and get `生成前确认`.
5. Generation review: generate page visuals, optionally run candidate selection, open the review HTML, retouch as needed, and export the final PPT only after approval.
Read `references/workflow.md` for stage-by-stage execution details.
## Progressive Loading
- Intake and baseline: read `references/conversation_framework.md` only when you need the conversation-first intake pattern.
- Style proposals: read `references/style-system.md` when producing proposal cards or interpreting V1-V8 internally.
- Preview/review UI: read `references/preview-flow.md` before producing style previews, candidate-picker pages, or review pages.
- Content basis: read `templates/content_report_reference.md` before writing `content_report.md`.
- Planning files: read `templates/design_spec_reference.md`, `templates/slide_blueprint_reference.md`, and `templates/spec_lock_reference.md` immediately before writing those files.
## Working Principles
- Treat the user like a client and yourself like the proposing design agent.
- Do not force the user to configure design parameters manually; translate their natural-language intent into design decisions.
- Ask for real-world identity anchors when relevant, but treat them as grounding context rather than style questions.
- Keep intake lightweight; do not turn content basis or style alignment into a long questionnaire.
- Use style vectors internally, but present front-stage options as concise proposal cards plus image previews.
- Use the content basis for previews and planning rather than generic placeholder structures.
- Mark inferred claims carefully; do not present unsupported precise data, experiment results, citations, or institutional conclusions as user-provided facts.
- Show summaries, proposal cards, previews, and review surfaces by default; show raw planning files only when useful or requested.
## Hard Rules
- Preview-first: final style confirmation should be based on generated `首页 / 目录页 / 正文页` previews, not text-only choices.
- Shells are mandatory: use `assets/preview_shell/index.html`, `assets/candidate_picker_shell/index.html`, and `assets/review_shell/index.html` as the base UIs for their stages.
- Open the local preview, candidate-picker, review, and final PPT files immediately when those stages produce them; if opening fails, state the blocker and provide the path.
- Do not write `slide_blueprint.md` before style direction and `风格反演确认` are complete.
- Keep generation image-first when the confirmed direction depends on generated page visuals; do not silently fall back to shape-by-shape PPT construction or hand-drawn code substitutes.
- User-requested edits such as adding, replacing, correcting, or supplementing visible text are still image-generation/editing tasks by default. Do not use PIL, Pillow, canvas, SVG, HTML screenshots, PPT native text boxes, or deterministic overlays to patch final page visuals unless the user explicitly asks for a code/PPT-overlay workaround.
- Treat generated page visuals as complete by default; post-generation overlays default to zero unless they are traceable to approved blueprint fields.
- Keep slide identifiers, candidate codes, filenames, and generation batch labels outside the image-generation prompt body. They may appear in planning files, filenames, mapping tables, review UI, and chat instructions, but the prompt sent to the image model should contain only audience-facing content and visual direction.
- Review payloads should carry lightweight coordinate markup, not base64 preview images. When a user pastes review JSON with markup, first render the marked review images locally with `scripts/render_review_markup.py`, then use the marked images plus separate text comments as the retouch/regeneration reference.
- Before full generation, ask whether the user wants one final image per slide or multiple final candidates per slide.
- Do not export the final PPT immediately after first-pass generation; export only after the reviewed pages are approved.
## Output Hierarchy
Use these layers consistently:
- `content_report.md` = upstream content basis when the user did not provide complete report-like material.
- `design_spec.md` = global deck rationale and confirmed visual system.
- `slide_blueprint.md` = page-by-page intent and content plan.
- `spec_lock.md` = execution constraints and final generation guardrails.
`content_report.md` supports the 3 core planning files; it does not replace them. `spec_lock.md` is always the last core planning file.
提问、分享技巧或报告无法使用。按“有帮助”数量排序。