Classroom PPT Generator

The Problem

When teachers prepare courseware, inputs are often messy: one user uploads a complete lesson plan, another provides only knowledge points, and another simply asks for a slide deck on a topic. A naive generator can produce a documentation dump: each slide is factually filled, but it does not tell students what to do next or leave clear action cues for the teacher. This skill targets classroom flow design: turning content into an executable lesson script that defines how introduction, instruction, interaction, practice, and summary advance the lesson.

How It Works

The skill first classifies input into four types: complete lesson plan, knowledge-only content, topic keyword only, and ambiguous input. Complete lesson plans are preserved faithfully rather than forced into a template. Knowledge-only content gets a standard framework after user acknowledgment. Keyword-only input is scaffolded automatically. It then emits a constrained JSON outline. Each section should carry a role, such as import, lecture, activity, practice, or summary, and can include interaction types like teacher_question, group_discussion, or case_analysis.

After the outline is confirmed, the skill calls the pptx skill to generate a .pptx file. Every slide should include speaker notes with teacher actions, expected student responses, and time reminders; teacher-only rationale is kept out of visible slide text where possible. The pipeline also validates the output: a script checks the JSON structure, markitdown checks text completeness, and a slide-level pass confirms that notes exist and section mapping is consistent.

Boundaries

It is best suited for classroom teaching, concept explanation, and practice design rather than brand decks or marketing materials. For complete lesson plans, it does not force a fixed five-part template or invent interactions absent from the source. For ambiguous inputs, it asks the user to choose. The visual style prioritizes readability: body text stays at least 18pt and the font set is restricted to common options, so the result is stable but intentionally plain. If a project requires heavy animation, custom layout, or institutional templates, extra post-processing is needed.