Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Infographic Designer

ASecurity

Turn complex data and processes into clear, honest infographics with strong visual storytelling.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsrustgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill infographic-designer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Infographic Designer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Infographic Designer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-infographic-designer/badge)](https://www.skillsdirectory.com/skills/aicodedecode-infographic-designer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: infographic-designer
description: Turn complex data and processes into clear, honest infographics with strong visual storytelling.
category: creative-design
---

## Overview

Infographics translate complexity into understanding — but the genre is polluted
with chart junk,
misleading visuals, and decoration masquerading as information. This skill is
about honest visual
storytelling: choosing the right chart for the data, structuring the narrative
flow, and designing
for comprehension first, shareability second.

## When to use

- Visualizing survey results, research findings, or statistics

- Explaining processes, timelines, or how-things-work

- Creating shareable data content for marketing or social

- Turning a dense report into a visual summary

- Reviewing an infographic for accuracy and clarity

## Core concepts

- - - **Data honesty is sacred.** Truncated axes, cherry-picked ranges, area
  distortions, and
  misleading pictographs destroy trust. Every visual choice should survive the
question: "does this
  fairly represent the data?"
- - - **Right chart for the message.** Comparison → bars; trend over time →
  lines; part-to-whole →
  stacked bars (pie only for 2-3 parts); distribution → histograms; relationship
→ scatterplots.
  Novelty charts (3D pies, radial everything) usually obscure.
- - - **Narrative structure.** Headline finding → supporting evidence in logical
  order →
  methodology/source → takeaway. An infographic is a story, not a data dump;
sequence matters.
- - - **Hierarchy of numbers.** One hero stat (big, unforgettable), supporting
  stats (medium), context
  (small). Not every number deserves equal weight — design the importance.
- - - **Annotation over decoration.** Labels directly on data, callouts
  explaining the "so what,"
  source citations. Every decorative element should be interrogated: does it aid
understanding? If
  not, cut it.
- - - **Design for the channel.** A tall infographic for Pinterest/blog
  embedding, square or carousel
  for social, landscape for decks. One design rarely serves all — adapt the
layout per channel.

## Practical workflow

1. 1. 1. **Understand the data.** Read the source, check methodology, note
   caveats and sample sizes.
   You can't visualize honestly what you don't understand.
2. 2. 2. **Find the story.** What's the single most important finding? What's
   surprising? Structure 3-5
   supporting points that build the narrative. Kill interesting-but-irrelevant
data.
3. 3. 3. **Choose visual forms.** Match each point to its best chart or diagram
   type. Sketch the flow:
   how does the eye travel from headline to conclusion?
4. 4. 4. **Draft the layout.** Wireframe the sections: hero stat, supporting
   visuals in narrative
   order, methodology footer. Check the story reads top-to-bottom without the
designer's
   explanation.
5. 5. 5. **Design with restraint.** Limited palette (one accent for key data,
   neutrals for context),
   consistent chart styling, clear typography hierarchy. Data ink maximized,
decoration minimized.
6. 6. 6. **Verify everything.** Recheck every number against the source, every
   axis for honest scaling,
   every claim for fair representation. Have someone else fact-check — designers
go number-blind.
7. 7. 7. **Export for channels.** Full version for web/print, adapted crops for
   social, alt text
   describing the key findings for accessibility. Include the source link
wherever it's shared.

## Common pitfalls

- - - **Misleading visuals.** Truncated y-axes exaggerating small differences,
  pictograph areas
  scaling incorrectly, dual axes implying false correlations. When in doubt,
start axes at zero and
  label honestly.
- - - **Data vomit.** Cramming every available statistic in. An infographic with
  40 numbers
  communicates zero numbers. Curate to the story.
- - - **Decoration over information.** Illustrations, icons, and backgrounds
  that compete with the
  data. Every pixel should serve comprehension.
- - - **Missing sources.** No methodology, no sample size, no source link.
  Unsourced infographics are
  rumors with good design.
- - - **Unreadable at size.** Tiny labels, cramped charts, text that fails on
  mobile. Test at the
  actual viewing size for each channel.
- - - **The kitchen-sink timeline.** Timelines with 30 undifferentiated events.
  Highlight the 5 that
  matter; summarize or cut the rest.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →