Baoyu Slide Deck
Structure pitch, launch, and content presentations with a message hierarchy and audience matrix before you design slides.
Overview
baoyu-slide-deck is an agent skill most often used in Launch (also Validate and Grow) that analyzes audience and message hierarchy before effective slide deck creation.
Install
npx skills add https://github.com/jimliu/baoyu-skills --skill baoyu-slide-deckWhat is this skill?
- Core message exercise capped at one sentence and ≤15 words before any slide layout
- 3–5 maximum supporting points prioritized by audience relevance, not source order
- Explicit call-to-action placement tied to what the audience should do after viewing
- Audience decision matrix with five analysis questions plus executive, technical, and general adaptation rows
- Message hierarchy separates takeaway, evidence, and CTA so agents do not dump source material onto slides
- Core message stated in ≤15 words
Adoption & trust: 23.3k installs on skills.sh; 20.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have raw notes or a long doc but no single takeaway, prioritized proof, or audience-specific framing for a deck that has to persuade someone.
Who is it for?
Solo builders drafting investor pitches, launch announcements, or webinar decks who need narrative structure before pixels.
Skip if: Teams that already have an approved deck template and only need automatic slide generation with no messaging work.
When should I use this skill?
Before creating or redesigning a slide deck when you need message hierarchy, audience fit, and a clear call-to-action.
What do I get? / Deliverables
You get a defined core message, capped supporting points, CTA placement, and an audience decision matrix you can hand to slide layout or export as a deck brief.
- Core message and supporting-points hierarchy
- Completed audience decision matrix
- Audience-adapted content focus notes for slide outline
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Slide decks are most often built when you are ready to show the product or story to the world—pitches, launch narratives, and distribution-facing talks map cleanly to Launch. Distribution is where solo builders turn ideas into decks investors, customers, and communities actually see; this framework front-loads clarity before visual design.
Where it fits
Map investor objections and proof types before building a fundraising deck outline.
Lock one launch takeaway and CTA before slides for a product hunt or demo day.
Adapt a technical deep dive into executive-friendly highlights for a webinar deck.
Prioritize roadmap themes into three to five slides for a stakeholder review.
How it compares
Use as a structured briefing pass before design tools or generic “make me slides” prompts that skip audience and message hierarchy.
Common Questions / FAQ
Who is baoyu-slide-deck for?
Solo and indie builders using Claude Code, Cursor, or similar agents who create pitch decks, launch presentations, or content slides and want analysis before design.
When should I use baoyu-slide-deck?
At Validate when scoping a pitch to investors; at Launch when shaping distribution and demo narratives; at Grow when planning webinar or content decks; and at Build when presenting roadmaps to stakeholders.
Is baoyu-slide-deck safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and your agent’s filesystem permissions before running it on sensitive draft materials.
SKILL.md
READMESKILL.md - Baoyu Slide Deck
# Presentation Analysis Framework Deep content analysis for effective slide deck creation. ## 1. Message Hierarchy Identify the core message structure before designing slides. ### Core Message (One Sentence) - What is the single most important takeaway? - If the audience remembers only one thing, what should it be? - Can you state it in ≤15 words? ### Supporting Points (3-5 Maximum) - What evidence supports the core message? - What sub-topics must be covered? - Prioritize by audience relevance, not source order ### Call-to-Action - What should the audience DO after viewing? - Is it clear, specific, and achievable? - Where does it appear (slide position)? ## 2. Audience Decision Matrix | Question | Analysis | |----------|----------| | Who is the primary audience? | [Role, expertise level, relationship to topic] | | What do they currently believe? | [Existing knowledge, assumptions, biases] | | What decision do we want them to make? | [Specific action or conclusion] | | What barriers exist? | [Objections, concerns, missing information] | | What evidence will convince them? | [Data types, credibility sources, emotional hooks] | ### Audience Adaptation | Audience Type | Content Focus | Visual Treatment | |---------------|---------------|------------------| | Executives | Outcomes, ROI, strategic impact | High-level, clean, data highlights | | Technical | Architecture, implementation, specs | Detailed diagrams, code, schematics | | General | Benefits, stories, relatability | Visual metaphors, simple charts | | Investors | Market size, traction, team | Growth charts, milestones, comparisons | | Learners | Step-by-step, examples, practice | Progressive reveals, exercises | ## 3. Visual Opportunity Map Identify which content benefits from visualization. ### Content-to-Visual Mapping | Content Type | Visual Treatment | Example | |--------------|------------------|---------| | Comparisons | Side-by-side, before/after | Feature comparison table | | Processes | Flow diagrams, numbered steps | Workflow illustration | | Hierarchies | Org charts, pyramids, trees | Organizational structure | | Timelines | Horizontal/vertical timelines | Project milestones | | Statistics | Charts, highlighted numbers | Key metrics with context | | Concepts | Icons, metaphors, illustrations | Abstract idea visualization | | Relationships | Venn diagrams, networks | Ecosystem or dependencies | | Lists | Structured grids, icon rows | Feature bullets with icons | ### Visual Priority Rate each piece of content: - **Must Visualize**: Complex data, key differentiators, memorable moments - **Should Visualize**: Supporting evidence, secondary points - **Text Only**: Simple statements, transitions, minor details ## 4. Presentation Flow Structure for impact and retention. ### Opening (First 2-3 Slides) | Element | Purpose | |---------|---------| | Hook | Capture attention (surprising stat, question, story) | | Context | Why this matters now | | Preview | What audience will learn/gain | ### Middle (Content Slides) | Pattern | When to Use | |---------|-------------| | Problem → Solution | Introducing new products/ideas | | Situation → Complication → Resolution | Complex business cases | | What → Why → How | Educational content | | Past → Present → Future | Transformation stories | | Claim → Evidence → Implication | Data-driven arguments | ### Closing (Final 2-3 Slides) | Element | Purpose | |---------|---------| | Synthesis | Tie back to core message | | Call-to-Action | Clear next steps | | Memorable Close | Resonant quote, image, or statement | ### Transitions - Each slide should answer: "What comes next?" - Use narrative connectors between sections - Build logical progression, not topic jumps ## 5. Content Adaptation Decide what to keep, transform, or omit. ### Keep (High Value) - Core arguments and evidence - Unique insights or data - Audience-relevant examples - Memorable quotes or statistics ### Simplify (Medium Value) - Technical detail