seo-image-gen skill

SEO Image Gen: AI Image Generation for SEO Assets (Extension)

Generate production-ready images for SEO use cases using Gemini's image generation via the banana Creative Director pipeline. Maps SEO needs to optimized domain modes, aspect ratios, and resolution defaults.

Architecture Note

This extension is built on Claude Banana, the standalone AI image generation skill for Claude Code.

This skill has two components with distinct roles:

• SKILL.md (this file): Handles interactive /seo image-gen commands for generating images
• Agent (agents/seo-image-gen.md): Audit-only analyst spawned during /seo audit to assess existing OG/social images and produce a generation plan (never auto-generates)

Prerequisites

This skill requires the banana extension to be installed:

./extensions/banana/install.sh

Check availability: Before using any image generation tool, verify the MCP server is connected by checking if geminigenerateimage or setaspectratio tools are available. If tools are not available, inform the user the extension is not installed and provide install instructions.

Quick Reference

SEO Image Use Cases

Each use case maps to pre-configured banana parameters:

Generation Pipeline

For every generation request:

1. Identify use case from command or context (og, hero, product, etc.)
2. Apply SEO defaults from the use cases table above
3. Set aspect ratio via setaspectratio MCP tool
4. Construct Reasoning Brief using the banana Creative Director pipeline:

• Use ${CLAUDESKILLDIR} as the installed skill root
• Load ${CLAUDESKILLDIR}/references/prompt-engineering.md for the 6-component system
• Apply domain mode emphasis (Subject 30%, Style 25%, Context 15%, etc.)
• Be SPECIFIC and VISCERAL: describe what the camera sees

1. Generate via geminigenerateimage MCP tool
2. Post-generation SEO checklist (see below)

Check for Presets

If the user mentions a brand or has SEO presets configured:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run --extension banana presets.py list

Load matching preset and apply as defaults. Also check ${CLAUDESKILLDIR}/references/seo-image-presets.md for SEO-specific preset templates.

Post-Generation SEO Checklist

After every successful generation, guide the user on:

1. Alt text:Write descriptive, keyword-rich alt text for the generated image
2. File naming:Rename to SEO-friendly format: keyword-description-widthxheight.webp
3. WebP conversion:Convert to WebP for optimal page speed:

magick output.png -quality 85 output.webp

1. File size:Target under 200KB for hero images, under 100KB for thumbnails
2. Schema markup:Suggest ImageObject schema for the generated image:

{
     "@type": "ImageObject",
     "url": "https://example.com/images/keyword-description.webp",
     "width": 1200,
     "height": 630,
     "caption": "Descriptive caption with target keyword"
   }

1. OG meta tags:For social preview images, remind about:

<meta property="og:image" content="https://example.com/images/og-image.webp" />
   <meta property="og:image:width" content="1200" />
   <meta property="og:image:height" content="630" />
   <meta property="og:image:alt" content="Descriptive alt text" />

Cost Awareness

Image generation costs money. Be transparent:

• Show estimated cost before generating (especially for batch)
• Log every generation: "${CLAUDEPLUGINROOT}/scripts/claude-seo" run --extension banana cost_tracker.py log --model MODEL --resolution RES --prompt "brief"
• Run cost_tracker.py summary if user asks about usage

Pricing is not hard-coded. Check current Google pricing at https://ai.google.dev/gemini-api/docs/pricing, store dated values in ~/.banana/pricing.json, and treat estimates as approximate.

Model Routing

Error Handling

Cross-Skill Integration

• seo-images (analysis) feeds into seo-image-gen (generation): audit results from /seo images identify missing or low-quality images; use those findings to drive /seo image-gen commands
• seo-audit spawns the seo-image-gen agent (not this skill) to analyze OG/social images across the site and produce a prioritized generation plan
• seo-schema can consume generated images: after generation, suggest ImageObject schema markup pointing to the new assets

Reference Documentation

Load on-demand. Do NOT load all at startup:

• ${CLAUDESKILLDIR}/references/prompt-engineering.md:6-component system, domain modes, templates
• ${CLAUDESKILLDIR}/references/gemini-models.md:Model specs, rate limits, capabilities
• ${CLAUDESKILLDIR}/references/mcp-tools.md:MCP tool parameters and responses
• ${CLAUDESKILLDIR}/references/post-processing.md:ImageMagick/FFmpeg pipeline recipes
• ${CLAUDESKILLDIR}/references/cost-tracking.md:Pricing, usage tracking
• ${CLAUDESKILLDIR}/references/presets.md:Brand preset management
• ${CLAUDESKILLDIR}/references/seo-image-presets.md:SEO-specific preset templates

Response Format

After generating, always provide:

1. Image path:where it was saved
2. Crafted prompt:show what was sent to the API (educational)
3. Settings:model, aspect ratio, resolution
4. SEO checklist:alt text suggestion, file naming, WebP conversion
5. Schema snippet:ImageObject or og:image markup if applicable