agentleFS
aemerson-commitsaemerson-commits/shareable-skills/skills/html-slides/SKILL.md

html-slides

Skill1 starsChanged 8 months agoMITView on GitHub

HTML Slides — Create polished, interactive HTML presentation slides from a single prompt. Output is a self-contained HTML file. Triggers: 'create a presentation', 'make slides', 'build a deck'.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create polished, interactive HTML presentation slides from a single prompt.

    line 8
  2. Distinctive:

    When the user asks to create a presentation, slides, deck, or similar.

    line 12
  3. Distinctive:

    Ask user for topic/content if not provided

    line 109

“Common” is measured: kept by at least 6 in 10 of the 7 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

HTML Slides

Create polished, interactive HTML presentation slides from a single prompt. Output is a self-contained HTML file with embedded CSS and JS — no dependencies needed.

Trigger

When the user asks to create a presentation, slides, deck, or similar. Examples: "make a presentation about X", "create slides for the meeting", "build a deck on Y".

Output

A single .html file saved to the user's specified location (default: a temp or output directory). The file is self-contained and can be opened directly in any browser.

Design Principles

  • Professional and clean — avoid "AI-flavored" design. Use generous whitespace, strong hierarchy, and restrained color.
  • Dark theme by default — dark backgrounds (#0f172a to #1e293b range), light text.
  • One idea per slide — short headlines, supporting bullets or visuals. Never wall-of-text.
  • Keyboard navigation — arrow keys, spacebar, or click to advance. Show slide counter.
  • Responsive — works on projector (16:9), laptop screen, or tablet.
  • Print-friendly — include @media print styles for handout mode.

Structure

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>{Presentation Title}</title>
  <style>
    /* All styles inline — no external deps */
  </style>
</head>
<body>
  <div class="deck">
    <div class="slide" id="slide-1">...</div>
    <div class="slide" id="slide-2">...</div>
    <!-- ... -->
  </div>
  <div class="slide-counter">1 / N</div>
  <script>
    /* Keyboard/click navigation, slide counter, transitions */
  </script>
</body>
</html>

Slide Types

Support these slide layouts:

TypeUse
TitleOpening slide — large title, subtitle, date/author
SectionSection divider — large centered text
ContentHeadline + bullet points (3-5 max)
Two-ColumnSide-by-side content, comparison, before/after
ImageFull-bleed image with caption (user provides URL or base64)
QuoteLarge quote with attribution
DataKey metrics, KPI cards, simple charts (CSS-only bar charts)
TimelineHorizontal or vertical timeline of events
SummaryKey takeaways, action items, next steps

Navigation JS

let current = 0;
const slides = document.querySelectorAll('.slide');
const counter = document.querySelector('.slide-counter');

function showSlide(n) {
  slides.forEach(s => s.classList.remove('active'));
  current = Math.max(0, Math.min(n, slides.length - 1));
  slides[current].classList.add('active');
  counter.textContent = `${current + 1} / ${slides.length}`;
}

document.addEventListener('keydown', e => {
  if (e.key === 'ArrowRight' || e.key === ' ') showSlide(current + 1);
  if (e.key === 'ArrowLeft') showSlide(current - 1);
  if (e.key === 'Home') showSlide(0);
  if (e.key === 'End') showSlide(slides.length - 1);
});

document.addEventListener('click', e => {
  if (e.clientX > window.innerWidth / 2) showSlide(current + 1);
  else showSlide(current - 1);
});

showSlide(0);

CSS Foundation

  • Slides: width: 100vw; height: 100vh; display: flex; flex-direction: column; justify-content: center; align-items: center;
  • Transitions: opacity or transform with 0.3s ease
  • Font stack: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif
  • Accent color: Derive from topic (blue for tech, green for finance, orange for operations)
  • Code blocks: font-family: 'Fira Code', monospace; background: rgba(0,0,0,0.3); border-radius: 8px; padding: 1.5rem;

Workflow

  1. Ask user for topic/content if not provided
  2. Outline the slide structure (titles only) and confirm with user
  3. Generate the full HTML file
  4. Save to disk and report the file path
  5. Offer to open in browser via Chrome DevTools MCP if available

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.