Infographic

Infographic Skill

Create professional, mobile-friendly infographic images from structured content using HTML + Playwright screenshot.

When to Use

• User shares an article/tweet and asks for an infographic or visual summary
• User wants a shareable image for WeChat groups, Telegram, Twitter, etc.
• User asks for a "knowledge card", "one-pager", or "visual breakdown"

Workflow

Article/Content → Extract Key Points → Design HTML → Screenshot (3x) → Deliver PNG

Step 1: Extract & Structure Content

Analyze the source material and identify:

• Title (bilingual if applicable: Chinese primary, English subtitle)
• Core thesis (1-2 sentence summary for callout box)
• Main sections (3-7 sections, each with title + 1-3 bullet points)
• Key insight or takeaway (for the dark bottom section)
• Source attribution (author, platform, URL)

Keep text concise — infographics are scannable, not readable. If a section needs more than 3 short lines, split it.

Step 2: Design the HTML

Create a single self-contained HTML file (no external dependencies). Read {baseDir}/references/design-system.md for the full color palette, typography, and component library.

Page setup:

* { margin: 0; padding: 0; box-sizing: border-box; }
body {
  width: 750px;
  background: #faf6f0;
  font-family: -apple-system, 'PingFang SC', 'Noto Sans SC', sans-serif;
  padding: 44px 40px;
}

Key rules:

• Width: always 750px (renders to 2250px at 3x — optimal for mobile)
• No fixed height — content determines length, no wasted whitespace
• Minimum font size: 12px (renders to 36px physical pixels at 3x)
• Background: #faf6f0 (cream) or #fff — never transparent
• All CSS inline in `` — no external files, no Google Fonts CDN
• Chinese font stack: -apple-system, 'PingFang SC', 'Noto Sans SC', sans-serif

Layout pattern (adapt to content):

1. Header: badge + title + subtitle + divider
2. Callout box: core thesis in yellow box with gold left border
3. Content cards: numbered sections with colored accent circles
4. Takeaway box: dark background, key conclusions
5. Footer: source attribution + brand

Use the design system reference for exact colors, spacing, and component HTML.

Step 3: Screenshot with Playwright

Use the bundled screenshot script:

node {baseDir}/scripts/screenshot.js /tmp/infographic.html /path/to/output.png 3 750

Arguments: [scaleFactor=3] [viewportWidth=750]

The script automatically finds Playwright in the npx cache or global install.

If the script fails, use this inline approach:

NODE_PATH=$(find ~/.npm/_npx -name "index.mjs" -path "*/playwright/*" -exec dirname {} \; -exec dirname {} \; 2>/dev/null | head -1) \
node -e "
const pw = require('playwright');
(async () => {
  const browser = await pw.chromium.launch();
  const ctx = await browser.newContext({ viewport: { width: 750, height: 600 }, deviceScaleFactor: 3 });
  const page = await ctx.newPage();
  await page.goto('file:///tmp/infographic.html', { waitUntil: 'networkidle' });
  await page.locator('body').screenshot({ path: 'OUTPUT.png', type: 'png' });
  await browser.close();
})();
"

Never use npx playwright screenshot CLI — it doesn't support deviceScaleFactor and produces blurry 1x images.

Step 4: Deliver

Telegram delivery (lossless):

OpenClaw's message send routes .png files through Telegram's sendPhoto API, which compresses images to max 2048px on the longest side. To deliver the original high-res image, use sendDocument directly:

bash {baseDir}/scripts/send_telegram.sh /path/to/output.png "Caption text"

Or with the message tool if the platform doesn't compress (Discord, etc.), just send normally.

Other platforms: Most platforms preserve document uploads. Use the message tool with filePath for non-Telegram delivery.

Design Principles

1. Scannable, not readable — if someone has to zoom in to read, there's too much text
2. Visual hierarchy — title → callout → numbered cards → takeaway. Eyes should flow top-to-bottom naturally
3. Consistent color coding — each section gets one accent color from the palette, don't mix randomly
4. Mobile-first — 750px width at 3x = 2250px physical. Looks crisp on any phone
5. Self-contained — single HTML file, no external resources, works offline

Customization

• For English-only content: same layout, adjust font stack to include serif options
• For data-heavy content: use the 2×2 grid pattern or horizontal bar charts in CSS
• For comparison content: use side-by-side dark cards in the takeaway section
• For longer articles (7+ sections): consider splitting into 2 images or using a more compact card style

Requirements

• Node.js (any recent version)
• Playwright with Chromium (npx playwright install chromium)
• For Telegram lossless delivery: curl + bot token in ~/.openclaw/openclaw.json

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: jincai
• Source: jincai/openclaw-skills
• License: MIT

Install and usage instructions live in the source repository linked above.