
presentation-design
Design and evaluate presentations that communicate effectively. Use when designing a presentation, creating slides, getting presentation feedback, structuring a talk, or reviewing slides. Keywords: presentation, slides, talk, PowerPoint, Keynote, reveal.js.
- Installs
- 2.5K
- Last 24h
- +14
- Trending rank
- #7126
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jwynia/agent-skills --skill presentation-design- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads presentation-design automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Presentation Design Diagnostic
Purpose
Design and evaluate presentations that communicate effectively. Provides frameworks for planning, visual design, cognitive load management, and evaluation. Applicable to any presentation tool (reveal.js, PowerPoint, Keynote, Google Slides).
Core Principle
Audience-centered design. Every decision should serve audience understanding, not presenter convenience.
Quick Reference: Common Problems
| Problem | Symptom | Fix |
|---|---|---|
| Wall of Text | Slides are paragraphs | Assertion-evidence structure |
| Bullet Point Disease | Lists instead of visuals | One concept + visual evidence |
| Kitchen Sink | Everything included | Essential vs. expandable content |
| Pretty but Empty | Design without substance | Message-first design |
| Cognitive Overload | Too much per slide | One key concept per slide |
Phase 1: Audience & Content Planning
Key Questions
- Who specifically is my audience? What's their knowledge level?
- What's the ONE main message? What should they remember?
- What are 3-5 supporting points? How do they reinforce the message?
- What evidence supports each point? Visual, data, examples?
- What action should they take? What's the call to action?
- What are time constraints? What's essential vs. optional?
Actions
- Create audience persona(s)
- Write one-sentence main message
- Organize supporting points in logical flow
- Identify evidence for each point
- Define essential vs. expandable content
- Sketch presentation flow
Phase 2: Visual Strategy
Assertion-Evidence Structure
Replace bullet points with:
- Assertion: Clear, complete sentence stating the point
- Evidence: Visual that supports the assertion
Instead of:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
Use:
"User engagement increased 43% after redesign"
[Graph showing the increase]
Visual Principles
- Limited palette: 3-5 colors maximum
- Typography hierarchy: 2-3 fonts with clear roles
- Whitespace: Let content breathe
- Consistency: Same layouts, same treatment
- Visual progress: Help audience track where they are
Phase 3: Cognitive Load Management
One Concept Per Slide
Each slide should answer: "What's the ONE thing I want them to take from this?"
Progressive Disclosure
Reveal information sequentially instead of all at once:
- Show initial state
- Add first element with context
- Add second element building on first
Spoken vs. Shown
| Show on Slide | Speak Aloud |
|---|---|
| Key assertion | Elaboration |
| Visual evidence | Context and explanation |
| Critical data | Interpretation |
| Next step | Why it matters |
Code Examples (Technical Talks)
- Syntax highlighting always
- Highlight the critical line
- Build up complex examples
- Remove boilerplate when possible
Phase 4: Structure Patterns
Horizontal vs. Vertical (Multi-Level Navigation)
Horizontal slides: Main narrative flow Vertical slides: Supporting details (optional deep dives)
Example:
- Horizontal: "Three Key Factors in Customer Retention"
- Vertical (under that): Detailed slide for each factor
Time Flexibility
Mark content as:
- Essential: Must cover in any version
- Standard: Include with normal time
- Expandable: Include only with extra time
Evaluation Framework
1. Audience-Centered Design (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| Content matches audience knowledge level | ||
| Clear value proposition for audience | ||
| Adaptable to time constraints | ||
| Navigation structure aids understanding |
Red Flags:
- Presenter-focused rather than audience-focused
- No consideration of audience's existing knowledge
2. Visual Clarity (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| Assertion-evidence structure used | ||
| Visual elements balance text | ||
| Visual hierarchy guides attention | ||
| Consistent design elements | ||
| Thoughtful whitespace |
Red Flags:
- Bullet-point overuse
- Text-heavy slides
- Cluttered layouts
3. Cognitive Load (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| One key concept per slide | ||
| Appropriate text density | ||
| Judicious animations/transitions | ||
| Code properly formatted (if applicable) | ||
| Supporting details accessible, not distracting |
Red Flags:
- Multiple complex concepts per slide
- Excessive text competing with speech
- Animation overuse
4. Accessibility (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| Works across display sizes | ||
| Sufficient color contrast | ||
| Inclusive imagery and language | ||
| Font sizes appropriate |
Red Flags:
- Poor contrast
- Too-small fonts
- Non-inclusive content
Implementation Checklist
Structure
- Main message clear in first 2 minutes
- Supporting points organized logically
- Essential vs. expandable content marked
- Navigation aids understanding
Content
- Assertion-evidence structure used
- Visual evidence supports assertions
- One concept per slide
- Code examples properly formatted
Visual
- Consistent color palette
- Typography hierarchy
- Sufficient whitespace
- Elements aligned
Accessibility
- Color contrast verified
- Font sizes appropriate
- Alternative text for key images
Improvement Prioritization
After evaluation:
1. Critical Issues (Fix immediately):
- Blocks audience understanding
- Accessibility failures
- Core message unclear
2. Important Enhancements (Second priority):
- Cognitive load issues
- Visual consistency problems
- Structure improvements
3. Nice-to-Have Refinements:
- Advanced animations
- Custom styling
- Polish details
Anti-Patterns
1. The Data Dump
Pattern: Every slide full of data, charts, and statistics without interpretation or hierarchy. Why it fails: Audiences can't process raw data in real-time. Without interpretation, they're left doing analysis instead of learning. Most data is forgotten immediately. Fix: One insight per slide with visual evidence supporting the insight. State the conclusion; show the proof. The audience should understand your point before seeing the data.
2. The Script Reader
Pattern: Slides that contain the speaker's full script—bullet points that are really paragraphs. Why it fails: Audiences read faster than speakers talk. They read ahead, then tune out when you say what they already read. The slides become teleprompter, not communication tool. Fix: Slides show what you can't say; you say what you can't show. Visuals, diagrams, and key assertions on screen. Context, explanation, and elaboration spoken.
3. The Template Trap
Pattern: Dropping content into a generic template without considering how the design serves the message. Why it fails: Design should support comprehension, not just look professional. Generic templates create generic communication. One-size-fits-all fits no one well. Fix: Design serves message. Ask: what visual structure helps this specific audience understand this specific content? Start from communication need, not template options.
4. The Animation Circus
Pattern: Transitions, builds, and effects everywhere—flying text, spinning images, fade after fade. Why it fails: Animation is attention. Every effect says "look at this." When everything animates, nothing stands out. Audiences become overwhelmed or numbed. Fix: Animation only for progressive disclosure (building complex ideas step by step) or emphasis (highlighting the key point). Default to no animation; add only with purpose.
5. The Bullet Point Disease
Pattern: Slide after slide of bullet point lists—the default structure for everything. Why it fails: Bullet points are for documents, not presentations. They encourage equal weight for unequal ideas, text-heavy slides, and passive reading instead of active viewing. Fix: Use assertion-evidence structure. Replace bullet lists with clear assertions supported by visual evidence. If you need a list, question whether it needs to be a slide.
Integration
Inbound (feeds into this skill)
| Skill | What it provides |
|---|---|
| speech-adaptation | Spoken content structure to coordinate with visuals |
| story-sense | Narrative structure for presentation flow |
| (content expertise) | Subject matter to communicate |
Outbound (this skill enables)
| Skill | What this provides |
|---|---|
| (implementation) | Design principles for any presentation tool |
| (delivery) | Slides designed to support effective speaking |
Complementary
| Skill | Relationship |
|---|---|
| speech-adaptation | Presentation-design handles visuals; speech-adaptation handles spoken content. Design together for coordination |
| voice-analysis | Understanding the presenter's voice helps design slides that match their natural delivery style |
FAQ
What does the presentation-design skill do?
Design and evaluate presentations that communicate effectively. Use when designing a presentation, creating slides, getting presentation feedback, structuring a talk, or reviewing slides. Keywords: presentation, slides, talk, PowerPoint, Keynote, reveal.js.
How do I install presentation-design?
Run npx skills add https://github.com/jwynia/agent-skills --skill presentation-design in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/presentation-design/ (personal) or .claude/skills/presentation-design/ (project).
Which AI agents can use presentation-design?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is presentation-design safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains presentation-design?
It is published by jwynia in jwynia/agent-skills. It has 2,539 recorded installs.
More from jwynia/agent-skills
frontend-design
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality. Provides analysis tools for auditing existing designs and generation tools for creating color palettes, typography systems, design tokens, and component templates. Supports React, Vue, Svelte, and vanilla HTML/CSS. Use when building web components, pages, or applications. Keywords: design, UI, frontend, CSS, components, palette, typography, tokens, accessibility.
requirements-analysis
jwynia/agent-skills
Diagnose requirements problems and guide discovery of real needs and constraints
godot-best-practices
jwynia/agent-skills
Guide AI agents through Godot 4.x GDScript coding best practices including scene organization, signals, resources, state machines, and performance optimization. This skill should be used when generating GDScript code, creating Godot scenes, designing game architecture, implementing state machines, object pooling, save/load systems, or when the user asks about Godot patterns, node structure, or GDScript standards. Keywords: godot, gdscript, game development, signals, resources, scenes, nodes, state machine, object pooling, save system, autoload, export, type hints.
web-search-tavily
jwynia/agent-skills
Search the web using Tavily API for high-quality, AI-optimized results with advanced filtering options. Use when you need structured search results, domain filtering, relevance scores, or AI-generated answer summaries. Requires TAVILYAPIKEY. Keywords: tavily, advanced search, filtered search, domain filtering, relevance scoring.
godot-asset-generator
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot. Covers the full art pipeline from concept art and style guides to final sprites, sprite sheets, and import configuration. This skill should be used when creating game art, generating sprites, making tilesets, creating UI elements, or preparing assets for Godot import. Keywords: game assets, AI art, DALL-E, Replicate, fal.ai, sprite sheet, tileset, Godot, pixel art, character sprite, game art, texture, animation frames.
document-to-narration
jwynia/agent-skills
Convert written documents to narrated video scripts with TTS audio and word-level timing. Use when preparing essays, blog posts, or articles for video narration. Outputs scene files, audio, and VTT with precise word timestamps. Keywords: narration, voiceover, TTS, scenes, audio, timing, video script, spoken.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.