git:20260216.0df482f to git:20260216.0b52bb5

---

name: infographic

description: Generate professional infographics using Nano Banana MCP (Gemini AI image generation). Follows a guided flow — analyze content, suggest visualizable concepts, propose visualization approaches, then generate on-brand images. USE THIS SKILL WHEN user says "create infographic", "make a visual", "design an infographic", "generate infographic", wants to visualize a concept, framework, or data for social media, mentions "LinkedIn post", "visual content", "infographic series", asks to explain a concept visually or create a diagram-style image, mentions "visual metaphor", "iceberg diagram", "pyramid", "funnel visualization", wants to generate images with Gemini for informational content, or says "brand visuals", "social media graphics", "thought leadership visual".

- User mentions "nano banana", "gemini image generation", "professional infographics"

---

# Infographic Generation Skill

---

## When This Skill Loads (DO THIS IMMEDIATELY)

4. Execute Phase 0 (silent config check)

5. **If API key is NOT configured in Phase 0:**

- Skip directly to Phase 4 (API Key Setup)

- Do NOT proceed to Phase 1

- Do NOT ask about content

6. **If API key IS configured:**

- Begin Phase 1

---

## Phase 0: Silent Config Check

Run silently — do NOT ask questions yet.

### 0.1: Ensure Directory Structure

```bash

mkdir -p .infographic/images

mkdir -p .infographic/prompts

```

### 0.2: Check for API Key

Check if the GEMINI_API_KEY exists. Check BOTH the environment variable AND the `.env` file:

```bash

# Check environment variable first, then .env file

if [ -n "$GEMINI_API_KEY" ]; then

echo "API key found in environment"

elif [ -f .env ] && grep -q "^GEMINI_API_KEY=.\+" .env; then

echo "API key found in .env file"

else

echo "API key not configured"

fi

```

**Why check both?** The MCP server uses `dotenv` to load `.env` automatically at startup. So even if the bash shell doesn't have the env var set, the MCP server reads it from `.env` directly. If the key exists in `.env`, the MCP server has it.

**CRITICAL DECISION POINT:**

- If found (in env var OR `.env` file): Proceed silently to Phase 1

- If NOT found in either: **IMMEDIATELY jump to Phase 4 (API Key Setup)**

- Do NOT proceed to Phase 1

- Do NOT ask about content

- Do NOT try to generate

- Go directly to Phase 4 to get the API key from the user

**Note:** Do NOT use `get_configuration_status` MCP tool - it gives false positives.

### 0.3: Check for Brand Config

```bash

if [ -f .infographic/brand.md ]; then

cat .infographic/brand.md

fi

```

If brand config exists, acknowledge briefly:

```

I found your saved settings. Ready to create your infographic!

```

If nothing exists, proceed to Phase 1.

---

```

```

Use `AskUserQuestion`:

```

options:

```

Use `AskUserQuestion`:

```

question: "Where will this be posted?"

header: "Platform"

options:

- label: "LinkedIn (Recommended)"

description: "4:5 portrait, optimized for feed engagement"

- label: "Instagram"

description: "1:1 square or 4:5 portrait"

- label: "Twitter/X"

description: "16:9 landscape for timeline"

- label: "Presentation"

description: "16:9 landscape for slides"

```

---

```

```

```

options:

```

---

```

```

```

options:

```

```

```

```

question: "Does this content mapping look right?"

header: "Mapping"

options:

- label: "Yes, looks good"

- label: "Adjust the mapping"

description: "I'll tell you what to change"

- label: "Try a different approach"

```

---

## Phase 4: API Key Setup

**Goal:** Ensure the Gemini API key is configured in the Nano Banana MCP server.

### 4.1: Check for API Key

Before generating, check if the GEMINI_API_KEY exists in the environment or `.env` file:

```bash

if [ -n "$GEMINI_API_KEY" ]; then

echo "API key found in environment"

elif [ -f .env ] && grep -q "^GEMINI_API_KEY=.\+" .env; then

echo "API key found in .env file"

else

echo "API key not configured"

fi

```

### If Key IS Found (env var OR .env file) → Skip to Phase 5

The MCP server uses `dotenv` to load `.env` automatically. If the key is in `.env`, the MCP server has it.

### If Key NOT Found in Either

Ask the user how they want to proceed:

Use `AskUserQuestion`:

```

question: "I need a Gemini API key to generate the image. How do you want to proceed?"

header: "API Key"

options:

- label: "Set it up now (Recommended)"

description: "I'll guide you through getting a free key from Google AI Studio"

- label: "I have a key ready"

description: "Let me paste it"

- label: "Skip for now"

description: "Just give me the prompt to use elsewhere"

```

### Path A: Set Up Now (Guided Setup)

Present these instructions:

```

To get your free Gemini API key:

1. Go to Google AI Studio: https://aistudio.google.com

2. Sign in with your Google account

3. Click "Get API Key" in the left sidebar

4. Click "Create API Key" and select a project (or create a new one)

5. Copy the generated key (starts with "AIza...")

Paste your API key below when ready.

```

Wait for user to provide the key, then proceed to **Save the Key**.

### Path B: User Has Key Ready

```

Great! Paste your Gemini API key below.

```

Wait for user to provide the key, then proceed to **Save the Key**.

### Save the Key (After Path A or B)

Once user provides the key:

1. **Save to `.env` file:**

