# Lecture Style

Masterclass lecturing, one continuous explanation carried by slides, with dense pages...

- Repository: https://github.com/THU-MAIC/OpenMAIC (42385 stars)
- Category: Documents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add THU-MAIC/OpenMAIC --skill lecture-style -g -a claude-code -y`
Codex: `npx skills add THU-MAIC/OpenMAIC --skill lecture-style -g -a codex -y`
Cursor: `npx skills add THU-MAIC/OpenMAIC --skill lecture-style -g -a cursor -y`
Gemini CLI: `npx skills add THU-MAIC/OpenMAIC --skill lecture-style -g -a gemini-cli -y`

## Description

Masterclass lecturing, one continuous explanation carried by slides, with dense pages, long narration that builds an argument across several real cases, and checkpoints that are rare and deliberate. Use when the ask is a lecture, a masterclass, a systematic walkthrough of a subject, 「大师课」「系统讲解」「讲透」, or any topic whose payoff is understanding rather than practice; also use when the user names this style. Not for hands-on training (that is `workshop-style`) and not for a course whose point is manipulating a mechanism (that is `deep-interactive`).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Masterclass lecture design

You are designing a **lecture**. One voice carries the learner from not knowing
the subject to being able to explain it, and the pages exist to support that
explanation rather than to interrupt it. Density is a feature here: a lecture
page that says one thing is a wasted page.

`stage-design` still governs how the stage is built, outline, roster, one page
per `generate_scene`, audio before done. This skill governs what the stage
contains and how it sounds.

## The shape

- **Scene 1 is a `slide`** that opens the lecture properly, the question the
  subject answers, why it is worth an hour, and the route the lecture takes
  through it. Not a definitions page and not a table of contents.
- **The body is `slide` pages, in arcs.** An arc is three to five pages that
  carry one idea from statement to consequence, the claim, the mechanism
  underneath it, then real cases that test it. Arcs follow each other; the
  lecture never restarts.
- **Checkpoints are rare.** One `quiz` roughly every four to five pages, placed
  at the seam where one arc closes and the next begins, testing whether the
  learner can apply the arc's idea rather than recall its words. Two quizzes in
  six pages is not a lecture, it is a test with slides in between.
- **At most one `interactive` page**, at the single most mechanism-heavy concept
  in the whole lecture, the one place where telling genuinely fails and the
  learner has to see the thing move. If the subject has two such concepts, a
  second is defensible; a third means the request was never a lecture and
  `deep-interactive` fits it better.
- **Close on the argument**, not on a bullet recap: what the lecture
  established, what it deliberately left open, where a curious learner goes
  next.

## Page density

The rest: https://github.com/THU-MAIC/OpenMAIC/blob/HEAD/skills/agent-runtime/lecture-style/SKILL.md