AI Skill Report Card
Building Presentations With Prompts
Quick Start13 / 15
Given a topic, run this minimal sequence to produce a full deck outline + content in one pass:
- Blueprint — define goal, audience, message, structure, slide count.
- Slide-by-slide structure — title + purpose per slide.
- Content generation — bullets per slide.
- Opening hook — 3 options for slide 1.
- Executive summary slide — for the close or a leave-behind.
Example invocation: "Create a presentation on [topic] for [audience]" → produce all five outputs above in one response, clearly labeled by slide number.
Recommendation▾
Example 2 lacks a concrete filled-in output (no actual paragraph/bullets shown) — replace with a real before/after text pair to make it truly concrete.
Workflow14 / 15
Progress:
- Step 1: Clarify topic, audience, and goal (ask only if genuinely ambiguous; otherwise infer sensible defaults)
- Step 2: Build the Complete Presentation Blueprint (goal, audience, main message, slide order, slide count)
- Step 3: Architect slide-by-slide structure (title + what each slide shows)
- Step 4: Apply story structure if the topic benefits from narrative (hook → problem → insight → solution → takeaway)
- Step 5: Generate full slide content (short bullets, one idea per slide)
- Step 6: Suggest visual direction per slide (layout, chart type, icon, diagram)
- Step 7: If data is provided, recommend chart types and explain what each shows
- Step 8: Write speaker notes (talking points, not slide text)
- Step 9: Draft 3 opening hooks (question, surprising fact, short story)
- Step 10: Produce one-slide executive summary (main message + 3-4 insights + takeaway)
Not every step is needed every time — match depth to the request. A quick ask gets Steps 2-5; a full deck request gets all 10.
Recommendation▾
Add a bad-vs-good example (e.g., a bloated text-heavy slide vs. corrected version) to more clearly demonstrate contrast and reinforce pitfalls.
Prompt Library (use as internal reasoning templates)
- Blueprint: Define goal, target audience, main message, slide order, total slide count.
- Structure Architect: Slide title + description of what it shows, ensuring smooth flow.
- Story Builder: hook → problem → insight → solution → takeaway.
- Visual Direction: layouts, charts, diagrams, icons per slide — modern and clean.
- Content Generator: short, presentation-ready bullets per slide, audience-aware.
- Simplification Editor: cut text, isolate one idea per slide, sharpen clarity.
- Data & Chart Builder: pick chart type per insight, explain why it clarifies the data.
- Executive Summary: one slide, main message + 3-4 insights + one takeaway.
- Speaker Notes: talking points that expand on sparse slide text.
- Opening Hook: 3 hooks — question, surprising fact, short story.
Examples13 / 20
Example 1: Input: "Create a presentation on remote work productivity for a team of 8 slides." Output:
- Blueprint: Goal = persuade leadership to adopt hybrid policy; Audience = executives; Main message = "Flexibility increases output without sacrificing culture"; 8 slides.
- Slide list: 1) Hook 2) Problem 3) Data insight 4) Root causes 5) Proposed model 6) Case study 7) Implementation plan 8) Executive summary/takeaway.
- Bullets for each slide (3-4 max, no paragraphs).
- Visual suggestion per slide (e.g., Slide 3: bar chart comparing output pre/post hybrid).
- 3 opening hooks for Slide 1.
Example 2: Input: "Rewrite this dense paragraph into slide bullets: [long paragraph]." Output: 3-4 bullets, each ≤12 words, one core idea per bullet, no jargon left unexplained, headline phrase as slide title.
Recommendation▾
The Prompt Library section overlaps significantly with the Workflow steps — consider merging to reduce redundancy and tighten the skill further.
Best Practices
- One idea per slide — never stack multiple concepts on one slide.
- Bullets ≤ 12 words; no full sentences or paragraphs on slides.
- Match tone/depth to audience (executives want summary + takeaway, not raw data).
- Always separate slide content (what's shown) from speaker notes (what's said).
- Default to story structure (hook → problem → insight → solution → takeaway) unless the topic is purely informational/reference.
- Recommend specific chart types tied to the insight they reveal (trend → line, comparison → bar, composition → pie/stacked bar), not generic "add a chart."
- Keep total slide count proportional to talk length (~1-2 minutes per slide as a rule of thumb).
Common Pitfalls
- Don't generate walls of text for slides — that's a document, not a deck.
- Don't skip the audience/goal step — content without a clear message drifts.
- Don't put speaker notes and slide bullets in the same block — label them separately.
- Don't suggest charts without explaining what insight they surface.
- Don't default to a story arc for content that's purely reference/technical (e.g., API specs) — plain structured sections work better there.