Presentation Deck
Outline stakeholder updates, design reviews, final showcases, and portfolio case studies with a six-beat story that gets alignment or approval.
Overview
presentation-deck is an agent skill most often used in Validate (also Ship, Launch) that structures design presentations—updates, reviews, showcases, and case studies—around Hook, Context, Journey, Solution, Evidence, an
Install
npx skills add https://github.com/owl-listener/designer-skills --skill presentation-deckWhat is this skill?
- Four presentation modes: stakeholder update, design review, final showcase, portfolio/case study—each with goal-driven s
- Universal six-beat arc: Hook, Context, Journey, Solution, Evidence, Ask
- Slide discipline: one idea per slide, progressive disclosure, show-don’t-tell, back-of-room legibility
- Design review flow: objectives, walkthrough, rationale, open questions, explicit feedback request
- Final showcase flow: problem, process, solution, evidence, impact, next steps for approval
- 6-step universal structure
- 4 presentation types with dedicated outlines
Adoption & trust: 817 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have strong design work but reviews stall because slides lack a clear story, rationale, and specific ask for stakeholders.
Who is it for?
Indie founders and solo designers presenting UX work to cofounders, clients, or investors with limited time and high skepticism.
Skip if: Automated slide pixel generation, brand-system creation, or engineering architecture decks with no design walkthrough.
When should I use this skill?
User needs to structure a design presentation for stakeholders, design review, final showcase, or portfolio/case study.
What do I get? / Deliverables
You leave with a mode-matched outline and slide principles so reviewers understand the problem, trust the process, and know what decision or feedback you need next.
- Mode-specific section outline
- Slide-level talking beats aligned to Hook–Ask
- Explicit feedback or approval ask
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate → prototype is the canonical shelf because the skill optimizes presentations that walk stakeholders through evolving design choices and open questions. Prototype subphase covers review-ready narratives before build lock-in—exactly when hook, journey, evidence, and asks must land.
Where it fits
Run a design review deck that surfaces open questions before you code the MVP shell.
Package rationale and evidence for final sign-off before release.
Showcase the shipped solution with impact metrics for launch allies and press.
Turn a shipped feature into a portfolio case study with challenge, approach, and learnings.
Frame early concept explorations so advisors see the problem hook before pixels.
How it compares
Use instead of dumping mockup PDFs when you need a persuasion structure tailored to stakeholder, review, showcase, or portfolio goals.
Common Questions / FAQ
Who is presentation-deck for?
Solo builders and designers who must communicate UX decisions clearly to non-designers in updates, critiques, approvals, or portfolio storytelling.
When should I use presentation-deck?
During Validate prototype reviews, Ship design sign-off, Launch showcase decks, and Grow portfolio case studies whenever the audience needs a guided narrative—not raw screens.
Is presentation-deck safe to install?
Check this page’s Security Audits panel for supply-chain and permission signals; the skill is narrative guidance only with no bundled executables.
SKILL.md
READMESKILL.md - Presentation Deck
# Presentation Deck You are an expert in structuring design presentations that communicate clearly and persuade effectively. ## What You Do You structure presentations that tell a compelling design story tailored to the audience. ## Presentation Types ### Stakeholder Update Goal: Inform and align. Structure: context recap, progress, key decisions, next steps, asks. ### Design Review Goal: Get feedback. Structure: objectives, design walkthrough, rationale, open questions, feedback request. ### Final Showcase Goal: Gain approval. Structure: problem, process, solution, evidence, impact, next steps. ### Portfolio/Case Study Goal: Demonstrate capability. Structure: challenge, approach, key decisions, outcome, learnings. ## Universal Structure 1. **Hook** — Why should the audience care? (problem, data, story) 2. **Context** — What do they need to know? (background, constraints) 3. **Journey** — How did you get here? (process, key moments) 4. **Solution** — What are you proposing? (the design, with rationale) 5. **Evidence** — Why is this right? (research, testing, data) 6. **Ask** — What do you need from them? (approval, feedback, resources) ## Slide Design Principles - One idea per slide - Show, don't tell (use visuals over text) - Use progressive disclosure (reveal complexity gradually) - Design for the back of the room (large text, high contrast) - Include speaker notes for context ## Audience Adaptation - **Executives**: Lead with impact, be concise, focus on business value - **Engineers**: Include technical details, interaction specs, edge cases - **Designers**: Show process, rationale, design system alignment - **Mixed**: Layer detail progressively, lead with the big picture ## Best Practices - Rehearse with a colleague before the real presentation - Prepare for questions (have backup slides) - Start with the audience's concerns, not yours - End with a clear ask or next step - Follow up with a summary document