agentleFS
npownpow/claude-skills/slides/SKILL.md

slides

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Turns bullet points, research, or structured content into a browser-based Reveal.js slide deck. Use when the user asks to create slides, a presentation, a deck, a slideshow, or says "present this", "turn this into slides", "make a deck", or mentions keynote, powerpoint, or reveal.

82 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use banner-design, ui-styling and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 39 projects that use this

  • MicrosoftSkill

    ui-styling

    Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

    Also in 38 projects that use this

  • seikaikyoSkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 44 projects that use this

  • jpoindexterSkill

    fal-restore

    Restore and fix image quality — deblur, denoise, fix faces, and restore old documents using fal.ai's hosted restoration models.

    Also in 3 projects that use this

  • jpoindexterSkill

    faq-page

    A Frequently Asked Questions (FAQ) page with collapsible accordion sections, search functionality, and category filtering. Use when the brief asks for "FAQ", "help center", "questions", or "support page".

    Also in 3 projects that use this

  • xfstudioSkill

    fal-generate

    Generate images and videos using fal.ai AI models

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before delivering, verify ALL:

    line 29
  2. Very specific:

    Never allow headings to render uppercase: Always include .reveal h1, .reveal h2 { text-transform: none.

    line 43
  3. Distinctive:

    Always call wait_for before take_screenshot: Wait on the title text. Screenshotting before Reveal renders produces a blank white image.

    line 47
  4. Very specific:

    Always use new_page for first open: Use mcp__chrome-devtools__new_page with url: file:///tmp/slides.html.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slides

Converts content from the conversation into a Reveal.js HTML slide deck, writes it to /tmp/slides.html, and opens it live in the browser.

Workflow

  1. Extract content structure — identify the title, sections, and key points from the conversation or user-supplied content. See TEMPLATE.md for content chunking rules.
  2. Plan slide types and count — assign each section a slide type: title, bullet, two-column, quote, or code. Max 6 bullets per slide; split if more. See TEMPLATE.md for slide type patterns.
  3. Write /tmp/slides.html — use the complete Reveal.js template with all CDN links in correct order. See TEMPLATE.md for the full template.
  4. Render in browser — follow _shared/chrome-devtools-render.md to open /tmp/slides.html, wait for render, and screenshot. wait_for the title slide's main heading text. See TROUBLESHOOTING.md if slide rendering looks wrong.
  5. Tell user how to navigate — reply: "arrow keys to navigate, F for fullscreen".

Self-review checklist

Before delivering, verify ALL:

  • Screenshot shows a styled dark slide — not plain unstyled HTML text on a white background
  • Heading text is mixed-case, not ALL CAPS (custom CSS override applied)
  • No slide has more than 6 bullet points
  • CDN links appear in correct order: reveal.css, then black.css theme, then reveal.js
  • Reveal.initialize() is called with hash: true, transition: 'slide', backgroundTransition: 'fade'
  • wait_for was called before take_screenshot
  • User was told: arrow keys to navigate, F for fullscreen

Golden rules

Hard rules. Never violate these.

  1. Never allow headings to render uppercase. Always include .reveal h1, .reveal h2 { text-transform: none; } in custom CSS. Reveal.js default forces uppercase and it looks bad.
  2. Never put more than 6 bullet points on one slide. Split into two consecutive slides with a shared heading if needed (e.g. "Key Points (1/2)" and "Key Points (2/2)").
  3. Always load theme CSS after reveal.css. The order is: reveal.css, then theme/black.css. Reversed order silently breaks all theming.
  4. Always use hash: true in Reveal.initialize. This enables deep-linking to slides by index.
  5. Always call wait_for before take_screenshot. Wait on the title text. Screenshotting before Reveal renders produces a blank white image.
  6. Always use new_page for first open. Use mcp__chrome-devtools__new_page with url: file:///tmp/slides.html. Never navigate an existing page to a file:// URL.

Reference files

FileContents
TEMPLATE.mdComplete Reveal.js HTML template, all slide type patterns, content chunking rules
TROUBLESHOOTING.mdFailure diagnosis table: symptoms, causes, fixes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.