54 glukicov

slideops Skill

当用户想要关于代码仓库、其子系统、某项功能、架构或近期变更的幻灯片或演示文稿时使用。触发语包括 "make slides"、"build a slide deck"、"create a presentation"、"HTML slides for this repo"、"overview deck"、"team update slides" 等,或点名主题并要求制作相关幻灯片。当用户询问现有幻灯片是否仍与代码相符,或想重新检查、刷新或自动保持同步时也应使用,如 "is this deck still accurate"。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

SlideOps: generate a deck from a repository, and keep it true

This skill has two jobs, and the second one is the point.

Build: turn a repository into a 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, cheaply enough that nobody has to
remember to care.

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. That turns "is this deck still accurate?" from a question somebody has to
answer by reading into a command that answers itself:

python3 scripts/check.py docs/slides/ --repo .

Standard library only. No model, no network, no tokens, milliseconds to run. Two scripts
ship with this skill and do all of it: scripts/cite.py writes the
citations while you build, and scripts/check.py reads them back
afterwards. Writing the citations as you go (Step 3) is therefore not optional decoration:
it is the entire reason the deck can be maintained instead of rewritten. See
references/freshness.md for the mechanism and
references/automation.md for wiring it into pull requests,
scheduled refreshes, and agent hooks.

Which job is this?

  • The user wants a new deck: start at Step 0 below.
  • The user wants Markdown documentation instead of slides (a doc that lives in the

repo and renders on GitHub, with the same citations and the same freshness check):
follow references/markdown.md. It reuses this file's
research, confidentiality, and refresh rules and swaps the build and verify steps;
references/markdown-pdf.md covers exporting such a doc
to PDF. Checking or refreshing an existing .md doc is the same check.py workflow
as decks; sweeps pick both up together.

  • The user is asking whether an existing deck is still accurate, wants one

refreshed, or wants the check automated: go straight to
Refreshing an existing deck near the end. Do not rebuild
a deck from scratch because a few slides drifted.


Produces a single self-contained HTML slide deck (no build step, no CDN dependencies):
one 1280×720 slide per screen, click/arrow-key/URL-hash navigation, a progress bar and
slide counter, an Esc-toggled overview grid (deep-linkable as #overview), optional
per-slide speaker notes (