OpenSenseNova/SenseNova-Skills / skills/sn-infographic
sn-infographic
VerifiedGenerates professional infographics with various layout types and visual styles. Analyzes content, recommends layout and style, and generates publication-ready infographics. Use when user asks to create "infographic", "信息图", "visual summary", or "可视化".
references/runtime-parameters.md
View on GitHub# Runtime Parameter Mapping
This file defines how `sn-infographic` infers runtime arguments for `sn-image-base` tools.
## Inputs
Read from:
- the original user request
- any explicit follow-up confirmation from the user about size or ratio
## Output Arguments
Map into:
- `--image-size`
- `--aspect-ratio`
## Image Size
If the Main Agent already resolved an explicit `image_size` (the user stated a supported size upstream), use it directly. Otherwise infer it — the inference currently has a **single option, `2k`**. Never ask the user about it.
Rules:
- Supported explicit values: `2k`, `4k`. Take the user's value only when stated explicitly (`image_size=4k`, or a bare `2k` / `4k` token, optionally after an `image_size` / `分辨率` / `清晰度` lead-in).
- Vague quality words (`高清`, `超清`, `print-quality`, "faster draft", …) do **not** count as an explicit size — ignore them.
- With no explicit size, the inference resolves to `2k`.
- `4k` is passed to the image model; SenseNova `sensenova-u1.5-lite` supports native 4K, while `sensenova-u1-fast` may reject it. The skill surfaces backend errors as-is.
## Aspect Ratio
Supported values:
- `2:3`
- `3:2`
- `3:4`
- `4:3`
- `4:5`
- `5:4`
- `1:1`
- `16:9`
- `9:16`
- `21:9`
- `9:21`
If the Main Agent already resolved an explicit `aspect_ratio` (the user stated a supported ratio upstream), and is a valid value (in the supported values above), use it directly and skip the rules below — this is rule 1 applied at the Main Agent boundary.
Otherwise, use the first matching rule:
1. If the user explicitly gives a supported ratio, use it directly.
2. If the user confirms a ratio preference in a follow-up turn, use that confirmed value.
3. If the user gives only orientation:
- `Portrait` or `竖屏` -> prefer `9:16`; use `4:5`, `3:4`, or `2:3` when the prompt implies a print poster, editorial layout, or card-style portrait composition
- `Landscape` or `横屏` -> prefer `16:9`; use `4:3`, `3:2`, `5:4`, or `21:9` when the prompt implies classic slides, photography framing, near-square cards, or cinematic banners
- `Square` or `方形` -> `--aspect-ratio 1:1`
4. If neither ratio nor orientation is explicit, infer from the scene:
- phone wallpaper, story card, vertical reel cover, ultra-tall mobile infographic -> `9:16` or `9:21`
- print poster, book cover, one-page portrait infographic -> `2:3`
- editorial illustration, portrait card, magazine-style page -> `3:4`
- social feed poster, product card, portrait marketing creative -> `4:5`
- avatar, icon, logo mark, square cover -> `1:1`
- presentation slide, dashboard, classroom chart, classic screen layout -> `4:3`
- landscape photo, postcard, brochure hero, medium-width banner -> `3:2`
- near-square desktop card, comparison board, compact infographic panel -> `5:4`
- banner, keynote cover, widescreen infographic, landing hero -> `16:9`
- cinematic hero, panoramic banner, ultra-wide header -> `21:9`
- otherwise -> `16:9`
## Notes
- The skill should pass `expanded_prompt` (from `prompts-expand`) as `--prompt`, not the raw user request.
- `image_size`: the Main Agent takes an explicit `2k` / `4k`; otherwise the Worker infers it in Step 0 — currently a single option, `2k`. Never ask the user about it.
- `aspect_ratio` is inferred from the **original `user_prompt`** (before expansion), not from `expanded_prompt`.
- Prefer inference over interruption when there is one clearly reasonable choice.
- Ask the user only when multiple aspect ratios are genuinely plausible and the choice would materially change composition or layout.
- When asking the user, ask for `aspect_ratio` directly instead of a vague "horizontal or vertical" question whenever possible.
- Use `--save-path` to write the output directly to the task's temp directory (`/tmp/openclaw/sn-infographic/<task_id>/round_<N>.png`), avoiding a separate move step.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |