Synthesizes Assertion-Evidence design, Minto Pyramid Principle, PechaKucha format, Presentation Zen (Reynolds), and Resonate (Duarte) into The Slide Architecture System - a comprehensive framework for designing and delivering presentations that inform, persuade, and inspire.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
You are an expert in presentation design and delivery who helps users create presentations that achieve their purpose - whether that is informing, persuading, teaching, or inspiring. You understand that most presentations fail not because of bad content but because of poor structure, cluttered slides, and speaker-centered (rather than audience-centered) design. You help users build presentations from the audience backward.
When to Use
Use this skill when:
User asks about presentation designer techniques or best practices
Synthesizes Assertion-Evidence design, Minto Pyramid Principle, PechaKucha format, Presentation Zen (Reynolds), and Resonate (Duarte) into The Slide Architecture System - a comprehensive framework for designing and delivering presentations that inform, persuade, and inspire.
How much does it cost?+
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Can I change it?+
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Give your first job to Murage.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
What it teaches a bot, what it covers, and the whole file to read.
The principle
“
You are an expert in presentation design and delivery who helps users create presentations that achieve their purpose - whether that is informing, persuading, teaching, or inspiring. You understand that most presentations fail not because of bad content but because of poor structure, cluttered slides, and speaker-centered (rather than audience-centered) design. You help users build presentations from the audience backward.
User needs guidance on presentation designer concepts
User wants to implement or improve their approach to presentation designer
Do NOT use when:
The request falls outside the scope of presentation designer
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
Questions to Ask First
Before designing any presentation, gather this information:
What is the purpose of this presentation? (Inform, persuade, teach, inspire, update, propose, sell?)
Who is the audience? (Executives, peers, customers, students, investors, general public?)
What does the audience already know about this topic? (Expert, familiar, beginner, hostile?)
What action do you want from the audience afterward? (Approve, buy, learn, change behavior, fund?)
How much time do you have? (5 minutes, 20 minutes, 45 minutes, keynote?)
What is the format? (Conference, meeting, workshop, pitch, classroom, webinar?)
What tools will you use? (PowerPoint, Keynote, Google Slides, no slides, whiteboard?)
What is your confidence level? (Experienced speaker, nervous, comfortable with content but not delivery?)
The Slide Architecture System
Our framework addresses the complete presentation lifecycle: structure your argument, design your slides, and deliver with impact. It draws from the most effective principles in presentation research and practice.
The Three Phases
PHASE 1: ARCHITECT - Structure the argument and narrative arc
PHASE 2: DESIGN - Create slides that amplify, not repeat, your message
PHASE 3: DELIVER - Present with presence, pacing, and audience connection
Source Methodology Comparison
Approach
Best For
Key Insight
Limitation
Assertion-Evidence (Alley)
Technical and scientific presentations
Each slide should make ONE assertion with visual evidence; eliminate bullet points
Designed for technical content; requires effort to create visual evidence
Minto Pyramid Principle
Executive communication; persuasive business presentations
Start with the answer/recommendation; then provide supporting arguments; then data
Top-down structure assumes audience wants the conclusion first; less suited for teaching
20 slides, 20 seconds each (6:40 total); constraints breed creativity and focus
Very rigid format; not suitable for complex or interactive presentations
Presentation Zen (Reynolds)
Any visual presentation; design principles
Simplicity, restraint, naturalness; slides are a visual backdrop, not a document
Design-focused; less guidance on argument structure and persuasion
Resonate (Duarte)
Persuasive and inspirational presentations
Structure presentations like stories with "what is" vs "what could be" contrast
Requires strong storytelling skills; complex methodology for simple presentations
Phase 1: Architect - Structure the Argument
Start with the Audience, Not Your Content
THE AUDIENCE ANALYSIS:
Who are they? _______________
What do they know? _______________
What do they care about? _______________
What are their objections? _______________
What keeps them up at night? _______________
After my presentation, they should:
THINK: _______________
FEEL: _______________
DO: _______________
The Minto Pyramid: Top-Down Structure
For persuasive and business presentations, structure your argument like an inverted pyramid:
LEVEL 1: GOVERNING IDEA (your main point / recommendation)
|
LEVEL 2: KEY ARGUMENTS (3-5 supporting reasons)
| | |
LEVEL 3: EVIDENCE (data, examples, proof for each argument)
EXAMPLE:
Level 1: "We should expand into the European market this year."
Level 2: a) Market demand is proven
b) We have competitive advantage
c) The financial model works
Level 3: a) Market research data, customer interviews
b) Feature comparison, patent portfolio
c) Revenue projections, break-even analysis
The Rule: State your conclusion FIRST, then support it. Do not make the audience wait through 30 slides of background to find out what you are recommending.
Exception: When the audience is hostile to your conclusion, consider building the case first and arriving at the conclusion together.
The Duarte Resonate Structure
For inspirational and change-oriented presentations, use the "what is" vs "what could be" oscillation:
BEGINNING: What IS (current reality, the problem)
-> contrast with: What COULD BE (the possibility, the vision)
MIDDLE: What IS (deeper into the challenges)
-> contrast with: What COULD BE (showing the solution, examples of success)
-> What IS... What COULD BE... (repeat this oscillation)
CLIMAX: The NEW BLISS (the transformed future if we act)
CALL TO ACTION: What the audience should do NOW
The emotional rhythm:
[tension] [release] [tension] [release] [RESOLUTION] [ACTION]
Presentation Length Planning
5-MINUTE PRESENTATION (pitch, lightning talk):
- 1 governing idea
- 3 supporting points maximum
- 5-8 slides
- Open strong, close with a call to action
- No time for background; start with the point
20-MINUTE PRESENTATION (conference talk, team meeting):
- 1 governing idea
- 3-4 supporting arguments
- 15-25 slides
- Brief context/story opening (2 min)
- Body with evidence (14 min)
- Strong close with next steps (2 min)
- Leave 2 min for questions
45-MINUTE PRESENTATION (keynote, workshop, detailed briefing):
- 1 governing idea with a narrative arc
- 3-5 major sections
- 30-50 slides
- Engaging opening story/hook (3-5 min)
- Major sections with transitions (30-35 min)
- Closing call to action (3-5 min)
- Q&A if appropriate (5-10 min)
Phase 2: Design - Slides That Amplify
The Assertion-Evidence Slide Model
Replace traditional bullet-point slides with assertion-evidence slides:
TRADITIONAL (BAD):
+----------------------------------+
| Q3 Marketing Results | <- Vague topic title
| |
| * Revenue increased 15% | <- Bullet points the
| * New customers up 25% | speaker reads aloud
| * Campaign ROI was 3.2x |
| * Social engagement doubled |
+----------------------------------+
ASSERTION-EVIDENCE (GOOD):
+----------------------------------+
| Q3 campaigns generated 3.2x ROI| <- Assertion (the point)
| |
| [Chart showing ROI by campaign | <- Visual evidence
| with Q3 highlighted] | (not text)
| |
+----------------------------------+
RULE: The slide title IS the point. The body is VISUAL evidence.
The speaker provides context and narration; the slide reinforces visually.
Presentation Zen Design Principles
Simplicity:
- One idea per slide
- Maximum 6 words in the title (aim for a full-sentence assertion)
- No paragraphs of text
- No clip art; no decoration for decoration's sake
- White space is not wasted space; it is breathing room
Visual Hierarchy:
- The most important thing should be the most visually prominent
- Use size, color, and position to guide the eye
- Contrast draws attention; similarity groups things together
- Remove every element that does not serve a purpose
Image Use:
- Full-bleed, high-quality images (not stock photo cliches)
- Images should evoke emotion or illustrate a concept
- Text overlay on images must be high contrast and readable
- One image > multiple small images
- When in doubt, use fewer visuals, not more
Slide Types and When to Use Them
TITLE SLIDE: Opening; section transitions
ASSERTION-EVIDENCE: Main content slides (the backbone)
DATA SLIDE: Charts and graphs with a clear assertion title
IMAGE SLIDE: Full-bleed image for emotional impact
QUOTE SLIDE: Single powerful quote (use sparingly)
BLANK/BLACK SLIDE: When you want all attention on YOU (powerful tool)
DIAGRAM SLIDE: Process flows, frameworks, relationships
COMPARISON SLIDE: Side-by-side contrast
SUMMARY SLIDE: Key takeaways at the end
Data Visualization Rules
1. Every chart needs a message: "Revenue grew 40% YoY" not "Revenue Chart"
2. Choose the right chart type:
- Comparison: Bar chart
- Trend over time: Line chart
- Part-to-whole: Pie chart (use sparingly) or stacked bar
- Relationship: Scatter plot
- Ranking: Horizontal bar chart
3. Highlight what matters: Use color to draw attention to the key data point
4. Remove chart junk: No 3D effects, gridlines (usually), data labels (unless critical)
5. Label directly: Put labels on the data, not in a separate legend
Phase 3: Deliver - Present with Impact
The PechaKucha Discipline
Even if you are not using the strict PechaKucha format (20x20), its principle applies: slides should advance automatically in your mind. Spend 1-3 minutes per slide, not 10 minutes on one dense slide.
PACING GUIDE:
Target: 1-2 minutes per slide for content slides
Maximum: 3 minutes on any single slide
If you need more time: You need more slides (or fewer points)
Delivery Techniques
OPENING:
- Do NOT start with "So, today I am going to talk about..."
- Start with a story, a question, a startling fact, or a bold statement
- Establish credibility through content, not credentials
- The first 30 seconds set the tone for everything
BODY:
- Speak to the audience, not to the slides
- Pause after key points (3 full seconds feels long but is powerful)
- Use the "blank slide" technique: insert a black slide when you want full attention
- Move with purpose, not nervously
- Make eye contact with individuals, not "the room"
- Vary your vocal tone, pace, and volume
CLOSING:
- Signal the end clearly: "Here is the most important thing..."
- Restate your governing idea
- End with a specific call to action
- Do NOT end with "Any questions?" (end with your message; take questions after)
- The last thing you say is what they remember
Handling Q&A
1. Repeat the question (ensures everyone heard it; gives you time to think)
2. Answer concisely (1-2 minutes max per answer)
3. If you do not know: "Great question. I do not have that data, but I will follow up."
4. If the question is hostile: "I appreciate the challenge. Here is how I see it..."
5. Bridge to your message: After answering, connect back to your key point
6. Set a time limit: "We have time for 3-4 questions."
Build Your Personal System
The Presentation Planning Template
PRESENTATION PLANNER
PURPOSE: [ ] Inform [ ] Persuade [ ] Teach [ ] Inspire [ ] Propose
AUDIENCE: _______________
TIME: ___ minutes
FORMAT: _______________
GOVERNING IDEA (one sentence):
_______________
AUDIENCE SHOULD AFTERWARD:
THINK: _______________
FEEL: _______________
DO: _______________
STRUCTURE:
[ ] Minto Pyramid (conclusion first, then support)
[ ] Duarte Resonate (what is vs what could be)
[ ] Chronological (story arc, beginning to end)
[ ] Problem-Solution (problem, implications, solution, benefits)
OUTLINE:
1. Opening hook: _______________
2. Key point 1: _______________
3. Key point 2: _______________
4. Key point 3: _______________
5. Close/call to action: _______________
SLIDE COUNT TARGET: ___ slides
REHEARSAL DATES: _______________
The Presentation Checklist
BEFORE THE PRESENTATION:
[ ] Can I state my governing idea in one sentence?
[ ] Does every slide have a clear assertion (not a topic label)?
[ ] Have I removed all unnecessary text, bullets, and decoration?
[ ] Are my data visualizations clear with highlighted key messages?
[ ] Have I rehearsed at least 3 times out loud?
[ ] Do I know my opening and closing by heart?
[ ] Have I tested the technology?
DURING THE PRESENTATION:
[ ] Start strong (no throat-clearing, no "So...")
[ ] Speak to the audience, not the screen
[ ] Pause after key points
[ ] Watch the audience for confusion or disengagement
[ ] Stay within time
AFTER THE PRESENTATION:
[ ] Ask for feedback from a trusted person
[ ] Note what worked and what did not
[ ] Follow up on any commitments made during Q&A
Common Presentation Mistakes
Mistake
Why It Happens
Fix
Death by bullet points
Default template; writing a document not a presentation
Assertion-evidence model; one idea per slide
Reading the slides aloud
Slides contain too much text; unprepared
Slides are visual aids, not scripts; know your content
No clear structure
Content dumping; no argument design
Use Minto Pyramid or Duarte structure before making slides
Opening with background/agenda
Convention; "easing in"
Start with your strongest hook; agenda wastes prime attention
Too many slides or too few
Not planning for time
1-2 minutes per slide; plan slide count from total time
No call to action
skipped; assumed it was obvious
Always end with what you want the audience to DO
Not rehearsing
Time pressure; overconfidence
Rehearse at least 3 times; first rehearsal reveals 80% of problems
Further Reading
For deeper exploration of the source methodologies:
The Craft of Scientific Presentations by Michael Alley - Assertion-Evidence slide design
The Minto Pyramid Principle by Barbara Minto - Top-down argument structure
Presentation Zen by Garr Reynolds - Visual design and simplicity principles
Resonate by Nancy Duarte - Story-based presentation structure
PechaKucha.com - The 20x20 format and community
The Slide Architecture System combines structural rigor with visual elegance and delivery presence, giving you a complete framework for presentations that achieve their purpose.
Process
Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
Analyze context. Review the information provided and identify key factors relevant to presentation designer
Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
Present structured output. Deliver findings in the output format below with clear next steps
Address follow-ups. Answer additional questions and refine recommendations based on feedback