/baoyu-comic

name: baoyu-comic
description: Knowledge comic creator supporting multiple art styles and tones. Creates original educational comics with detailed panel layouts and batch-capable image generation. Use when user asks to create "知识漫画", "教育漫画", "biography comic", "tutorial comic", or "Logicomix-style comic".
version: 1.117.4
metadata:
  openclaw:
    homepage: https://github.com/JimLiu/baoyu-skills#baoyu-comic
    requires:
      anyBins:
        - bun
        - npx

Knowledge Comic Creator

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

Resolve the image backend in this order:

1. **User names a backend** in the current message → use it. 2. **`preferred_image_backend`** in `EXTEND.md` names a backend available now → use it. `ask` means ask every run. 3. **Auto-select** (preference `auto`, unset, or the pinned backend is unavailable), first match wins:

• **Codex `imagegen`** skill is in your available skills → you are in Codex and MUST use it: `Skill` with `skill: "imagegen"`, passing the prompt file's content plus output path and aspect ratio. It outranks non-native skills such as `baoyu-image-gen`.
• **Codex via `codex exec` (`codex-imagegen`)**: no native `imagegen`, but the `codex` CLI is on `PATH` with an active `codex login` → `baoyu-image-gen --provider codex-cli` (preferred), or the bundled wrapper if baoyu-image-gen is unavailable. Load [references/codex-imagegen.md](references/codex-imagegen.md) only for this branch.
• **Cursor `GenerateImage`** → use it (outranks non-native skills). It has no aspect-ratio parameter, so state the aspect ratio / dimensions in the `description` prompt; it saves to a tool-managed location, so copy the file to the expected output path (e.g., `outputs/.../NN-xxx.png`). Reference images go in `reference_image_paths`.
• **Other runtime-native image tool** (e.g., Hermes `image_generate`) → use it the same way.
• Exactly one non-native backend installed (e.g., `baoyu-image-gen`) → use it.
• Several non-native backends → ask the user once, batched with other initial questions.

4. **None available** → tell the user and ask how to proceed.

**⛔ Raster only**: never substitute SVG, HTML/CSS, canvas, or other code-based rendering for a raster image, even for diagram-like content. If no raster backend resolves, go to step 4.

**⛔ No bitmap text patching**: never use ImageMagick, Pillow, Canvas, SVG, HTML/CSS, OCR scripts, or any other overlay to cover, rewrite, erase, stroke, or replace dialogue, sound effects, panel labels, or any other text inside an already generated comic page. Regenerate from a corrected prompt, redraw the page with less or no on-image text, or ask the user which imperfect candidate to keep.

**Prompt file (hard)**: before invoking any backend, write each image's full, final prompt to its own file under `prompts/` (`NN-{type}-[slug].md`) and pass that file (or its content) to the backend. It is the reproducibility record and lets you switch backends without rewriting prompts.

Change the pinned backend via `## Changing Preferences` below. Tool names above are examples; use the local equivalent in other runtimes.

Batch Generation Policy

After every prompt file for the current generation group is saved and verified, generate images in batches by default:

1. Use the backend's native batch / multi-task interface if it exists. Each task keeps its own prompt file, output path, aspect ratio, session ID, and direct reference images. 2. Else, if the runtime can issue parallel tool calls, dispatch up to `generation_batch_size` images at a time (default `4`). An explicit request in the current message (e.g. `--batch-size 4`, "并行4张一起生成") overrides EXTEND.md. 3. Else generate sequentially.

Rules:

• Honor dependencies: generate `characters/characters.png` before pages that use it as a reference.
• Never start the first page batch until all selected page prompt files exist on disk.
• Retry failed items once without regenerating successful items.
• Do not use subagents merely to parallelize image rendering; use them only for separate prompt iteration or creative exploration.

Reference Images

User-supplied reference images guide art style, palette, scene composition, or subject. They are **separate from** the auto-generated character sheet (Step 7.1); both can coexist — user refs guide the look, the character sheet anchors recurring character identity.

**Intake** via `--ref <files...>` or file paths / pasted images in conversation:

• File path(s) → copy to `refs/NN-ref-{slug}.{ext}` alongside the comic output
• Pasted image with no path → ask for the path (per User Input Tools), or extract style traits verbally as a text fallback
• No reference → skip this section

**Usage modes** (per reference):

| Usage | Effect | |-------|--------| | `direct` | Pass the file to the backend as a reference image on every page (or selected pages) | | `style` | Extract style traits (line treatment, texture, mood) and append to every page's prompt body | | `palette` | Extract hex colors and append to every page's prompt body |

**Record in each page's prompt frontmatter** when refs exist:

references:
  - ref_id: 01
    filename: 01-ref-scene.png
    usage: direct

**At generation time**:

• Verify each referenced file exists on dis