---

name: baoyu-slide-deck description: Generates professional slide deck images from content. Creates outlines with style instructions, then generates individual slide images. Use when user asks to "create slides", "make a presentation", "generate deck", "slide deck", or "PPT". version: 1.117.4 metadata: openclaw: homepage: https://github.com/JimLiu/baoyu-skills#baoyu-slide-deck requires: anyBins: - bun - npx

Slide Deck Generator

Transform content into professional slide deck images. The deck is designed for reading and sharing (self-explanatory slides, logical scroll flow, social-media-friendly) rather than live presentation — that assumption drives every layout and density decision below.

User Input Tools

When this skill prompts the user, follow this tool-selection rule (priority order):

1. Prefer built-in user-input tools exposed by the current agent runtime — e.g., AskUserQuestion, request_user_input, clarify, ask_user, or any equivalent.
2. Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question.
3. Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order.

Concrete AskUserQuestion references below are examples — substitute the local equivalent in other runtimes.

Image Generation Tools

When this skill needs to render an image, resolve the backend in this order:

1. Current-request override — if the user names a specific backend in the current message, use it.
2. Saved preference — if EXTEND.md sets preferred_image_backend to a backend available right now, use it.
3. Auto-select (when the preference is auto, unset, or the pinned backend isn't available):
   • Codex (imagegen) — first, inspect your available-skills / tool inventory. If a skill named imagegen is listed, you are running inside Codex and MUST use it: invoke via the Skill tool with skill: "imagegen", passing the saved prompt file's content (plus output path and aspect ratio per Codex imagegen's own args). Codex imagegen is the official raster backend in that runtime and outranks any non-native skill (e.g., baoyu-image-gen) unless the user has explicitly pinned a different preferred_image_backend.
   • Codex via codex exec (codex-imagegen) — if the current runtime exposes no native imagegen skill but the codex CLI is on PATH with an active codex login, route through baoyu-image-gen --provider codex-cli (preferred), or — if baoyu-image-gen is unavailable — invoke the bundled wrapper directly. Details, parameters, and the runtime-discovery procedure live in references/codex-imagegen.md — load that file only when this branch is selected.
   • Cursor (GenerateImage) — if the runtime exposes a native GenerateImage tool, you are running inside Cursor and it outranks any non-native skill the same way Codex imagegen does. Two hard caveats: (a) it has no aspect-ratio parameter — state the target aspect ratio / dimensions explicitly in the prompt text passed as description; (b) it does not accept an output directory — it saves to a tool-managed location, so after generation copy/move the file to the skill's expected output path (e.g., outputs/.../NN-xxx.png). Reference images go in reference_image_paths.
   • Other runtime-native tools — if the runtime exposes a different native image tool (e.g., Hermes image_generate), use it the same way.
   • Otherwise, if exactly one non-native backend is installed (e.g., baoyu-image-gen), use it.
   • Otherwise (multiple non-native backends with no runtime-native tool), ask the user once — batch with any other initial questions.
4. If none are available, tell the user and ask how to proceed.

⛔ Never substitute SVG, HTML, canvas, or other code-based rendering for raster image generation. Codex imagegen's own description says it should be used "when the output should be a bitmap asset rather than repo-native code or vector." If you cannot resolve a raster backend via step 3, fall through to step 4 and ask the user — do not silently emit SVG, write inline <svg> markup, or produce HTML/CSS art as a substitute. This applies even if the article/section seems "diagram-like": the consumer skill calling this rule has already decided that a raster image is what it needs.

⛔ Never repair rendered text by painting over a generated bitmap. Do not use ImageMagick, Pillow, Canvas, SVG, HTML/CSS, OCR scripts, or any other programmatic overlay to cover, rewrite, erase, stroke, or replace slide titles, bullets, or any other text inside an already generated slide image. If text is wrong or unclear, regenerate from a corrected prompt, simplify the slide's on-image text, or ask the user which imperfect candidate to keep.

Setting preferred_image_backend: ask forces the step-3 prompt every run regardless of available backends. Users change the pinned backend via the ## Changing Preferences section below.

