Skip to content
Back to search

beats-scenario

MarketplaceWorks with Claude CodeGitHub

A Claude skill for beat-based presentations in plain HTML, CSS and JS: one click = one beat, speaker notes and presenter window, no dependencies. (EN · ES)

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/samuelsolis--beats-scenario/badge.svg)](/listings/samuelsolis--beats-scenario)

HTML

<a href="/listings/samuelsolis--beats-scenario"><img src="/api/listings/samuelsolis--beats-scenario/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code, as a plugin (recommended)

/plugin marketplace add samuelsolis/beats-scenario
/plugin install beats-scenario@beats-scenario

Claude Code, by hand

git clone https://github.com/samuelsolis/beats-scenario.git
cp -r beats-scenario/plugins/beats-scenario/skills/beats-scenario ~/.claude/skills/

claude.ai (web and desktop)

Download `beats-scenario.zip` from the [latest release](https://github.com/samuelsolis/beats-scenario/releases/latest) and upload it as a skill in *Settings → Capabilities → Skills*.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "name": "beats-scenario",
  3. "owner": {
  4. "name": "Samuel Solis"
  5. },
  6. "metadata": {
  7. "description": "Beat-based presentations in plain HTML, CSS and JS, built with Claude."
  8. },
  9. "plugins": [
  10. {
  11. "name": "beats-scenario",
  12. "source": "./plugins/beats-scenario",
  13. "description": "Skill to build beat-based presentations: one click = one beat, fixed 1920×1080 stage, speaker notes and presenter window, no dependencies."
  14. }
  15. ]
  16. }
README.md · README · 97 lines
  1. # beats-scenario
  2. **English** · [Español](README.es.md)
  3. A skill for [Claude](https://claude.com) that builds **beat-based** presentations in plain HTML, CSS and JavaScript, with no dependencies and no build step.
  4. A beat-based presentation is not a list of slides. It is a fixed stage where **every click changes something**: a piece appears, another one leaves, a drawing turns into the next one. It is meant for lectures, talks and training sessions where drawings and code matter more than bullet points.
  5. | | |
  6. |---|---|
  7. | ![Three vectors placed inside another vector](docs/img/vector-de-vectores.png) | ![The vectors become a matrix](docs/img/matriz.png) |
  8. | ![Three stacked matrices form a cube](docs/img/cubo.png) | ![Code with highlighted lines next to a drawing](docs/img/codigo-y-dibujo.png) |
  9. *Screenshots from a Programming lecture made with the skill (in Spanish): a vector becomes a matrix and the matrix becomes a cube, beat by beat.*
  10. ## What it does
  11. - **One click = one beat.** The position lives in the URL (`#3.4` = scene 3, beat 4), so any beat is rebuilt the same way whether you move forward, go back or reload.
  12. - **Fixed 1920×1080 stage** that scales to any screen.
  13. - **Speaker notes and presenter window** (P key): current note, next note, timer and a thumbnail of the next beat, kept in sync with the main screen.
  14. - **Code with lines highlighted per beat** and basic syntax colouring for JavaScript, Python, C/C++ and PHP.
  15. - **Custom animations** through one hook per scene, for transformations that CSS alone can't do.
  16. - **Checking tools:** screenshots of any beat, a contact sheet, and a full walkthrough that reports errors, beats without notes and pieces that overflow the stage.
  17. - **No dependencies.** An `index.html` you open with a double click, with no server and no internet connection.
  18. Keys: → / click next · ← previous · 1–9 scene · O overview · P presenter · F fullscreen · B black screen.
  19. ## Installation
  20. ### Claude Code, as a plugin (recommended)
  21. ```
  22. /plugin marketplace add samuelsolis/beats-scenario
  23. /plugin install beats-scenario@beats-scenario
  24. ```
  25. ### Claude Code, by hand
  26. ```bash
  27. git clone https://github.com/samuelsolis/beats-scenario.git
  28. cp -r beats-scenario/plugins/beats-scenario/skills/beats-scenario ~/.claude/skills/
  29. ```
  30. ### claude.ai (web and desktop)
  31. Download `beats-scenario.zip` from the [latest release](https://github.com/samuelsolis/beats-scenario/releases/latest) and upload it as a skill in *Settings → Capabilities → Skills*.
  32. ## Usage
  33. Ask Claude for a presentation the way you would ask a person:
  34. > Prepare a 15-minute lecture on recursion for first-year students. Plain style, white background. The material is in `notes.pdf`.
  35. Claude first clarifies what you want to tell, to whom and with what look. Then it proposes the storyline scene by scene and waits for your go-ahead. Finally it builds the presentation scene by scene, checking each one with screenshots. Claude writes the presentation in your language. The result is a folder with:
  36. ```
  37. index.html scenes and notes
  38. tema.css the look of this presentation
  39. base.css stage mechanics (not to be edited)
  40. motor.js beats, URL, keyboard, presenter
  41. escenas.js custom animations
  42. presentador.html presenter window
  43. herramientas/ screenshots and walkthrough checks
  44. ```
  45. The file names and the attributes of the format are in Spanish, the language the skill was born in.
  46. ### The essentials of the format
  47. ```html
  48. <section class="escena" data-id="example" data-titulo="Example">
  49. <p data-in="2">appears at beat 2</p>
  50. <p data-in="2" data-out="4">visible at beats 2 and 3</p>
  51. <div data-on="3:highlighted">has the class from beat 3 on</div>
  52. <pre class="codigo" data-foco="2:1-3 4:5">…</pre>
  53. <aside class="nota" data-beat="2">what to say at beat 2</aside>
  54. </section>
  55. ```
  56. | Attribute | Meaning |
  57. |---|---|
  58. | `data-in="n"` | visible from beat *n* |
  59. | `data-out="n"` | hidden from beat *n* |
  60. | `data-on="n:class"` / `"n-m:class"` | adds the class from beat *n* (or only from *n* to *m*) |
  61. | `data-foco="beat:lines"` | highlights code lines at that beat |
  62. | `data-fuera` | on a scene: parks it (stays in the HTML, not shown) |
  63. | `<aside class="nota" data-beat="n">` | speaker note for beat *n* |
  64. The full details, design criteria and known pitfalls are in [`SKILL.md`](plugins/beats-scenario/skills/beats-scenario/SKILL.md) (in Spanish; Claude reads it in any language).
  65. ### Requirements for the checking tools
  66. Only for the checks, not for viewing the presentation: `google-chrome`, Node ≥ 21 and, for the contact sheet, Python with Pillow.
  67. ## License
  68. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.