agentleFS
Sign inStart free
EthanLLLEthanLLL/loom/skills/slides/SKILL.md

slides

Skill4 starsChanged 4 days agoMITView on GitHub

Make a slide deck, presentation or talk as a reveal.js web page shown in Loom's canvas. Use when the user asks for slides, a deck, a presentation, a PPT, "幻灯片", "做个 slide", "演示文稿", "做个 PPT" — and there is no existing .pptx/.key file to edit (editing one of those is a different job).

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. Very specific:

    Themes: only white, black, serif, dracula, white-contrast, black-contrast.

    line 105
  2. Distinctive:

    Keep the template's PDF button (bottom left) in every deck.

    line 131
  3. Distinctive:

    Only when they explicitly ask for a .pptx: convert the finished deck into a native, editable one — load each slide with Playwright, measure …

    line 138
  4. Very specific:

    Check the result with soffice --headless --convert-to pdf and pdftoppm.

    line 142

“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: a reveal.js deck in the canvas

A deck is one self-contained page, <output dir>/<deck-name>/index.html, which opens in the canvas. The user presents from there: the canvas has a full-window button that hides the chat and sidebar.

reveal.js and KaTeX are served by Loom itself under /vendor/, so a deck works whenever Loom does. Load them only from there — never from a CDN — and pull in nothing else from the network (no Google Fonts, no remote images): the deck must open on a bad connection.

Start from this

<!doctype html>
<html lang="zh-CN">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Deck title</title>
<link rel="stylesheet" href="/vendor/reveal.js/reset.css">
<link rel="stylesheet" href="/vendor/reveal.js/reveal.css">
<link rel="stylesheet" href="/vendor/reveal.js/theme/white.css">
<link rel="stylesheet" href="/vendor/reveal.js/plugin/highlight/monokai.css">
<style>
  /* The themes' fonts have no CJK glyphs; fall back to the system's. */
  .reveal { font-family: "Source Sans Pro", -apple-system, "PingFang SC",
    "Hiragino Sans GB", "Microsoft YaHei", "Noto Sans CJK SC", sans-serif; }
  .reveal h1, .reveal h2, .reveal h3 { font-family: inherit; text-transform: none; }
  /* Export button: reveal's own ?print-pdf view, then the browser's print dialog. */
  .export-pdf { position: fixed; left: 16px; bottom: 14px; z-index: 30; padding: 7px 12px;
    font: 600 13px/1 -apple-system, "PingFang SC", sans-serif; color: #555; cursor: pointer;
    background: rgba(255,255,255,.85); border: 1px solid rgba(0,0,0,.15); border-radius: 8px; opacity: .45; }
  .export-pdf:hover { opacity: 1; }
  html.print-pdf .export-pdf { display: none; }
</style>
</head>
<body>
<button class="export-pdf" type="button" title="导出 PDF">PDF</button>
<div class="reveal"><div class="slides">

  <section>
    <h1>Title</h1>
    <p>Subtitle</p>
  </section>

  <section>
    <h2>One idea per slide</h2>
    <ul>
      <li class="fragment">Points appear one at a time</li>
      <li class="fragment">Inline math $e^{i\pi} + 1 = 0$</li>
    </ul>
    <aside class="notes">Speaker notes go here.</aside>
  </section>

  <section>
    <h2>Code</h2>
    <pre><code class="language-elixir" data-trim data-line-numbers>
Process.send_after(self(), :tick, 1_000)
    </code></pre>
  </section>

</div></div>

<script src="/vendor/reveal.js/reveal.js"></script>
<script src="/vendor/reveal.js/plugin/highlight.js"></script>
<script src="/vendor/reveal.js/plugin/math.js"></script>
<script src="/vendor/reveal.js/plugin/zoom.js"></script>
<script>
  Reveal.initialize({
    width: 1280,
    height: 720,
    hash: true,
    slideNumber: "c/t",
    pdfSeparateFragments: false,
    // Keep the slides at any canvas width; see Rules.
    scrollActivationWidth: null,
    katex: { local: "/vendor/katex" },
    plugins: [RevealHighlight, RevealMath.KaTeX, RevealZoom],
  })

  // PDF: reload as reveal's print view, print once it has laid out, come back.
  document.querySelector(".export-pdf").onclick = () =>
    location.replace(location.pathname + "?print-pdf")
  if (/print-pdf/.test(location.search)) {
    Reveal.on("pdf-ready", () => setTimeout(() => window.print(), 300))
    addEventListener("afterprint", () => location.replace(location.pathname))
  }
</script>
</body>
</html>

Rules

  • Keep scrollActivationWidth: null. Below 435px wide reveal switches to a scrolling view, and the canvas is that narrow with its file tree open; widening it again (the tree closed, full window, F) then leaves only the backgrounds, the text gone.
  • Themes: only white, black, serif, dracula, white-contrast, black-contrast. The others import Google Fonts and break offline.
  • Plugins: highlight, math (KaTeX, always with katex: { local: "/vendor/katex" }), zoom, search, markdown. Not notes: the canvas is sandboxed, so the speaker-notes window comes up blank. <aside class="notes"> is still fine to write — it is just not shown.
  • Images and other assets go beside index.html and are referenced relatively (img/arch.png), never by absolute path or URL.
  • Charts: draw them as inline SVG or plain HTML/CSS. There is no charting library under /vendor/. Give each slide's <svg> its own <defs> (arrow markers, gradients) with ids unique in the page: reveal hides the other slides, and a url(#id) pointing into a hidden one renders nothing.
  • Content: one idea per slide, at most about six short bullets, no paragraphs. Use class="fragment" to build a slide up step by step, and nested <section>s (vertical slides) only for optional detail.
  • Fit: everything must fit in 1280×720 without scrolling. Split a slide rather than shrink its text.

Revising

Edit the same index.html in place; the canvas shows the newest version. hash: true keeps the URL on the current slide, so after the canvas reloads the user stays where they were.

Exporting

Keep the template's PDF button (bottom left) in every deck. It reloads the deck as reveal's print view, opens the browser's print dialog, and comes back when the dialog closes — the user picks "Save as PDF", in their own browser, so nothing is rendered on the server. One page per slide, fragments shown (pdfSeparateFragments: false). Tell them: margins "None", "Background graphics" on. On a dark theme, restyle the button so it stays visible.

Only when they explicitly ask for a .pptx: convert the finished deck into a native, editable one — load each slide with Playwright, measure every element's box and style, and rebuild it with python-pptx (1 CSS px = 9525 EMU on a 1280×720 page). If ~/annual-review/scripts/to_pptx.py exists, start from it. Check the result with soffice --headless --convert-to pdf and pdftoppm; for layout only, since the fonts differ from PowerPoint's.

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.

Check your setup, free