SlideOps plugin
A plugin that turns a repository into a deck or doc and shows in milliseconds which slides drifted from the code.
- 54 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent reads repository source code and writes deck and document files into `docs/slides/`.
- Visual verification launches headless Chrome and Python scripts.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/slideopsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent reads repository source code and writes deck and document files into `docs/slides/`.
- Visual verification launches headless Chrome and Python scripts.
This is third-party code. Review the repository files before installing.
What it does
SlideOps is a pair of skills, `slideops` and `slides-to-pdf`. Say "make slides about this repo" and the agent first scans the code, proposes concrete topics with a "why now" note, asks a short set of questions about audience, length and theme and agrees an outline with you. Only then does it write HTML: one self-contained file with no build step or outside dependencies. Every quoted code snippet carries a source reference: file, lines and hash. Later in the same repository the question "is the architecture deck still accurate" runs `scripts/check.py`. A standard-library Python script with no model and no network reports in milliseconds which slides quote changed, moved or deleted code and hands the agent a JSON repair brief. The agent fixes what drifted and does not regenerate the whole file, so the pacing and storyline survive.
Who it is for. Teams that keep architecture decks and docs about a repository and do not want them to go stale unnoticed.
Good fit when
- Before an architecture review you need a deck about the code, with topics found in the repository itself.
- Six months later you need to learn which slides no longer match the code.
- You need a Markdown document where every quoted snippet is checked by the same sweep as slides.
- A finished deck must export to PDF and you must confirm the pages are not blank.
Not a fit when
- You need a deck unrelated to code: a marketing landing page or a pitch.
- Finished slides live in PowerPoint or Keynote: the skill writes HTML and Markdown.
- The machine has no Chrome, while visual verification and PDF export need it headless.
Example request
Make a deep dive on the authorization subsystem: 15 slides, Ledger Dark theme, with a PDF. Show the outline for approval first.Limitations
The freshness check catches drift in code quotes but does not decide whether a slide claim is true: the agent only flags such slides for a human to review. Visual verification and PDF export need headless Chrome: a Playwright Chromium cache or a system Chrome works. The scripts use only the Python standard library. Third-party Claude Code marketplaces do not auto-update by default, so turn updates on in `/plugin`, Marketplaces. Four themes are built in: Ledger Light, Ledger Dark, Midnight and Graphite.
How to disable. Remove the `slideops` plugin through `/plugin`, or the skills from the agent directory if you installed with `npx skills`. Created decks live in `docs/slides/` in your repository and stay.
FAQ
How do I install SlideOps?
In Claude Code run `/plugin marketplace add glukicov/slideops`, then `/plugin install slideops@slideops`. For other agents use `npx skills add glukicov/slideops`, and for Codex, Copilot CLI and OpenCode there is `./install.sh` from a clone.
How do I know a deck is out of date?
Ask the agent "is the architecture deck still accurate". It runs `scripts/check.py`, gets a status for each slide and re-quotes snippets that merely moved. Slides whose claim might no longer hold are flagged separately.
Can I get a document instead of a deck?
Yes, since version 1.1.0. A request like "write markdown docs for the sync subsystem" creates a single `.md` with invisible citation comments above each snippet and the build commit stamped on line 1.
Which slide patterns does SlideOps support?
Thirteen patterns: title, agenda, section divider, prose with cards, reference table, before and after code, annotated snippet, flow diagram, lane comparison, image with caption, chat bubbles and closing. Mermaid diagrams are pre-rendered to inline SVG at build time.
Do freshness checks need a network and tokens?
No. `scripts/check.py` runs on the Python standard library with no model and no network and takes milliseconds.
Discussion
No questions or reviews yet.
Related
PluginsA skill for HTML presentations: a theme and two preview slides for approval, then the deck, PDF and PowerPoint export and a link
A skill that builds a PowerPoint deck with live text, charts and tables: an image model draws each slide, the agent rebuilds it.
A skill that builds Slidev presentations from your materials and returns offline HTML you can edit and export to PDF.
A skill for single-file, dependency-free HTML presentations: 22 styles, a BRIEF.json plan and content review.
A Claude Code and Codex workflow that makes native PPTX decks where every element stays editable in PowerPoint.
A Claude Code plugin for technical talks on Slidev: from idea and outline to slides, visual review and PDF export.
README in short
The README frames the idea this way: a document is built from a source like code and keeps a reference to it. It shows installation for Claude Code, Codex, Copilot CLI and OpenCode, example requests, the freshness check, four themes and verified PDF export.