baoyu-slide-deck

jimliu/baoyu-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jimliu/baoyu-skills --skill baoyu-slide-deck
0 commentsdiscussion
summary

Transform content into professional slide deck images with customizable styles and audience targeting.

  • Generates slide outlines with style instructions, then creates individual slide images in 10+ preset styles (blueprint, corporate, sketch-notes, minimal, etc.) or custom dimension combinations
  • Supports audience targeting (beginners, executives, experts), language selection, and configurable slide counts (5-30 slides based on content length)
  • Includes two-round confirmation workflow w
skill.md

Slide Deck Generator

Transform content into professional slide deck images.

Usage

/baoyu-slide-deck path/to/content.md
/baoyu-slide-deck path/to/content.md --style sketch-notes
/baoyu-slide-deck path/to/content.md --audience executives
/baoyu-slide-deck path/to/content.md --lang zh
/baoyu-slide-deck path/to/content.md --slides 10
/baoyu-slide-deck path/to/content.md --outline-only
/baoyu-slide-deck  # Then paste content

Script Directory

Agent Execution Instructions:

  1. Determine this SKILL.md file's directory path as {baseDir}
  2. Script path = {baseDir}/scripts/<script-name>.ts
  3. Resolve ${BUN_X} runtime: if bun installed → bun; if npx available → npx -y bun; else suggest installing bun
Script Purpose
scripts/merge-to-pptx.ts Merge slides into PowerPoint
scripts/merge-to-pdf.ts Merge slides into PDF

Options

Option Description
--style <name> Visual style: preset name, custom, or custom style name
--audience <type> Target: beginners, intermediate, experts, executives, general
--lang <code> Output language (en, zh, ja, etc.)
--slides <number> Target slide count (8-25 recommended, max 30)
--outline-only Generate outline only, skip image generation
--prompts-only Generate outline + prompts, skip images
--images-only Generate images from existing prompts directory
--regenerate <N> Regenerate specific slide(s): --regenerate 3 or --regenerate 2,5,8

Slide Count by Content Length:

Content Slides
< 1000 words 5-10
1000-3000 words 10-18
3000-5000 words 15-25
> 5000 words 20-30 (consider splitting)

Style System

Presets

Preset Dimensions Best For
blueprint (Default) grid + cool + technical + balanced Architecture, system design
chalkboard organic + warm + handwritten + balanced Education, tutorials
corporate clean + professional + geometric + balanced Investor decks, proposals
minimal clean + neutral + geometric + minimal Executive briefings
sketch-notes organic + warm + handwritten + balanced Educational, tutorials
watercolor organic + warm + humanist + minimal Lifestyle, wellness
dark-atmospheric clean + dark + editorial + balanced Entertainment, gaming
notion clean + neutral + geometric + dense Product demos, SaaS
bold-editorial clean + vibrant + editorial + balanced Product launches, keynotes
editorial-infographic clean + cool + editorial + dense Tech explainers, research
fantasy-animation organic + vibrant + handwritten + minimal Educational storytelling
intuition-machine clean + cool + technical + dense Technical docs, academic
pixel-art pixel + vibrant + technical + balanced Gaming, developer talks
scientific clean + cool + technical + dense Biology, chemistry, medical
vector-illustration clean + vibrant + humanist + balanced Creative, children's content
vintage paper + warm + editorial + balanced Historical, heritage

Style Dimensions

Dimension Options Description
Texture clean, grid, organic, pixel, paper Visual texture and background treatment
Mood professional, warm, cool, vibrant, dark, neutral Color temperature and palette style
Typography geometric, humanist, handwritten, editorial, technical Headline and body text styling
Density minimal, balanced, dense Information density per slide

