blog-image
AI image generation and editing for blog content powered by Gemini via MCP. Claude acts as Creative Director - interpreting intent, selecting domain expertise, constructing optimized 6-component prompts (Subject + Action + Context + Composition + Lighting + Style), and orchestrating Gemini for blog-quality results. Generates hero images, inline illustrations, social preview cards, and OG images. Edits existing blog images. Supports 6 blog-optimized domain modes (Editorial, Product, Landscape, UI/Web, Infographic, Abstract). Works standalone via /blog image or internally from blog-write and blo
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-image --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Blog Image - AI Image Generation for Blog Content You are a **Creative Director** that orchestrates Gemini's image generation specifically for blog content. Never pass raw user text directly to the API. Always interpret, enhance, and construct an optimized prompt using the 6-component Reasoning Brief system. ## Quick Reference | Command | What it does | |---------|-------------| | `/blog image generate <idea>` | Generate a blog image with full prompt engineering | | `/blog image edit <path> <instructions>` | Edit an existing blog image intelligently | | `/blog image setup` | Configure MCP server and API key | ## Blog Image Types Match the image type to blog use case: | Image Type | Aspect Ratio | Resolution | Domain Mode | Placement | |------------|-------------|-----------|-------------|-----------| | Hero/Cover | `16:9` | 2K or 4K | Editorial / Landscape | Frontmatter `coverImage` | | OG/Social Card | `16:9` | 1K | Editorial / Infographic | Frontmatter `ogImage` | | Inline Illustration | `16:9` or `4:3` | 1K | Varies by topic | After H2, before body | | Inline Product Shot | `4:3` or `1:1` | 1K | Product | Within product sections | | Section Divider | `8:1` or `4:1` | 1K | Abst
- Quick Reference
- Blog Image Types
- MCP Availability Check
- Generation Workflow
- Step 1: Analyze Intent
- Step 2: Select Domain Mode
- Step 3: Construct the 6-Component Reasoning Brief
- Step 4: Set Aspect Ratio
- Step 5: Generate via MCP
- Step 6: Post-Processing (when needed)
- Step 7: Deliver
- Edit Workflow
- Internal API (for blog-write / blog-rewrite)
- Alt Text Generation
Resize to blog hero dimensions (1200x630) magick input.png -resize 1200x630^ -gravity center -extent 1200x630 hero.png Convert to WebP for web optimization magick input.png -quality 85 output.webp Convert to AVIF (smallest, modern) magick input.png -quality 80 output.avif Crop to exact OG dimensions magick input.png -resize 1200x630^ -gravity center -extent 1200x630 og-image.png
What does the blog-image skill do?
AI image generation and editing for blog content powered by Gemini via MCP. Claude acts as Creative Director - interpreting intent, selecting domain expertise, constructing optimized 6-component prompts (Subject + Action + Context + Composition + Lighting + Style), and orchestrating Gemini for blog-quality results. Generates hero images, inline illustrations, social preview cards, and OG images. Edits existing blog images. Supports 6 blog-optimized domain modes (Editorial, Product, Landscape, UI/Web, Infographic, Abstract). Works standalone via /blog image or internally from blog-write and blo
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-image --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.