* refactor(desktop): split clarify-tool.tsx into a clarify/ folder
Pure moves, no behaviour change. Parsing, the question-card core
(shell, choice rows, question block), the delivery watchdog, and each
pending/settled card get their own file so the core can be reused.
* feat(clarify): one questions[] shape with per-question status and one outcome
The clarify tool now takes only questions=[{question, choices?, multi_select?}].
A wrong shape is a tool error that names the right one, so a model that
sends the old top-level question/choices corrects itself on the next call.
Every result has the same shape on every surface: each response carries
status (answered, skipped, unanswered) with user_response null unless
answered, and the result carries one outcome (submitted, cancelled,
timed_out, undelivered) plus an optional surface-written notice. The
timeout and cancel sentences that used to pose as the user's answer are
gone, and the compressor reads status instead of matching their prefixes.
The callback contract is callback(questions) -> {answers, outcome, notice?}
(None = skipped, missing qid = unanswered). tui_gateway settles a batch the
same way for the last lock, a cancel, an interrupt and the deadline, and
clarify.lock keeps a null answer as a skip. A multi-select answer that is
not a JSON array counts as one typed ("Other") answer. The tool-row preview
reads the first question.
* feat(clarify): every surface asks through the one question card
CLI: the batch panel is the only panel; Enter on an empty field skips a
question, Ctrl+C cancels and keeps the locked answers, the deadline returns
timed_out. -q and -z return undelivered with a no-user notice.
Ink TUI: the single-question prompt is gone; the card supports multi-select
(Space or a digit toggles, Enter locks, typed Other text joins the picks),
an empty submit skips, Esc cancels, and "Batch" names are dropped.
Desktop: the single-question card is deleted and its keyboard handling moved
into the one card (arrows, letters and digits, auto-advance, Enter picks then
confirms). Confirm enables at one answer; blank questions lock null; Skip and
a composer message cancel; the settled card shows No answer for unanswered
questions. The bots room card follows the same contract.
Messaging: one card per question with a "Reply skip to skip" line in every
locale; timeouts and delivery failures map to timed_out and undelivered.
* fix(clarify): cancelled for a released messaging card, labels win over the skip word
A prose reply to a messaging choice card, /new and session end released
the wait with "", which read as timed_out. They now resolve with a
CANCELLED marker and the tool gets outcome cancelled.
A typed reply that matches a choice label ("Skip") now resolves to that
choice; the skip word applies only when no choice matches.
The bots room card sends the picked labels as they are; the tool already
strips the recommendation label. Unused OUTCOMES and a new docstring and
comment are removed.
* fix(tui): re-editing a multi-select answer keeps its picks
The Ink card stored a multi-select answer as display text ("A, B"), so
revisiting the question put the whole string into Other and re-locked it
as one item. The answers map now keeps the raw JSON array, the card
restores the picks on revisit, and only the display lines format it.
Comments that earlier edits reworded are restored to their original
words, minus the phrases the change made wrong. The compute-host clarify
lock accepts None for a skipped question.
* test(clarify): align three checks with the one-answer confirm and the regenerated keys
The desktop Cmd+Enter test now expects a send with one answer (the blank
question locks null), the compressor test expects the single-answer summary
the code gives, and locales/_keys.desktop.json is regenerated for the
removed and added clarify strings.
* test(tui): the one-question card header is singular
10 KiB
| name | description | version | author | license | platforms | metadata | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| baoyu-infographic | Infographics: 21 layouts x 21 styles (信息图, 可视化). | 1.56.1 | 宝玉 (JimLiu) | MIT |
|
|
Infographic Generator
Adapted from baoyu-infographic for Hermes Agent's tool ecosystem.
Two dimensions: layout (information structure) × style (visual aesthetics). Freely combine any layout with any style.
When to Use
Trigger this skill when the user asks to create an infographic, visual summary, information graphic, or uses terms like "信息图", "可视化", or "高密度信息大图". The user provides content (text, file path, URL, or topic) and optionally specifies layout, style, aspect ratio, or language.
Options
| Option | Values |
|---|---|
| Layout | 21 options (see Layout Gallery), default: bento-grid |
| Style | 21 options (see Style Gallery), default: craft-handmade |
| Aspect | Named: landscape (16:9), portrait (9:16), square (1:1). Custom: any W:H ratio (e.g., 3:4, 4:3, 2.35:1) |
| Language | en, zh, ja, etc. |
Layout Gallery
| Layout | Best For |
|---|---|
linear-progression |
Timelines, processes, tutorials |
binary-comparison |
A vs B, before-after, pros-cons |
comparison-matrix |
Multi-factor comparisons |
hierarchical-layers |
Pyramids, priority levels |
tree-branching |
Categories, taxonomies |
hub-spoke |
Central concept with related items |
structural-breakdown |
Exploded views, cross-sections |
bento-grid |
Multiple topics, overview (default) |
iceberg |
Surface vs hidden aspects |
bridge |
Problem-solution |
funnel |
Conversion, filtering |
isometric-map |
Spatial relationships |
dashboard |
Metrics, KPIs |
periodic-table |
Categorized collections |
comic-strip |
Narratives, sequences |
story-mountain |
Plot structure, tension arcs |
jigsaw |
Interconnected parts |
venn-diagram |
Overlapping concepts |
winding-roadmap |
Journey, milestones |
circular-flow |
Cycles, recurring processes |
dense-modules |
High-density modules, data-rich guides |
Full definitions: references/layouts/<layout>.md
Style Gallery
| Style | Description |
|---|---|
craft-handmade |
Hand-drawn, paper craft (default) |
claymation |
3D clay figures, stop-motion |
kawaii |
Japanese cute, pastels |
storybook-watercolor |
Soft painted, whimsical |
chalkboard |
Chalk on black board |
cyberpunk-neon |
Neon glow, futuristic |
bold-graphic |
Comic style, halftone |
aged-academia |
Vintage science, sepia |
corporate-memphis |
Flat vector, vibrant |
technical-schematic |
Blueprint, engineering |
origami |
Folded paper, geometric |
pixel-art |
Retro 8-bit |
ui-wireframe |
Grayscale interface mockup |
subway-map |
Transit diagram |
ikea-manual |
Minimal line art |
knolling |
Organized flat-lay |
lego-brick |
Toy brick construction |
pop-laboratory |
Blueprint grid, coordinate markers, lab precision |
morandi-journal |
Hand-drawn doodle, warm Morandi tones |
retro-pop-grid |
1970s retro pop art, Swiss grid, thick outlines |
hand-drawn-edu |
Macaron pastels, hand-drawn wobble, stick figures |
Full definitions: references/styles/<style>.md
Recommended Combinations
| Content Type | Layout + Style |
|---|---|
| Timeline/History | linear-progression + craft-handmade |
| Step-by-step | linear-progression + ikea-manual |
| A vs B | binary-comparison + corporate-memphis |
| Hierarchy | hierarchical-layers + craft-handmade |
| Overlap | venn-diagram + craft-handmade |
| Conversion | funnel + corporate-memphis |
| Cycles | circular-flow + craft-handmade |
| Technical | structural-breakdown + technical-schematic |
| Metrics | dashboard + corporate-memphis |
| Educational | bento-grid + chalkboard |
| Journey | winding-roadmap + storybook-watercolor |
| Categories | periodic-table + bold-graphic |
| Product Guide | dense-modules + morandi-journal |
| Technical Guide | dense-modules + pop-laboratory |
| Trendy Guide | dense-modules + retro-pop-grid |
| Educational Diagram | hub-spoke + hand-drawn-edu |
| Process Tutorial | linear-progression + hand-drawn-edu |
Default: bento-grid + craft-handmade
Keyword Shortcuts
When user input contains these keywords, auto-select the associated layout and offer associated styles as top recommendations in Step 3. Skip content-based layout inference for matched keywords.
If a shortcut has Prompt Notes, append them to the generated prompt (Step 5) as additional style instructions.
| User Keyword | Layout | Recommended Styles | Default Aspect | Prompt Notes |
|---|---|---|---|---|
| 高密度信息大图 / high-density-info | dense-modules |
morandi-journal, pop-laboratory, retro-pop-grid |
portrait | — |
| 信息图 / infographic | bento-grid |
craft-handmade |
landscape | Minimalist: clean canvas, ample whitespace, no complex background textures. Simple cartoon elements and icons only. |
Output Structure
infographic/{topic-slug}/
├── source-{slug}.{ext}
├── analysis.md
├── structured-content.md
├── prompts/infographic.md
└── infographic.png
Slug: 2-4 words kebab-case from topic. Conflict: append -YYYYMMDD-HHMMSS.
Core Principles
- Preserve source data faithfully — no summarization or rephrasing (but strip any credentials, API keys, tokens, or secrets before including in outputs)
- Define learning objectives before structuring content
- Structure for visual communication (headlines, labels, visual elements)
Workflow
Step 1: Analyze Content
Load references: Read references/analysis-framework.md from this skill.
- Save source content (file path or paste →
source.mdusingwrite_file)- Backup rule: If
source.mdexists, rename tosource-backup-YYYYMMDD-HHMMSS.md
- Backup rule: If
- Analyze: topic, data type, complexity, tone, audience
- Detect source language and user language
- Extract design instructions from user input
- Save analysis to
analysis.md- Backup rule: If
analysis.mdexists, rename toanalysis-backup-YYYYMMDD-HHMMSS.md
- Backup rule: If
See references/analysis-framework.md for detailed format.
Step 2: Generate Structured Content → structured-content.md
Transform content into infographic structure:
- Title and learning objectives
- Sections with: key concept, content (verbatim), visual element, text labels
- Data points (all statistics/quotes copied exactly)
- Design instructions from user
Rules: Markdown only. No new information. Preserve data faithfully. Strip any credentials or secrets from output.
See references/structured-content-template.md for detailed format.
Step 3: Recommend Combinations
3.1 Check Keyword Shortcuts first: If user input matches a keyword from the Keyword Shortcuts table, auto-select the associated layout and prioritize associated styles as top recommendations. Skip content-based layout inference.
3.2 Otherwise, recommend 3-5 layout×style combinations based on:
- Data structure → matching layout
- Content tone → matching style
- Audience expectations
- User design instructions
Step 4: Confirm Options
Use the clarify tool to confirm options with the user. Put the independent questions below in one questions array (up to 5); ask separately any question whose options depend on an earlier answer:
Q1 — Combination: Present 3+ layout×style combos with rationale. Ask user to pick one.
Q2 — Aspect: Ask for aspect ratio preference (landscape/portrait/square or custom W:H).
Q3 — Language (only if source ≠ user language): Ask which language the text content should use.
Step 5: Generate Prompt → prompts/infographic.md
Backup rule: If prompts/infographic.md exists, rename to prompts/infographic-backup-YYYYMMDD-HHMMSS.md
Load references: Read the selected layout from references/layouts/<layout>.md and style from references/styles/<style>.md.
Combine:
- Layout definition from
references/layouts/<layout>.md - Style definition from
references/styles/<style>.md - Base template from
references/base-prompt.md - Structured content from Step 2
- All text in confirmed language
Aspect ratio resolution for {{ASPECT_RATIO}}:
- Named presets → ratio string: landscape→
16:9, portrait→9:16, square→1:1 - Custom W:H ratios → use as-is (e.g.,
3:4,4:3,2.35:1)
Save the assembled prompt to prompts/infographic.md using write_file.
Step 6: Generate Image
Use the image_generate tool with the assembled prompt from Step 5.
- Map aspect ratio to image_generate's format:
16:9→landscape,9:16→portrait,1:1→square - For custom ratios, pick the closest named aspect
- On failure, auto-retry once
- Save the resulting image URL/path to the output directory
Step 7: Output Summary
Report: topic, layout, style, aspect, language, output path, files created.
References
references/analysis-framework.md— Analysis methodologyreferences/structured-content-template.md— Content formatreferences/base-prompt.md— Prompt templatereferences/layouts/<layout>.md— 21 layout definitionsreferences/styles/<style>.md— 21 style definitions
Pitfalls
- Data integrity is paramount — never summarize, paraphrase, or alter source statistics. "73% increase" must stay "73% increase", not "significant increase".
- Strip secrets — always scan source content for API keys, tokens, or credentials before including in any output file.
- One message per section — each infographic section should convey one clear concept. Overloading sections reduces readability.
- Style consistency — the style definition from the references file must be applied consistently across the entire infographic. Don't mix styles.
- image_generate aspect ratios — the tool only supports
landscape,portrait, andsquare. Custom ratios like3:4should map to the nearest option (portrait in that case).