Prompt file requirement (hard): write each image's full, final prompt to a standalone file under prompts/ (naming: NN-slide-[slug].md) BEFORE invoking any backend. The file is the reproducibility record and lets you switch backends without regenerating prompts.

Concrete tool names (imagegen, GenerateImage, image_generate, baoyu-image-gen) above are examples — substitute the local equivalents under the same rule.

Batch Generation Policy

After every prompt file for the current generation group has been saved and verified, generate slide images in batches by default.

Priority order:

1. Use the chosen backend's native batch / multi-task interface if it exists. Each task must keep its own prompt file, output path, aspect ratio, session ID, and direct reference images.
2. If no native batch interface exists but the runtime can issue parallel tool calls, dispatch up to generation_batch_size slide images at a time. Default: 4. An explicit user request in the current message, such as --batch-size 4 or "并行4张一起生成", overrides EXTEND.md.
3. If neither native batch nor parallel tool calls are available, generate sequentially.

Rules:

• Never start the first batch until all selected slide prompt files exist on disk.
• Retry failed items once without regenerating successful items.
• Do not use subagents merely to parallelize image rendering. Use subagents only for separate prompt iteration or creative exploration.
• Merge PPTX/PDF only after all selected slide images are generated.

Confirmation Policy

Default behavior: confirm before generation.

• Treat explicit skill invocation, a file path, matched signals/presets, and EXTEND.md defaults as recommendation inputs only. None of them authorizes skipping confirmation.
• Do not start Step 3 or later until the user completes Step 2.
• Skip confirmation only when the current request explicitly says to do so, for example: "直接生成", "不用确认", "跳过确认", "按默认出幻灯片", or equivalent wording.
• If confirmation is skipped explicitly, state the assumed style / audience / slide-count / language / backend in the next user-facing update before generating.

Language

Respond in the user's language across questions, progress reports, error messages, and the completion summary. Keep technical tokens (style names, file paths, code) in English.

Script Directory

{baseDir} = this SKILL.md's directory. Resolve ${BUN_X}: prefer bun; else npx -y bun; else suggest brew install oven-sh/bun/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> | Preset (see Presets below), custom, or custom style name | | --audience <type> | beginners / intermediate / experts / executives / general | | --lang <code> | Output language (en, zh, ja, ...) | | --slides <N> | Target slide count (8-25 recommended, max 30) | | --ref <files...> | Reference images applied per slide (style / palette / composition / subject) | | --batch-size <n> | Temporary slide image generation batch size for this run. Default: generation_batch_size from EXTEND.md, otherwise 4. Clamp to 1-8. | | --outline-only | Stop after outline | | --prompts-only | Stop after prompts (skip image generation) | | --images-only | Skip to Step 7; requires existing prompts/ | | --regenerate <N> | Regenerate specific slide(s): 3 or 2,5,8 |

Style System

17 presets covering technical / educational / lifestyle / editorial use cases. Every preset is a combination of four dimensions (texture / mood / typography / density). If the user picks "Custom dimensions" in Round 1, Round 2 of the confirmation asks one question per dimension — options and verbatim copy live in references/confirmation.md.

Presets (17)

| 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 | | hand-drawn-edu | organic + macaron + handwritten + balanced | Educational diagrams, process explainers | | 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 |

Per-preset specs: references/styles/<preset>.md. Preset → dimension mapping: references/dimensions/presets.md.

Dimensions (when "Custom dimensions" picked)

| Dimension | Options | Purpose | |-----------|---------|---------| | Texture | clean, grid, organic, pixel, paper | Background treatment | | Mood | professional, warm, cool, vibrant, dark, neutral, macaron | Color temperature | | Typography | geometric, humanist, handwritten, editorial, technical | Headline/body styling | | Density | minimal, balanced, dense | Information per slide |

Full per-dimension specs: references/dimensions/*.md.

Auto-Selection

Match content signals to a preset. Pick the first row whose signal keywords appear in the source; fall back to blueprint if nothing matches.

| Signals in source | Preset | |-------------------|--------| | tutorial, learn, education, guide, beginner | sketch-notes | | hand-drawn, infographic, diagram, process, onboarding | hand-drawn-edu | | 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, quarter