// Article illustrations: type × style × palette consistency.
Configure, extend, or contribute to Hermes Agent.
Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
Use when a Hermes Kanban worker wants to run Codex CLI as an isolated implementation lane while Hermes keeps ownership of task lifecycle, reconciliation, testing, and handoff.
Zero-install localhost tunnels over SSH via Pinggy.
Notion API + ntn CLI: pages, databases, markdown, Workers.
| name | baoyu-article-illustrator |
| description | Article illustrations: type × style × palette consistency. |
| version | 1.57.0 |
| author | 宝玉 (JimLiu) |
| license | MIT |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["article-illustration","creative","image-generation"],"category":"creative","homepage":"https://github.com/JimLiu/baoyu-skills#baoyu-article-illustrator"}} |
Adapted from baoyu-article-illustrator for Hermes Agent's tool ecosystem.
Analyze articles, identify illustration positions, generate images with Type × Style × Palette consistency.
Trigger this skill when the user asks to illustrate an article, add images to an article, generate illustrations for content, or uses phrases like "为文章配图", "illustrate article", or "add images". The user provides an article (file path or pasted content) and optionally specifies type, style, palette, or density.
| Dimension | Controls | Examples |
|---|---|---|
| Type | Information structure | infographic, scene, flowchart, comparison, framework, timeline |
| Style | Rendering approach | notion, warm, minimal, blueprint, watercolor, elegant |
| Palette | Color scheme (optional) | macaron, warm, neon — overrides style's default colors |
Combine freely: type=infographic, style=vector-illustration, palette=macaron.
Or use presets: edu-visual → type + style + palette in one shot. See style-presets.md.
| Type | Best For |
|---|---|
infographic | Data, metrics, technical |
scene | Narratives, emotional |
flowchart | Processes, workflows |
comparison | Side-by-side, options |
framework | Models, architecture |
timeline | History, evolution |
See references/styles.md for Core Styles, the full gallery, and Type × Style compatibility.
{output-dir}/
├── source-{slug}.{ext} # Only for pasted content
├── outline.md
├── prompts/
│ └── NN-{type}-{slug}.md
└── NN-{type}-{slug}.png
Default output directory:
| Input | Output Directory | Markdown Insert Path |
|---|---|---|
| Article file path | {article-dir}/imgs/ | imgs/NN-{type}-{slug}.png |
| Pasted content | illustrations/{topic-slug}/ (cwd) | illustrations/{topic-slug}/NN-{type}-{slug}.png |
If the user asks for a different layout (e.g., images alongside the article, or a illustrations/ subdirectory), honor that.
Slug: 2-4 words, kebab-case. Conflict: append -YYYYMMDD-HHMMSS.
prompts/ before any image is generated.- [ ] Step 1: Detect reference images (if provided)
- [ ] Step 2: Analyze content
- [ ] Step 3: Confirm settings (clarify tool, one question at a time)
- [ ] Step 4: Generate outline
- [ ] Step 5: Generate prompts
- [ ] Step 6: Generate images (image_generate)
- [ ] Step 7: Finalize
If the user supplies reference images (paths pasted inline, attachments, or a URL):
vision_analyze with the path/URL and a question asking for style, palette, composition, and subject. Record the returned description in {output-dir}/references/NN-ref-{slug}.md via write_file.write_file / read_file — those are text-only. If you want a local copy for the record, use terminal (cp "$src" "{output-dir}/references/NN-ref-{slug}.{ext}"). The skill itself never needs to read the binary; it works off the vision description.image_generate doesn't take image inputs, the vision description is what gets embedded in prompts during Step 5.Full procedures: references/workflow.md.
| Analysis | Output |
|---|---|
| Content type | Technical / Tutorial / Methodology / Narrative |
| Purpose | information / visualization / imagination |
| Core arguments | 2-5 main points |
| Positions | Where illustrations add value |
Read source (file path → read_file, or pasted text) and write the analysis to {output-dir}/analysis.md using write_file.
Full procedures: references/workflow.md.
Use the clarify tool. Since clarify handles one question at a time, ask the most important question first. Skip any question whose answer is already present in the user's request.
| Order | Question | Options |
|---|---|---|
| Q1 | Preset or Type | [Recommended preset], [alt preset], or manual: infographic, scene, flowchart, comparison, framework, timeline, mixed |
| Q2 | Density | minimal (1-2), balanced (3-5), per-section (Recommended), rich (6+) |
| Q3 | Style (skip if preset chosen in Q1) | [Recommended], minimal-flat, sci-fi, hand-drawn, editorial, scene, poster |
| Q4 | Palette (optional) | Default (style colors), macaron, warm, neon |
| Q5 | Language (only if article language is ambiguous) | article language / user language |
Don't ask more than 2-3 clarify questions in a row. If the user already specified these in their request, skip entirely.
Full procedures: references/workflow.md.
outline.mdSave {output-dir}/outline.md using write_file with frontmatter (type, density, style, palette, image_count) and one entry per illustration:
## Illustration 1
**Position**: [section/paragraph]
**Purpose**: [why]
**Visual Content**: [what to show]
**Filename**: 01-infographic-concept-name.png
Full template: references/workflow.md.
BLOCKING: Every illustration must have a saved prompt file before any image is generated — the prompt file is the reproducibility record.
For each illustration:
{output-dir}/prompts/NN-{type}-{slug}.md using write_file with YAML frontmatter.direct/style/palette) per prompt frontmatter — for direct usage, embed a textual description of the reference in the prompt (since image_generate doesn't take reference-image inputs).For each prompt file:
image_generate(prompt=..., aspect_ratio=...). image_generate returns a JSON result containing an image URL; it does NOT write to disk and does NOT accept an output path.ASPECT to image_generate's enum: 16:9 → landscape, 9:16 → portrait, 1:1 → square. Custom ratios → nearest named aspect.{output-dir}/NN-{type}-{slug}.png via terminal (e.g. curl -sSL -o "{output-dir}/NN-{type}-{slug}.png" "{url}").Note: the underlying image-generation backend is user-configured (default: FAL FLUX 2 Klein 9B) and is NOT agent-selectable via image_generate. Do not write model names into prompts expecting them to route.
Insert  after the corresponding paragraph. Alt text: concise description in the article's language.
Report:
Article Illustration Complete!
Article: [path] | Type: [type] | Density: [level] | Style: [style] | Palette: [palette or default]
Images: X/N generated
| Action | Steps |
|---|---|
| Edit | Update prompt → Regenerate → Update reference |
| Add | Position → Prompt → Generate → Update outline → Insert |
| Delete | Delete files → Remove reference → Update outline |
| File | Content |
|---|---|
| references/workflow.md | Detailed procedures |
| references/usage.md | Invocation examples |
| references/styles.md | Style gallery + Palette gallery |
| references/style-presets.md | Preset shortcuts (type + style + palette) |
| references/prompt-construction.md | Prompt templates |
image_generate aspect ratios — the tool supports landscape, portrait, and square. Custom ratios map to the nearest option.image_generate returns a URL, not a local file — always download via terminal (curl) before inserting local image paths into the article.image_generate uses whatever model the user configured (default: FAL FLUX 2 Klein 9B). Don't write "use <model> to generate this" into prompts expecting it to route.