Full specs: references/dimensions/*.md

Auto Style Selection

Content Signals Preset
tutorial, learn, education, guide, beginner sketch-notes
classroom, teaching, school, chalkboard chalkboard
architecture, system, data, analysis, technical blueprint
creative, children, kids, cute vector-illustration
briefing, academic, research, bilingual intuition-machine
executive, minimal, clean, simple minimal
saas, product, dashboard, metrics notion
investor, quarterly, business, corporate corporate
launch, marketing, keynote, magazine bold-editorial
entertainment, music, gaming, atmospheric dark-atmospheric
explainer, journalism, science communication editorial-infographic
story, fantasy, animation, magical fantasy-animation
gaming, retro, pixel, developer pixel-art
biology, chemistry, medical, scientific scientific
history, heritage, vintage, expedition vintage
lifestyle, wellness, travel, artistic watercolor
Default blueprint

Design Philosophy

Decks designed for reading and sharing, not live presentation:

  • Each slide self-explanatory without verbal commentary
  • Logical flow when scrolling
  • All necessary context within each slide
  • Optimized for social media sharing

See references/design-guidelines.md for:

  • Audience-specific principles
  • Visual hierarchy
  • Content density guidelines
  • Color and typography selection
  • Font recommendations

See references/layouts.md for layout options.

File Management

Output Directory

slide-deck/{topic-slug}/
├── source-{slug}.{ext}
├── outline.md
├── prompts/
│   └── 01-slide-cover.md, 02-slide-{slug}.md, ...
├── 01-slide-cover.png, 02-slide-{slug}.png, ...
├── {topic-slug}.pptx
└── {topic-slug}.pdf

Slug: Extract topic (2-4 words, kebab-case). Example: "Introduction to Machine Learning" → intro-machine-learning

Conflict Handling: See Step 1.3 for existing content detection and user options.

Language Handling

Detection Priority:

  1. --lang flag (explicit)
  2. EXTEND.md language setting
  3. User's conversation language (input language)
  4. Source content language

Rule: ALL responses use user's preferred language:

  • Questions and confirmations
  • Progress reports
  • Error messages
  • Completion summaries

Technical terms (style names, file paths, code) remain in English.

Workflow

Copy this checklist and check off items as you complete them:

Slide Deck Progress:
- [ ] Step 1: Setup & Analyze
  - [ ] 1.1 Load preferences
  - [ ] 1.2 Analyze content
  - [ ] 1.3 Check existing ⚠️ REQUIRED
- [ ] Step 2: Confirmation ⚠️ REQUIRED (Round 1, optional Round 2)
- [ ] Step 3: Generate outline
- [ ] Step 4: Review outline (conditional)
- [ ] Step 5: Generate prompts
- [ ] Step 6: Review prompts (conditional)
- [ ] Step 7: Generate images
- [ ] Step 8: Merge to PPTX/PDF
- [ ] Step 9: Output summary

Flow

Input → Preferences → Analyze → [Check Existing?] → Confirm (1-2 rounds) → Outline → [Review Outline?] → Prompts → [Review Prompts?] → Images → Merge → Complete

Step 1: Setup & Analyze

1.1 Load Preferences (EXTEND.md)

Check EXTEND.md existence (priority order):

# macOS, Linux, WSL, Git Bash
test -f .baoyu-skills/baoyu-slide-deck/EXTEND.md && echo "project"
test -f "${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-slide-deck/EXTEND.md" && echo "xdg"
test -f "$HOME/.baoyu-skills/baoyu-slide-deck/EXTEND.md" && echo "user"
# PowerShell (Windows)
if (Test-Path .baoyu-skills/baoyu-slide-deck/EXTEND.md) { "project" }
$xdg = if ($env:XDG_CONFIG_HOME) { $env:XDG_CONFIG_HOME } else { "$HOME/.config" }
if (Test-Path "$xdg/baoyu-skills/baoyu-slide-deck/EXTEND.md") { "xdg" }
if (Test-Path "$HOME/.baoyu-skills/baoyu-slide-deck/EXTEND.md") { "user" }

┌──────────────────────────────────────────────────┬───────────────────┐ │ Path │ Location │ ├──────────────────────────────────────────────────┼───────────────────┤ │ .baoyu-skills/baoyu-slide-deck/EXTEND.md │ Project directory │ ├──────────────────────────────────────────────────┼───────────────────┤ │ $HOME/.baoyu-skills/baoyu-slide-deck/EXTEND.md │ User home │ └──────────────────────────────────────────────────┴───────────────────┘

When EXTEND.md Found → Read, parse, output summary to user:

📋 Loaded preferences from [full path]
├─ Style: [preset/custom name]
├─ Audience: [audience or "auto-detect"]
├─ Language: [language or "auto-detect"]
└─ Review: [enabled/disabled]

When EXTEND.md Not Found → First-time setup using AskUserQuestion or proceed with defaults.

EXTEND.md Supports: Preferred style | Custom dimensions | Default audience | Language preference | Review preference

Schema: references/config/preferences-schema.md

1.2 Analyze Content

  1. Save source content (if pasted, save as source.md)
    • Backup rule: If source.md exists, rename to source-backup-YYYYMMDD-HHMMSS.md
  2. Follow references/analysis-framework.md for content analysis
  3. Analyze content signals for style recommendations
  4. Detect source language
  5. Determine recommended slide count
  6. Generate topic slug from content

1.3 Check Existing Content ⚠️ REQUIRED

MUST execute before proceeding to Step 2.

Use Bash to check if output directory exists:

test -d "slide-deck/{topic-slug}" && echo "exists"

If directory exists, use AskUserQuestion:

header: "Existing"
question: "Existing content found. How to proceed?"
options:
  - label: "Regenerate outline"
    description: "Keep images, regenerate outline only"
  - label: "Regenerate images"
    description: "Keep outline, regenerate images only"
  - label: "Backup and regenerate"
    description: "Backup to {slug}-backup-{timestamp}, then regenerate all"
  - label: "Exit"
    description: "Cancel, keep existing content unchanged"

Save to analysis.md with:

  • Topic, audience, content signals
  • Recommended style (based on Auto Style Selection)
  • Recommended slide count
  • Language detection

Step 2: Confirmation ⚠️ REQUIRED

Two-round confirmation: Round 1 always, Round 2 only if "Custom dimensions" selected.

Language: Use user's input language or saved language preference.

Display summary:

  • Content type + topic identified
  • Language: [from EXTEND.md or detected]
  • Recommended style: [preset] (based on content signals)
  • Recommended slides: [N] (based on content length)

Round 1 (Always)

Use AskUserQuestion for all 5 questions:

Question 1: Style

header: "Style"
question: "Which visual style for this deck?"
options:
  - label: "{recommended_preset} (Recommended)"
    description: "Best match based on content analysis"
  - label: "{alternative_preset}"
    description: "[alternative style description]"
  - label: "Custom dimensions"
    description: "Choose texture, mood, typography, density separately"

Question 2: Audience

header: "Audience"
question: "Who is the primary reader?"
options:
  - label: "General readers (Recommended)"
    description: "Broad appeal, accessible content"
  - label: "Beginners/learners"
    description: "Educational focus, clear explanations"
  - label: "Experts/professionals"
    description: "Technical depth, domain knowledge"
  - label: "Executives"
    description: "High-level insights, minimal detail"

Question 3: Slide Count

header: "Slides"
question: "How many slides?"
options:
  - label: "{N} slides (Recommended)"
    description: "Based on content length"
  - label: "Fewer ({N-3} slides)"
    description: "More condensed, less detail"
  - label: "More ({N+3} slides)"
    description: "More detailed breakdown"

Question 4: Review Outline

header: "Outline"
question: "Review outline before generating prompts?"
options:
  - label: "Yes, review outline (Recommended)"
    description: "Review slide titles and structure"
  - label: "No, skip outline review"
    description: "Proceed directly to prompt generation"

Question 5: Review Prompts

header: "Prompts"
question: "Review prompts before generating images?"
options:
  - label: "Yes, review prompts (Recommended)"
    description: "Review image generation prompts"
  - label: "No, skip prompt review"
    description: "Proceed directly to image generation"

Round 2 (Only if "Custom dimensions" selected)

Use AskUserQuestion for all 4 dimensions:

Question 1: Texture

header: "Texture"
question: "Which visual texture?"
options:
  - label: "clean"
    description: "Pure solid color, no texture"
  - label: "grid"
    description: "Subtle grid overlay, technical"
  - label: "organic"
    description: "Soft textures, hand-drawn feel"
  - label: "pixel"
    description: "Chunky pixels, 8-bit aesthetic"

(Note: "paper" available via Other)

Question 2: Mood

header: "Mood"
question: "Which color mood?"
options:
  - label: "professional"
    description: "Cool-neutral, navy/gold"
how to use baoyu-slide-deck

How to use baoyu-slide-deck on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add baoyu-slide-deck
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jimliu/baoyu-skills --skill baoyu-slide-deck

The skills CLI fetches baoyu-slide-deck from GitHub repository jimliu/baoyu-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/baoyu-slide-deck

Reload or restart Cursor to activate baoyu-slide-deck. Access the skill through slash commands (e.g., /baoyu-slide-deck) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.671 reviews
  • Ganesh Mohane· Dec 28, 2024

    Useful defaults in baoyu-slide-deck — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Lucas Garcia· Dec 24, 2024

    baoyu-slide-deck is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Amina Sethi· Dec 24, 2024

    Useful defaults in baoyu-slide-deck — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Shikha Mishra· Dec 20, 2024

    Keeps context tight: baoyu-slide-deck is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Advait Sanchez· Dec 20, 2024

    baoyu-slide-deck has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ren Menon· Dec 4, 2024

    Solid pick for teams standardizing on skills: baoyu-slide-deck is focused, and the summary matches what you get after install.

  • Lucas Jackson· Dec 4, 2024

    Keeps context tight: baoyu-slide-deck is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yusuf Zhang· Nov 27, 2024

    Solid pick for teams standardizing on skills: baoyu-slide-deck is focused, and the summary matches what you get after install.

  • Fatima Sethi· Nov 23, 2024

    We added baoyu-slide-deck from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kofi Bansal· Nov 23, 2024

    Registry listing for baoyu-slide-deck matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 71

1 / 8