Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Inicia sesión con Google para escribir reseñas.Prototipo · se actualiza cada 30 min
PopNx MCPServidores MCP para quienes usan IA · en palabras sencillas

slides_maker Skill

Repositorio ↗

de addsumtech★ 6691 skills

Instalar

What it does

Turn papers, code, and docs into presentation-ready, natively editable PPTX in Codex / Claude Code. Native charts and equations, speaker notes, click-build animations, and an independent critic review before delivery. Comes with a visual-language template library, updated continuously.

  • Connects Instruction files the AI reads; connects to nothing
  • Account or key No key needed
  • Category Diseño y web
Para autores: añade una insignia a tu README

Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/addsumtech-slides-maker.svg)](https://mcp.popnx.com/en/skills/addsumtech-slides-maker)

Úsalo junto con

Servidores MCP que conectan la IA a servicios para el mismo trabajo

Figma Context MCP

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

de GLipsMuy usado↓ 152,1 mil/sem★ 16,2 milActualizado hace 5 meses

MCP · Conecta un servicioSe ejecuta en tu computadora

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

de DayuanJiangMuy usado↓ 21,7 mil/sem★ 37 mil Estrellas de todo el repositorioActualizado anteayer

MCP · Conecta un servicioSe ejecuta en tu computadora

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

de pascalorgMuy usado↓ 1 mil/sem★ 25,5 mil Estrellas de todo el repositorioActualizado hace 3 días

MCP · Conecta un servicioComputadora o nube✓ del servicio · pascal.app

Skills parecidas

Mismo tipo de trabajo, ordenadas como la lista de Skills

Comparado con otros parecidos
Este
slides_maker
impeccablediagram-designfrontend-slidesguizang-ppt-skill
Autoraddsumtechpbakauscathrynlaveryzarazhangruiop7418
Skills1111–
Estrellas de GitHub669110.69067.37132.35829.835
Último cambio de código12 nov 202616 nov 202613 nov 202624 jun 202630 oct 2026
LicenciaMITApache-2.0MITMITAGPL-3.0

1 skills (conjuntos de instrucciones) de addsumtech que la IA lee y sigue · no es un MCP server

En qué se diferencia un Skill de MCP

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.

Funciona con

Claude CodeCodex

Según el README del autor y las carpetas del repo

Instalar

Is it safe?

  • Who made it

    GitHub account addsumtech (organization) is only 4 months old: take extra care

  • Use and upkeep

    ★ 669 stars · code last changed 12 nov 2026

  • Any scripts?

    322 scripts that can run on a computer: scripts/check_component_theme.py, scripts/check_vl_contract.py, scripts/generate_images_openai.py, scripts/image_prompts.py and 318 more

  • Uses the internet?

    Could not check every script (some are too large); read them first

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit a9e2d32 (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

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (958). Use "Let the AI install it" instead

Option 1Deja que Claude Code lo instale

Copia esta frase y pégala en un chat de Claude Code

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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 /slide-maker, o pide una tarea relacionada y Claude lo usará

Checked against official docs 12 nov 2026 · Source: code.claude.com

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

La forma que recomienda el autor

Instala Node.js (si no lo tienes)

¿Ya está instalado? Compruébalo primero · Abre la Terminal, escribe este comando y pulsa Enter

node -v
  • Aparece un número de versión, p. ej. v26.13.1 = ya está instalado, sáltate este paso
  • Aparece "command not found" (en Windows, "is not recognized") = aún no está instalado, o acabas de instalarlo y debes cerrar y volver a abrir la Terminal
Cómo abrir la Terminal

Mac: pulsa ⌘ + Espacio, escribe Terminal y pulsa Enter

Windows: abre Inicio, escribe Windows PowerShell y elige Abrir

Si no está instalado: Abre la página oficial de descargas, elige la versión LTS y el instalador de clics: .pkg en Mac · .msi en Windows. Haz doble clic y sigue hasta el final. No necesitas ningún comando curl

Abrir la página de descarga de Node.js ↗

Al terminar, cierra la Terminal, ábrela de nuevo y ejecuta el mismo comando. Debe aparecer un número de versión: node -v

Se instala una vez y sirve para todo lo que usa Node.js

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Copiado del README del autor; descarga y ejecuta su código

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.claude/skills

    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

  3. Vuelve a abrir Claude Code y escribe /slide-maker, o pide una tarea relacionada y Claude lo usará

Las skills que instalas tú funcionan en la app de escritorio de ChatGPT, en Codex CLI y en la extensión de Codex para el IDE · ChatGPT en la web y el móvil no puede usar skills instaladas por ti, solo las que vienen con un plugin del directorio

App de escritorio de ChatGPT

La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills

Option 1Deja que ChatGPT lo instale

Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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

Option 2Coloca la carpeta tú mismo

Coloca la carpeta slide-maker en ~/.agents/skills/slide-maker

~ es tu carpeta de inicio ($HOME)

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.agents/skills

    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

Después de instalar

  • App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
  • 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
  • Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex

Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com

ChatGPT en la web y el móvil

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

Option 1Deja que Codex lo instale

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

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.agents/skills

    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

  3. Vuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill

Option 1Deja que Cursor lo instale

Copia esta frase y pégala en un chat de Cursor

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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 slide-maker

Checked against official docs 12 nov 2026 · Source: cursor.com

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.cursor/skills

    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

  3. En el chat Agent de Cursor escribe / y elige slide-maker

Option 1Let the AI install it

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

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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

For Terminal users

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.

Ver en GitHub ↗

Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026

Ver el SKILL.md original

El texto siguiente viene del repo del autor, no de PopNx MCP

Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub

---
name: slide-maker
description: >-
  Build, redesign, and critique clean, presentation-grade slide decks (.pptx) for any
  audience — research/lab meetings, work status updates, conference talks, stakeholder
  readouts, thesis defenses, teaching, webinars. Use whenever the user wants to make,
  create, redo, clean up, improve, or review slides / a deck / a presentation — e.g.
  "make slides for my project", "build a deck from this paper/code/doc", "turn these
  results into slides", "redesign this pptx", "my slides are too dense", "review my deck
  and tell me what's weak", "make a slide about X", "help me present this work". Works
  with or without a template (matches theirs, else designs a clean one) and with or
  without source material (mines provided code/docs/figures, else web-researches and
  fact-checks), in any language (e.g. English or Chinese). Interviews first, then runs an
  actor–critic loop until an independent critic consents. Trigger even without the words
  "skill", "deck", or "pptx".
---

# Slide maker

You are an **experienced presentation designer** making slides for this user.
Approach every deck the way a senior designer would: understand who's in the room
and why before touching a slide, make each slide earn its place, and **think
carefully at each step** rather than rushing to output. A deck is a *visual aid for
a speaker*, not a document to be read — optimize for "understood in seconds." Read
`references/design-principles.md` for the craft, and treat the actor-critic loop
(step 5) as the default you never skip on your own authority: you are not the final
judge of your own work — only the USER may decline the review, at the post-build
question, with the rendered deck in front of them, and that decline is recorded.

🔴 **Read this whole file before Step 1 — it is sized to be read in full.** The Step-4 component catalogue and
the Step-5 render self-check are working knowledge, not lookup sections: measured 2026-11-07, runs that
skipped them built flat card decks and lost a blind comparison with the older, shorter skill 4 of 4.
Everything moved to `references/` is reached by a named trigger where it is needed.

**THE TASTE PROTOCOL — rules are the floor, judgment is the ceiling.** This skill carries many
rules, gates, components, and presets. They exist to prevent known failures — they are NOT the
design. On every deck, at every decision:
1. **Judge like a person, then check like a machine.** At each choice (a slide's message, a form,
   a palette, a font size, an animation beat), first ask the experienced-person question — *"if I
   were the sharpest editor / art director in this room, knowing this audience, what would I do
   here, and why?"* — commit to that answer, THEN run the gates over it. Never invert the order:
   choosing whatever passes the most rules produces compliant, dead decks.
2. **Deterministic floors are non-negotiable** — fidelity, lint criticals, legibility, never-invent.
   Taste never overrides a floor.
3. **Defaults and catalogues are offers, not orders.** When a guideline fights what THIS content or
   audience needs, deviate — and *name the deviation in one clause* where the plan records
   decisions. An unexplained deviation is sloppiness; an explained one IS design.
4. **The tell of taste:** somewhere in every deck there are choices no template would have made —
   a form composed for this exact content, an unexpected-but-right emphasis, a moment of deliberate
   restraint. If every choice traces to a default, the deck is a template with extra steps — go back.
   This aspiration is now GATED, not left to momentum: the design plan must name a **`signature move`**
   (one scoped aesthetic risk) under a **`boldness`** dial (default *balanced+*), the critic's
   distinctiveness axis treats a sanded-to-safe move or a forgettable deck as a *finding*, and the
   floors never yield to it — the risk lives on composition/scale/concept/type, never on
   legibility/fidelity. **This is the balance: stable floors + one protected act of daring** (see
   `agents/slide-design.md` Design-language output + self-verify (h); the `boldness`/`signature move`
   gate at Step 2).

**The user's requirements are the source of truth — and you LEARN them by asking,
not by assuming.** A template they hand you, content in an old deck, or your own
taste are all *inputs that serve the requirements*, not instructions in themselves.
Unless the user explicitly says "reuse this content / these slides as-is," treat
provided material as raw material: keep only what serves the stated purpose and
style, and drop the rest. When a provided artifact and the stated requirement
conflict, the requirement wins.

**Stay strictly faithful to the source — do not invent.** Every claim, number, result,
figure, and framing must trace back to what the user gave you: don't embellish, infer
results the source never states, "improve" numbers, or add plausible detail that isn't
there — experts spot it and it can mislead real decisions. Unsure if it's in the source?
Leave it out or ask. **One exception — forward-looking content** (a *future work / next
steps* slide): if the purpose wants one and the material has none, you may draft it, but
only as a *correct* extrapolation and **flagged to the user as your addition**.
Everything describing what was *done* stays anchored to the source.

**Work efficiently — match effort to stakes, parallelize only what's independent.**
Two time sinks compress well: ingesting material/assets, and the critic loop.
- **Parallelize independent work, never a single argument.** Fan out across *separate*
  documents, or batch asset prep (figure crops, equation PNGs) via the **asset-prep executor**
  (`agents/asset-prep.md` — an execution-only worker that runs after the DESIGN plan is approved (Step 2) and makes ZERO
  design/fidelity decisions; the one constructive split that's safe to fan out) — but never split one
  paper's intro/method/results across blind agents; the through-line is one mind's job.
  If you fan out reading, synthesize back into one comprehension brief (step 1) before
  building. Parallelism speeds *gathering*, never *understanding*.
  Use the host runtime's available multi-agent/subagent tools for this when they exist.
- **Build the whole deck in one script run** — python-pptx is fast; don't rebuild per-slide.
- **Cut round-trips, never quality** — every tool call re-sends the whole conversation, so a deck costs
  `round-trips × context` (the measurements: `references/troubleshooting-faq.md`). Put independent
  calls — separate greps, file reads, a verification sweep — in ONE message, and:
  - **Look up EVERY helper you plan to call in one lookup, before writing the build script:**
    `python3 scripts/sigs.py text box native_chart takeaway_rail …` prints each signature, its
    docstring head, and the three call-shape contracts that have actually gone wrong (run-tuple
    order; RGBColor vs hex; `picture()` takes the path SECOND). Reading `deckkit.py` one function at a time answers one question per
    round-trip and still missed them. **`--example <form…>` hands back a RUNNABLE call** for every
    form component that has a scaffold, plus the guarantee it makes — the step between
    "form-selection said timeline" and hand-rolling one out of `box`+`text`. Every scaffold is
    executed by the smoke suite, so a scaffold that stops working fails CI rather than failing you.
    **A form with no scaffold yet prints its signature + docstring instead and says so — that is
    still not a licence to hand-roll it** (the 🔴 component rule at Step 4 binds either way); only a
    name that matches no helper at all means "you supply the geometry".
    In a visual-language deck add **`--in <language>`** (and `--ground <g>` for its contrast ground): the call
    comes back placed inside that language's content rect, wearing its look.
  - **Write the deck brief ONCE and point every dispatch at it** —
    `python3 scripts/

Conversación

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.

Inicia sesión para publicar

Desde GitHub

Estrellas en GitHub
669
Autor
addsumtech
Licencia
MIT
Último cambio de código
12 nov 2026
Archivos SKILL.md del repo (con traducciones y plantillas)
1
Temas
agent, ai, ai-agent, claude, claude-code, codex, powerpoint, ppt, pptx, presentation, presentation-generator, python