```bash

# Create .env if it doesn't exist

if [ ! -f .env ]; then

cat > .env <<'EOF'

# BenAI Skills - API Keys Configuration

# ============================================================================

# Marketing Plugin

# ============================================================================

# GEMINI_API_KEY - Required for /infographic skill

GEMINI_API_KEY=

GEMINI_IMAGE_MODEL=gemini-3-pro-image-preview

# APIFY_TOKEN - Required for /seo-audit and /programmatic-seo skills

APIFY_TOKEN=

EOF

fi

# Update the GEMINI_API_KEY line

sed -i '' "s|^GEMINI_API_KEY=.*|GEMINI_API_KEY=[user-provided-key]|" .env

# Add .env to .gitignore for security

echo ".env" >> .gitignore 2>/dev/null || true

```

2. **Confirm to user and EXIT THE SKILL:**

```

The Nano Banana MCP server uses dotenv to read .env automatically at startup.

After restart, your key will be loaded and ready.

Steps:

1. Restart Claude Code

2. Run /infographic again

3. It will work!

```

**CRITICAL:** After showing this message, the skill MUST EXIT. Do NOT:

- Call `configure_gemini_token` MCP tool (creates unwanted .nano-banana-config.json)

- Call `get_configuration_status` MCP tool (gives false positives)

- Proceed to generation

- Continue the workflow in any way

The MCP server needs to restart to load .env via dotenv. Exit the skill now.

### Path C: Skip for Now

```

No problem! I'll complete all the planning phases and give you a ready-to-use prompt at the end.

You can then:

- Paste it into Google AI Studio (aistudio.google.com)

- Use it with other image generation tools

- Come back later with /infographic after getting your API key

Let's continue with the design...

```

---

### 5.1: Craft the Prompt

### 5.2: Show Prompt for Approval

```

Here's the prompt I'll use:

---

[Full prompt text]

---

```

Use `AskUserQuestion`:

```

question: "Ready to generate with this prompt?"

header: "Prompt"

options:

- label: "Yes, generate"

description: "Looks good, go ahead"

- label: "Tweak the prompt"

description: "I want to adjust something before generating"

- label: "Start over"

description: "Go back to concept selection"

```

### 5.3: Generate

```

Call tool: generate_image

```

### 5.4: Copy and Display (CRITICAL)

```bash

mkdir -p .infographic/images

cp "./generated_imgs/[returned-filename]" ".infographic/images/[topic-slug]-v1.png"

```

**IMMEDIATELY display to user using Read tool:**

```

Read file: .infographic/images/[topic-slug]-v1.png

```

The user MUST see the image to give feedback.

### If No API Key (Skip Path)

Save the prompt to `.infographic/prompts/[topic]-prompt.md` with manual instructions:

```

To generate:

1. Go to aistudio.google.com

2. Select "Gemini" model

3. Paste the prompt

4. Click Generate

5. Download the image

```

---

```

header: "Reaction"

options:

```

Use `AskUserQuestion` with multiSelect:

```

header: "Changes"

multiSelect: true

options:

```

### 6.3: Apply Edits

**First edit:**

```

Call tool: edit_image

Parameters: {

"imagePath": ".infographic/images/[topic]-v1.png",

"prompt": "Edit this infographic:\n1. [Change 1]\n2. [Change 2]\nKeep everything else exactly the same."

}

```

**Subsequent edits:**

```

Call tool: continue_editing

Parameters: { "prompt": "[further changes]" }

```

After each edit:

1. Copy from `./generated_imgs/[returned-filename]` to `.infographic/images/[topic]-v[N].png`

2. Display using Read tool

3. Ask if changes are correct

Repeat until user approves. Save final version as `[topic]-final.png`.

---

## Phase 7: Wrap Up

```

Your infographic is ready!

Saved to:

Want to visualize another concept from your content? (I had [N] other suggestions from Phase 2.)

```

---

### Colors

| Role | Color | Hex |

|------|-------|-----|

| Primary text | Dark | #020309 |

| Light backgrounds / text on dark | Light yellow | #FAF3E3 |

| Subtle backgrounds | Light blue | #E5F5F9 |

### Typography

| Element | Font | Fallback |

|---------|------|----------|

| Headings (24pt+) | Space Grotesk | Montserrat → Arial |

| Body text | Montserrat | Georgia |

### Shape & Accent Styling

| Property | Rule |

|----------|------|

| Shadows | **Solid / hard shadows only** — 0 blur (`8px, 8px, 0px #000`) |

| Borders | **Solid borders** — 2px width |

| Border radius | **Slightly rounded** — must NOT look fully round |

| Accent colors | Cycle through yellow (#FDEEC4), blue (#E5F5F9), and green (#D2ECD0) |

### Footer

---

## File Naming

| Stage | Pattern | Example |

|-------|---------|---------|

| Series | `[topic]-01-v1.png` | `tips-01-v1.png` |

| Prompts | `[topic]-prompt.md` | `.infographic/prompts/tips-prompt.md` |

---

## Directory Structure

```

.infographic/

├── brand.md # Saved brand config (optional, for overrides)

├── images/ # All generated infographics

│ ├── topic-v1.png

│ ├── topic-v2.png

│ └── topic-final.png

└── prompts/ # Saved prompts (for no-key fallback)

└── topic-prompt.md

```

---

## Important Rules