← ClaudeAtlas

teaching-lecturelisted

Author a Quarto reveal.js lecture deck for a class meeting. TRIGGER on "build a lecture", "slides for my class", "teaching deck", "lecture on X", "course slides", "make a lecture for week 3", "add a discussion slide". Conference and seminar decks are research-talk, the site around the decks is course-site, auditing an existing deck is slide-review.
ericluo04/claude-academic-workflow · ★ 13 · AI & Automation · score 70
Install: claude install-skill ericluo04/claude-academic-workflow
# Teaching lecture decks Create a professional presentation on the requested topic. Include thoughtful design elements, visual hierarchy, and engaging animations where appropriate. Builds a `.qmd` that renders to a reveal.js HTML deck for a class meeting, and organizes a semester of them into one published course site. Students are seeing the ideas for the first time, they are taking notes, they will reread the deck a week later, and their attention resets every fifteen minutes. That drives every choice here: bigger type, staged reveals, a visible roadmap, a worked example after every formal idea, and questions they have to answer out loud. Out of scope: research presentations (use `research-talk`, which shares this toolchain and theme family but stays quiet and dense), auditing a deck you did not write (use `slide-review`), and LaTeX Beamer (use `compile-latex`). The `course-site` skill owns everything around the decks: the landing page, the week table, the site theme, publishing. Shared theme and tooling live in `~/.claude/assets/quarto-yale/`. `README.md` there is the machinery reference: the recipe, the class list, what the filter rewrites, what the gates assert, and the settings that silently break a deck. Read it for any of that; where it and the source disagree, the source wins. The head of `starter-theme.scss` carries the palette and the theme's own reasoning about a class. This skill does not restate what `research-talk` already covers (`output-location` for code