Audience-centered presentation design framework covering planning, visual strategy, cognitive load, and evaluation.
Works with
Provides assertion-evidence structure to replace bullet points with clear claims supported by visual evidence, reducing cognitive overload
Includes four evaluation phases: audience and content planning, visual strategy, cognitive load management, and structure patterns with scoring rubrics
Covers five common anti-patterns (data dumps, script reading, template traps, ani
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpresentation-designExecute the skills CLI command in your project's root directory to begin installation:
Fetches presentation-design from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate presentation-design. Access via /presentation-design in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
46
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
46
stars
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).
Audience-centered design. Every decision should serve audience understanding, not presenter convenience.
| 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 |
Replace bullet points with:
Instead of:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
Use:
"User engagement increased 43% after redesign"
[Graph showing the increase]
Each slide should answer: "What's the ONE thing I want them to take from this?"
Reveal information sequentially instead of all at once:
| Show on Slide | Speak Aloud |
|---|---|
| Key assertion | Elaboration |
| Visual evidence | Context and explanation |
| Critical data | Interpretation |
| Next step | Why it matters |
Horizontal slides: Main narrative flow Vertical slides: Supporting details (optional deep dives)
Example:
Mark content as:
| Criterion | Score | Notes |
|---|---|---|
| Content matches audience knowledge level | ||
| Clear value proposition for audience | ||
| Adaptable to time constraints | ||
| Navigation structure aids understanding |
Red Flags:
| Criterion | Score | Notes |
|---|---|---|
| Assertion-evidence structure used | ||
| Visual elements balance text | ||
| Visual hierarchy guides attention | ||
| Consistent design elements | ||
| Thoughtful whitespace |
Red Flags:
| 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:
| Criterion | Score | Notes |
|---|---|---|
| Works across display sizes | ||
| Sufficient color contrast | ||
| Inclusive imagery and language | ||
| Font sizes appropriate |
Red Flags:
After evaluation:
1. Critical Issues (Fix immediately):
2. Important Enhancements (Second priority):
3. Nice-to-Have Refinements:
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.
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.
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.
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.
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.
| 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 |
| Skill | What this provides |
|---|---|
| (implementation) | Design principles for any presentation tool |
| (delivery) | Slides designed to support effective speaking |
| 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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jwynia/agent-skills
anthropics/claude-code
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
hyperb1iss/hyperskills
Solid pick for teams standardizing on skills: presentation-design is focused, and the summary matches what you get after install.
I recommend presentation-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for presentation-design matched our evaluation — installs cleanly and behaves as described in the markdown.
presentation-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in presentation-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: presentation-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
presentation-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
presentation-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
presentation-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: presentation-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 27