OrRon/EpicInfographics

Selection

Select when

• You need a Claude Code skill specialized in infographic creation rather than general UI design.
• You want editable self-contained HTML/CSS/inline-SVG source alongside PNG output.
• You need presets for social, story, presentation, link-preview, print, or scrolling formats.
• You want an agent to propose and route among several visual story angles.
• You value computed chart geometry and explicit prohibitions on misleading common chart patterns.
• You want mechanical checks for text collisions, clipping, readability, and focal hierarchy before rendering.
• You want a mandatory render-review-fix loop with visual anti-template criteria.
• You need optional MP4 or GIF animation built from the approved static design.
• You are comfortable installing Node dependencies and Playwright Chromium locally.
• You can inspect generated HTML, sources, geometry, and final visual output before publication.

Boundaries

Avoid when

• You cannot allow local Node scripts or a headless Chromium dependency.
• You require a no-network render path because Google Fonts are the documented external exception.
• You need a hosted, zero-install image-generation service.
• You need direct editing in Figma, Illustrator, or another native design-file format.
• You cannot install or provide ffmpeg for requested animation.
• You require independently validated accessibility, security, or output-quality guarantees.
• You need fully automated publication without human fact-checking or visual review.
• You need a generic charting library or interactive dashboard rather than a composed static scene.
• You need a stable host-version compatibility matrix or long-term support policy.
• You cannot review executable generated HTML and repository scripts before use.

Strengths

Capabilities

Risk profile

Risks and limitations

• Uncertainty: the supplied evidence does not include the implementations of check.mjs, render.mjs, animate.mjs, validate.mjs, templates, style references, CI workflow, or generated example source for direct inspection.
• Uncertainty: repository metadata is dated in 2026 relative to this analysis context, so activity, adoption, and recency signals cannot be independently reconciled.
• Uncertainty: README and gallery quality claims are first-party statements, and no independent output benchmark, user study, or reproducible evaluation was supplied.
• Documentation is inconsistent about style count: the README and skill describe twelve styles, while plugin metadata advertises ten.
• The packaged version is 0.2.0, and no release history, migration policy, or stability commitment was supplied.
• Rendering requires Node dependencies, Playwright, and a Chromium installation; animation additionally requires ffmpeg on PATH.
• Google Fonts are allowed as an external resource, so font retrieval can create network availability and privacy considerations.
• The skill may research missing facts through the host agent, but source quality, permissions, and factual correctness remain user responsibilities.
• Mechanical checks cannot establish narrative truth, aesthetic quality, accessibility, or correct interpretation of the underlying data.
• Generated HTML and SVG are executable or active browser content and should be reviewed before opening or rendering with sensitive local context.
• The workflow is intentionally opinionated and may reject flat, minimal, corporate, or brand-system layouts unless explicitly requested.
• Only the latest release on main is supported according to the security policy, with no long-term-support branch documented.

First-party evidence includes a security policy covering unexpected render-script fetching or execution, external scripts or data exfiltration in HTML, and prompt injection in skill files or examples. Vulnerabilities are reported privately through GitHub with a stated one-week response target, and only latest main is supported. The workflow executes local Node scripts and opens generated HTML in Chromium; no sandbox, audit, dependency review, or script implementation was supplied, so users should treat generated pages and scripts as trusted-code surfaces.