slideops
Lets your agent turn a repository into slides. It creates HTML presentations with code citations and detects when content becomes outdated.
What it does
Turns a code repository into an HTML presentation with citations. It also checks if the presentation still matches the code.
When to use it
- ✓When you want to create a presentation about a code project.
- ✓When you want to know if a code presentation is still up-to-date.
- ✓To automate checking for updates in code presentations.
Example of what to ask your AI
“Create an HTML presentation about this code repository.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It takes snippets from your code, notes where they came from (file, lines, exact code), and builds a presentation. Then, a script checks if these snippets still exist and are the same in the current code.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill slideopsOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/slideops/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Bundled upstream support
Supporting files are included at skill-relative paths. See UPSTREAM-NOTICE.md for their pinned sources, licenses, hashes, and import changes.
SlideOps: slides from a repo, that tell you when they go stale
Catalog copy, frozen at v1.0.0. The canonical source is glukicov/slideops, which also carries the deck template, the two citation scripts, the reference docs, and the companion
slides-to-pdfskill. Install from there; this page summarizes the workflow.
Overview
SlideOps has two jobs, and the second one is the point. Build: turn a repository into a single self-contained HTML slide deck whose every claim came from the code, not from a model's impression of the code. Keep in sync: make that deck able to prove, months later, whether it still matches the repository.
The mechanism joining them is a citation. Every quoted snippet records the file, the line
range, and a hash of those source lines at build time, and the deck records the commit it
was built from. "Are these slides still accurate?" becomes a command instead of a
re-read: a standard-library Python script diffs each citation against the current code
and reports CURRENT, MOVED, CHANGED, or MISSING. No model, no network, no tokens,
milliseconds to run.
When to Use This Skill
- Use when the user asks for slides, a slide deck, or a presentation about a code repository, one of its subsystems, a feature, or its recent changes: "make slides", "overview deck", "team update slides", "HTML slides for this repo".
- Use when the user asks whether an existing deck still matches the code, or wants one rechecked, refreshed, or kept in sync: "is this deck still accurate", "check the slides against the code", "these docs are stale".
- Use when the user wants deck freshness wired into CI, a pull request check, or an agent hook: "fail the build when the deck stops matching the code".
- Do not use for slide decks about anything other than a codebase (a sales deck, a lecture); the citation mechanism assumes a git repository as the source of truth.
How It Works
Step 1: Install from the canonical repo
In Claude Code, as a plugin (both skills, background updates):
/plugin marketplace add glukicov/slideops
/plugin install slideops@slideops
Or for Codex CLI, Copilot CLI, and OpenCode, one installer covers all of them:
git clone https://github.com/glukicov/slideops && cd slideops
git checkout ba43e89bc7936649be36a1796a62203f704f8c60 # the v1.0.0 release commit
./install.sh
The checkout pins the exact commit this catalog copy froze at, which is what a reader
can verify independently. (The canonical repo also blocks retargeting of v* tags with
an active tag ruleset, but a SHA does not ask you to trust that.) install.sh symlinks
the two skills into ~/.claude/skills (read by Claude Code and OpenCode) and
~/.agents/skills (read by Codex CLI and Copilot CLI).
Step 2: Build a deck
The skill walks a fixed pipeline: a two-minute repo scan, one compact intake (topic,
audience, length, theme, scope, extras), an outline checkpoint before any HTML is
written, then slide-by-slide construction from a verified template. Every snippet is
cited as it is written. Run the citation script from inside the repository being
presented, via its installed path (an agent resolves scripts/ against the skill's own
directory automatically; the paths below are for running it yourself after
install.sh):
python3 ~/.agents/skills/slideops/scripts/cite.py app/main.py:40-58 --repo . --snippet # prints data-src + data-sha256
python3 ~/.agents/skills/slideops/scripts/cite.py --stamp deck.html --repo . # stamps the build commit
--repo always points at the repository the deck is about, never at the SlideOps
checkout.
Every slide is then rendered with headless Chrome and visually verified before the deck is considered done.
Step 3: Check it later, for free
From inside the repository being presented, same path convention as Step 2:
python3 ~/.agents/skills/slideops/scripts/check.py docs/slides/ --repo .
Real output, from the demo deck that ships with the skill:
Deck: skill-demo.html
Built: commit=179bbdb date=2026-08-28 repo=slideops
slide 9 THEMING skills/slideops/assets/template.html:22-45 CURRENT
…
FAQ
What are the 'citations'?
These are annotations that state exactly which part of the code was used in each slide, including the file, line numbers, and a verification code (hash).
How does it know if the presentation is outdated?
A script compares the code snippets cited in the presentation with the current code in the repository. It reports if the code has changed, moved, or disappeared.
Can I use this for any type of presentation?
No, it works best for presentations about code, as it relies on a repository as the source of truth.
Details
Original description by the author
Turn a repository into a cited HTML slide deck and detect the day it drifts from the code. Citations record file, lines, and hash; a stdlib check reports CURRENT, MOVED, or CHANGED.
Popularity
- GitHub stars
- 48k
- Ranking position
- #4196
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
architecture-decision-records
Has your agent record important project structure decisions. It helps to understand the reasoning behind choices and maintain a clear history of changes.
affaan-m/ECC
code-tour
Lets your agent create step-by-step code walkthroughs with exact file and line anchors. It's useful for project introductions, code explanations, or change reviews. Helps understand how a system works.
affaan-m/ECC
codebase-onboarding
Helps your agent analyze unfamiliar code and create an onboarding guide. It includes an architecture map, entry points, and conventions. Ideal for starting on a new project.
affaan-m/ECC