Design
1,324 installs
Knowledge Comic Creator
by jimliu/baoyu-skills
Knowledge comic creator supporting multiple art styles and tones. Creates original educational comics with detailed panel layouts and batch-capable image…
Skill content
Educational comics with flexible art styles, tones, and panel layouts for knowledge storytelling. - Supports five art styles (ligne-claire, manga, realistic, ink-brush, chalk) and seven tones (neutral, warm, dramatic, romantic, energetic, vintage, action) with compatibility guidance to avoid mismatched combinations - Includes three preset shortcuts (ohmsha for tutorials, wuxia for martial arts, shoujo for romance) that apply special visual rules beyond style selection - Auto-detects optimal style and tone from content signals (tutorials, historical, personal stories, biographies) and generates storyboards, character sheets, and sequential image prompts - Offers partial workflows: storyboard-only, prompts-only, image regeneration, and page-level edits with automatic renumbering and PDF merging - Requires bun or npx; outputs organized comic directories with analysis, storyboard, character references, generation prompts, and final PDF Knowledge Comic Creator Create original knowledge comics with flexible art style × tone combinations. User Input Tools When this skill prompts the user, follow this tool-selection rule (priority order): - Prefer built-in user-input tools exposed by the current agent runtime - e.g., AskUserQuestion, request_user_input, clarify, ask_user, or any equivalent. - 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. - 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: