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
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/nyxtides-ppt-image-first)Servidores MCP que conectan la IA a servicios para el mismo trabajo
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
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este ppt-image-first | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Autor | NyxTides | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| Estrellas de GitHub | 1239 | 463.670 | 233.682 | 148.887 | 143.987 |
| Último cambio de código | 8 may 2026 | 17 nov 2026 | 20 abr 2026 | 17 nov 2026 | 16 nov 2026 |
| Licencia | Apache-2.0 | MIT | – | Apache-2.0 | MIT |
1 skills (conjuntos de instrucciones) de NyxTides que la IA lee y sigue · no es un MCP server
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
El autor no lo indica · los skills con SKILL.md funcionan en apps compatibles con Agent Skills, como Claude Code, Codex y Cursor
GitHub account NyxTides (person), 1 years old
★ 1239 stars · code last changed 8 may 2026
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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Uploading to claude.ai would fail: the description is over 200 characters (401). Use "Let the AI install it" instead
Copia esta frase y pégala en un chat de 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
Vuelve a abrir Claude Code y escribe /ppt-image-first, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
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
Coloca la carpeta ppt-image-first en ~/.agents/skills/ppt-image-first
~ es tu carpeta de inicio ($HOME)
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del 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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Copia esta frase y pégala en un chat de 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
En el chat Agent de Cursor escribe / y elige ppt-image-first
Checked against official docs 12 nov 2026 · Source: cursor.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · 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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
El texto siguiente viene del repo del autor, no de PopNx MCP
6319 caracteres · Abrir el archivo completo en 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.
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.