course-slides — Claude Code skill: what it does, how to install
course-slides converts handouts and lesson plans into structured slide decks with clear bullet points and complete speaker scripts.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill course-slides -a claude-codeWhat course-slides does
The skill acts as a courseware designer for educators. It starts by clarifying target students, session duration, and interactive preferences, adopting a default pace of one slide every 2-3 minutes. Before touching presentation files, it returns an outline where each line lists slide number, title, core takeaway, and layout type. Full deck production stays paused until you confirm that outline.
Output decks separate student view from instructor notes. Slides stay brief with a cap of four bullets, each around eight words maximum. Detailed explanations, pacing estimates, and conversational speech scripts land in speaker notes running 60 to 150 words per slide.
The process relies on local slide tools being present to write PowerPoint decks. Content rules forbid three text-only slides in sequence, forcing a switch to diagrams, worked examples, or interactive questions.
What it helps with
- turn lesson handouts into an outline matching target session time
- generate first-person speaker scripts with clear timing per slide
- split complex walkthroughs into distinct problem and solution slides
- format lecture materials into PowerPoint presentations without wall-of-text slides
Example prompts for the agent
- Turn this lesson plan into a deck of about 20 slides.
- Build a training deck with a speaker script from this handout
handout.md. - Create a 45-minute slide deck with interactive questions from these lecture notes.
How to install course-slides
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill course-slides -a claude-code2Manually: put the files in place
~/.claude/skills/course-slides/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/course-slides/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill course-slides -a codex2Manually: put the files in place
.agents/skills/course-slides/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill course-slides -a cursor2Manually: put the files in place
.cursor/skills/course-slides/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/course-slides2Manually: put the files in place
.github/skills/course-slides/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill course-slides -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/course-slidesManually: put the files in place
.devin/skills/course-slides/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about course-slides
How to install course-slides in Claude Code?
Run npx skills add genspark-ai/genoffice --skill course-slides -a claude-code or place the file directly at ~/.claude/skills/course-slides/SKILL.md.
What does course-slides do?
It extracts core concepts from teaching materials, agrees on an outline first, and produces a PowerPoint deck where slides keep bullets minimal while notes carry the full speech script.
Can it build slides immediately without showing an outline?
Its built-in workflow explicitly waits for your outline sign-off first so you can tweak structure and pacing before deck creation runs.
Source text
SKILL.md · Apache-2.0
---
name: course-slides
description: Turn a handout or lesson plan into a slide outline, then after confirmation build the full courseware deck with key points on every slide and a teaching script in the notes, delivered as a PowerPoint deck
category: education
scenarios: Teaching courseware | Training slides | Speaker notes
quickPrompts: Turn this lesson plan into a deck of about 20 slides | Build a training deck with a speaker script from this handout
metadata:
version: 1.0.0
---
You are a courseware specialist. The user gives you a handout, a lesson plan or a list of knowledge points; you first align on a slide outline, then build the full deck, every slide carrying distilled key points and a speaker script the teacher can read from.
## Workflow
1. Confirm three things (ask if missing): the audience and session length, the slide budget (default one slide per 2-3 minutes), and whether interactive slides (questions / exercises / discussion) are wanted. If a lesson plan exists, reuse its stages and time allocation as they are.
2. Break down the structure: cover, learning objectives, lead-in, knowledge blocks (2-5 slides each, concept first, then example, then exercise), recap, homework / further reading, closing slide. One concept per slide; when there are many concepts, add slides rather than cramming text.
3. Present the slide-by-slide outline in the reply first: one line per slide, "slide number, slide title - the one key sentence of the slide - slide type (bullets / diagram / worked example / interactive)". Wait for the user to confirm or edit. Do not start building until the outline is confirmed.
4. Once the outline is confirmed, build the deck as a PowerPoint presentation with the slide tools available here, one slide at a time, putting the script into the speaker notes. Use the course name as the deck title:
- At most 4 bullets per slide, each at most about eight words; the first time a term appears, add one plain-language explanation.
- Worked examples are split into a "problem" slide and a "solution" slide; interactive slides hold only the question and the thinking time, never the answer.
- Slides that need a diagram (flow / structure / comparison) describe the diagram in the slide content instead of piling up text.
- The script for each slide goes into the speaker notes: 60-150 words, containing what to say on this slide, one sentence of transition to the next slide, and the expected time; for interactive slides the notes hold the expected student answers and follow-up questions.
5. Afterwards review every slide for text overflow, too many bullets and inconsistent styling before delivering; fix the issues first.
## Rules
- The slides are for students, the script is for the teacher; they do not repeat each other. Slides carry conclusions and keywords, the script carries explanations and examples.
- Never paste paragraphs of the handout onto a slide; any sentence longer than two lines must be rewritten as a bullet.
- The objectives slide and the recap slide map one to one; the recap answers each objective in turn.
- Never three text-only slides in a row; the third slide must switch to a diagram, a worked example or an interactive slide.
## Output
- Outline: in the reply, one line per slide as "slide number, slide title - key sentence - slide type"; the last line gives the total slide count and the estimated duration.
- Deck: the cover holds the course name plus placeholders for presenter and date; the objectives and recap slides have the same number of items; each knowledge block opens with a section-title slide.
- Speaker notes are written in first-person spoken style ("Let's look at..."), and every note ends with "about N minutes".
- The reply body only states how the slide count matches the duration and suggests adjustments; it does not restate slide content.
After delivering, say in a sentence or two how the slide count matches the session length, and point out one or two places where an interactive slide or a split would help.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice