SlideOps Skills

Generate repository-backed slide decks and detect when their claims drift from code.

SlideOps packages deck creation with slide-to-PDF export. It connects slide claims to source citations, checks freshness, and prepares focused repair work for changed slides.

Use cases

• Explain a repository with a slide deck
• Check whether existing slides still match code
• Export a deck to PDF

How to use

Provide a repository and the audience for the deck. Keep the generated deck’s citations, then use the upstream freshness checker after code changes and rebuild affected slides.

Skills

• slideops

  Use when the user asks for slides, a slide deck, or a presentation about a code repository, one of its subsystems, a feature, an architecture area, or its recent changes. Triggers include "make slides", "build a slide deck", "create a presentation", "HTML slides for this repo", "overview deck", "team update slides", "slides for our latest changes", or naming a topic and asking for a deck about it. Also use when the user asks whether an existing deck still matches the code, or wants one rechecked, refreshed, or kept in sync automatically: "is this deck still accurate", "check the slides against the code", "did anything we documented change", "refresh the architecture deck", "these docs are stale", "fail the build when the deck stops matching the code", or asks to wire that check into CI, a pull request, or an agent hook. Also use for Markdown documentation instead of slides ("write markdown docs", "a design doc with citations", "docs that know when they go stale"), including PDF export of a doc.

  glukicov/slideops

• slides-to-pdf

  Use when the user asks to convert, export, or save an HTML slide deck as a PDF ("save the slides as PDF", "export the deck to PDF", "make a PDF of the presentation"). Works on decks built by the SlideOps (slideops) skill and on any single-file HTML deck that shows one slide per URL hash (#1,

  glukicov/slideops