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

What it does

Talks as beats, not slides: a fixed 1920×1080 React stage where one click is one beat. Offline, deterministic, presenter view, and a Claude Code skill.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category Programación
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/borjaperfra-beatdeck.svg)](https://mcp.popnx.com/en/skills/borjaperfra-beatdeck)

Úsalo junto con

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

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

de morlutoMuy usado↓ 388,7 mil/sem★ 464,1 milActualizado hace 5 días

MCP · Conecta un servicioSe ejecuta en tu computadora

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

de fallow-rsMuy usado↓ 2,4 M/sem★ 5,4 milActualizado hoy

MCP · Conecta un servicioSe ejecuta en tu computadora

Desktop Commander

MCP server for terminal commands, file operations, and process management

de wonderwhy-erMuy usado↓ 740,3 mil/sem★ 10,3 milActualizado hace 5 días

MCP · Conecta un servicioSe ejecuta en tu computadora

Skills parecidas

Mismo tipo de trabajo, ordenadas como la lista de Skills

Comparado con otros parecidos
Este
beatdeck
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
Autorborjaperframorlutomultica-aiGraphify-Labsharry0703
Skills11111
Estrellas de GitHub244463.670233.682148.887143.987
Último cambio de código2 oct 202617 nov 202620 abr 202617 nov 202616 nov 2026
Licencia–MIT–Apache-2.0MIT

1 skills (conjuntos de instrucciones) de borjaperfra 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 Code

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

Instalar

Is it safe?

  • Who made it

    GitHub account borjaperfra (person), 3 years old

  • Use and upkeep

    ★ 244 stars, few users so far · code last changed 2 oct 2026

  • Any scripts?

    1 scripts that can run on a computer: scripts/extract_pptx.py

  • Uses the internet?

    No internet calls found in the scripts

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

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

  1. Download from GitHub

    This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the skills/building-a-beatdeck folder again. The ZIP must have a building-a-beatdeck folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick building-a-beatdeck.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    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 12 nov 2026 · Source: support.claude.com, support.claude.com, code.claude.com

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 /building-a-beatdeck, 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

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 /building-a-beatdeck, 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 building-a-beatdeck en ~/.agents/skills/building-a-beatdeck

~ 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 building-a-beatdeck

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 building-a-beatdeck

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: building-a-beatdeck
description: Builds a talk as a beatdeck - a fixed 1920x1080 React stage where one click is one beat, with authored motion, presenter view, overview, and an offline self-contained build. Covers turning source material (PPTX, Keynote/PDF export, Markdown, notes) into a content audit and a scene/beat map, choosing or applying a theme, writing scene layers, automatic beats, and verifying every beat with npm run verify. Use whenever the task is creating, porting, restyling, rehearsing or fixing a presentation, talk, keynote, slide deck or conference session that should feel like a live system rather than slides, or whenever the repo contains src/beatdeck/.
license: MIT
---

# Building a beatdeck

A beatdeck is a talk written as code: **8-ish scenes, each made of beats; one click = one beat**. The stage is a
fixed 1920×1080 canvas scaled into any screen with black letterbox. Everything is bundled, so it runs with Wi-Fi off.

Your job is to turn what the speaker wants to say into beats that feel authored — not to reproduce slides.

**Paths.** `references/…` and `scripts/…` below are relative to the folder of this SKILL.md, wherever the skill
is installed (plugin, `~/.claude/skills/`, or `skills/building-a-beatdeck/` inside a deck project). Everything
else (`deck/`, `src/`, `npm run …`) is relative to the deck project.

## 0 · Get a deck repo

If the working directory has no `src/beatdeck/`, scaffold one, clean it and install:

```bash
npx degit borjaperfra/beatdeck my-talk && cd my-talk
npm run init -- --title "<title>" --author "<speaker>" --lang <en|es|…> [--theme light] [--demo]
npm install
```

`init` strips what belongs to the beatdeck repo, not to a talk (the Kernel Panic showcase and its non-MIT
assets, plugin files, beatdeck's README, changelog and CI), renames the package and writes title/author/lang/
theme into the deck. `deck/` becomes a **blank two-scene starter** (standby + title, questions + QR) to build
on; `--demo` keeps beatdeck's 6-scene demo instead, as a reference to read and replace. It also creates
`reference/` (put the source there), `docs/CONTENT-AUDIT.md` and `docs/RUNBOOK.md` from the templates, the talk's
`AGENTS.md` and a CI workflow that builds and verifies every push.
Use `--theme light` when the room is bright or the talk is streamed. Run it once; it deletes itself.
It also resets the demo's `qrUrl` to `TODO` and clears its tagline: set the real QR target only from the source.

Then read `AGENTS.md`. The demo deck (on GitHub in `deck/`, or locally with `init --demo`) is the reference
implementation of every pattern below. `init` removes the heavier example from your project; read it on GitHub when you need it:
https://github.com/borjaperfra/beatdeck/tree/main/examples/kernel-panic — a 47-beat production talk. Look at
`index.tsx` (custom chrome, `isCut` + `Overlay` for a cut to black), `deck/timeline.ts` (every kind of automatic
beat), `architecture/` (one SVG world spanning several scenes) and `simulation/` (a Canvas 2D particle layer).

The talk lives in `deck/`. Never edit `src/beatdeck/` for one talk; if the engine truly lacks something, add it
generically there and say so (`npm run upgrade` replaces engine files; edits are backed up, not merged).

**Existing talk project?** If `.beatdeck.json` exists, `npm run upgrade -- --dry-run` shows whether a newer engine
is available; upgrade only when the user agrees, then `npm install && npm run verify`, and merge any
`*.beatdeck-new` file it reports.

## 1 · Collect the source

Ask for (or find) the source material and the facts you must not guess: title, speaker, event, date, the QR
target URL, real screenshots/logos/photos. Put originals in `reference/` (read-only from then on).

- **PPTX**: `python <skill folder>/scripts/extract_pptx.py deck.pptx reference/source` → one Markdown file with
  every slide's text, speaker notes and media, plus the media files. (Inside a scaffolded project the skill
  folder is `skills/building-a-beatdeck/`.)
- **PDF / Keynote**: export to PDF and read it page by page; ask for the original images.
- **A written script (Markdown, a doc, notes)**: use as is, and read it by kind of content:
  - **narration** (prose, `>` quotes: what the speaker *says*) → the presenter view (`source` / `note`). On
    stage it becomes a short statement in the speaker's own words — condensed, never reworded into new claims;
  - **facts** (bullets, figures, names) → on stage, exactly as written (same numbers, same rounding, same "~");
  - **code blocks, commands, formulas, output** → on stage character for character (`Terminal`, or a
    `data-exact` element — see step 6), never retyped from memory;
  - **stage directions** ("on screen…", "show how it grows…") → instructions for you, not text to display.

**Nobody to ask?** If you are working without the speaker, decide, record each decision in the audit's
"Decisions taken on the speaker's behalf", and list them in your hand-off. Keep the neutral theme and its
accent unless a brand is given — choosing a palette is an art direction, not a default.

Real artefacts beat redraws: if the source shows a tweet, a logo, a product photo or a meme, use the real file.
Never invent quotes, numbers, tweet text, URLs or logos. Missing facts become explicit `TODO`s and questions.

## 2 · Content audit (before any code)

Write `docs/CONTENT-AUDIT.md` from `references/content-audit-template.md`: every source slide → the beat(s)
that carry it, what is kept, restored or deliberately cut, and open questions. This is what lets you say
"nothing was lost" later. Show it to the user when it changes what the talk says.

## 3 · Beat map

Turn the audit into `deck/scenes.ts` (`SceneDef[]`). Rules (details in `references/beat-model.md`):

- A **scene** is a mode of the talk (a stage world), not a slide title. 5–9 scenes is typical; keys 1–9 jump
  to scenes, so more than 9 leaves the rest reachable only by stepping or the overview (O).
- A **beat** is one idea landing. If two things must appear on separate clicks, they are two beats.
- `auto: true` marks a beat whose motion runs by itself and takes noticeable time (a boot sequence, a counter,
  a cascade of warnings, a typed command). The presenter flags it and `verify` waits for it. Everything else
  waits for the click. Two ways to implement it — pick the lighter:
  - **self-contained** (a `Typewriter`, a `CountUp` that restarts on entry): no `timeline` needed;
  - **state-driven** (other layers react to its progress, a later beat depends on it, or it advances by itself):
    a `Live` field + `initialLive` + `timeline` in `deck/timeline.ts`. See `references/beat-model.md`.
- Fill `ref` (where it comes from), `source` (what the source says) and `note` (speaker cue) — the presenter
  view shows them; the audience never does.
- Keep the first scene's first beat as a calm standby screen: the talk starts on the first click. On a dark
  theme it can be pure black (`isBlack`); on a light theme use the theme background — anything drawn on a
  forced-black standby must not use theme ink colours.

## 4 · Visual direction

Default to the neutral theme (`themes/neutral.css`): near-black stage, off-white type, one accent, hairlines,
huge editorial type, negative space. Bright room, daylight or a stream → `themes/light.css` on top of it
(`init --theme light` does this). If the speaker has a brand, change tokens (`--accent`, fonts, `--bg`) in a
theme file — do not invent a new art direction, decorative labels, stickers, gradients, rounded cards or a
dashboard look. If a design reference exists (Figma, a v3 HTML prototype, a brand book), it decides *how it
looks and moves*; the source decides *what is said*. Record conflicts in the audit.

Fonts must be local: `@fontsource-variable/*` packages or `.woff2` files in the deck, plus their specs in
`fonts` of the deck definition so the first frame never shows a fallback face.

## 5 · Build the scenes

Read `references/authoring.md` and

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
244
Autor
borjaperfra
Licencia
Sin licencia indicada Este repo no indica licencia: por defecto el autor conserva todos los derechos. Pregunta antes de compartirlo o usarlo comercialmente.
Último cambio de código
2 oct 2026
Archivos SKILL.md del repo (con traducciones y plantillas)
1
Temas
claude-code, claude-skill, gsap, presentation, react, slides, talk