skills/content/visual-content/SKILL.md
When the user wants to plan, create, or repurpose visual content (images, infographics, social post images) across channels. Also use when the user mentions "content images," "social media images," "infographic," "visual content," "post image," "image specs," "visual repurposing," "content visuals," or "image for social post." For Pinterest, use pinterest-posts.
npx skillsauth add kostja94/marketing-skills visual-contentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guides visual content planning and creation across website, social media, email, and other channels. Images are needed not just for websites—social posts, infographics, and repurposed content all require visuals. Visual-first planning in content calendars improves engagement; cross-channel consistency and repurposing maximize ROI.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Section 12 (Visual Identity) for brand consistency.
Identify:
| Content Type | Visual Need | Notes | |--------------|-------------|-------| | Article / Blog | Hero image, in-article images, screenshots | See image-optimization for web (alt, WebP, LCP) | | Social post | Single image, carousel, or link preview | Platform-specific specs below | | Infographic | Primary format; data visualization | Repurpose to social (cropped), blog (full) | | Case study | Customer photo, results chart, logo | Repurpose to LinkedIn carousel, blog | | Product update | Screenshot, feature graphic | Changelog, email, social | | Email | Header image, inline graphics | Keep lightweight; many clients block images | | Landing page | Hero, trust badges, screenshots | See hero-generator, image-optimization |
| Context | Priority | Skill | |---------|----------|-------| | Website | Alt text, WebP, LCP, responsive, lazy loading | image-optimization | | Social posts | Platform dimensions, aspect ratio, file size | Platform skills (X, LinkedIn, Pinterest, etc.) | | OG / Twitter Cards | 1200×630, 1200×675 for link previews | open-graph, twitter-cards | | Email | Inline-friendly; avoid heavy images; alt for blocked | email-marketing |
| Platform | Post Image | Stories / Reels | Profile | Notes | |----------|------------|-----------------|---------|-------| | X (Twitter) | 1200×675 (16:9), 800×800 | — | 400×400 | See twitter-x-posts | | LinkedIn | 1200×627, 1200×1200; carousel up to 20 | — | 400×400 | See linkedin-posts; vertical preferred on mobile | | Pinterest | 1000×1500 (2:3) | — | 165×165 | Alt text ~25% more impressions; see pinterest-posts | | Instagram | 1080×1350 (4:5), 1080×1080 | 1080×1920 (9:16) | 320×320 | 4:5 outperforms square on feed | | Facebook | 1200×630, 1080×1080 | 1080×1920 | 320×320 | | | YouTube | Thumbnail 1280×720 | — | 800×800 | |
General: 1080px width works across most platforms; vertical (4:5, 9:16) outperforms square on mobile-first feeds. Keep critical elements (logo, text) in safe center—platforms may crop.
Principle: One core visual → multiple crops/formats → multiple channels.
| Core Visual | Adaptations | Channels | |-------------|-------------|----------| | Infographic | Full (blog), cropped sections (Instagram, LinkedIn carousel), square (X) | Blog, LinkedIn, Instagram, X | | Case study graphic | Hero (blog), single slide (LinkedIn), story (Instagram) | Blog, LinkedIn, Instagram | | Product screenshot | Hero (landing), post (X, LinkedIn), email header | Website, social, email | | Quote graphic | Square (X, LinkedIn), 4:5 (Instagram) | X, LinkedIn, Instagram |
Workflow: Design at largest needed size; export platform-specific crops. Use consistent colors, fonts, logo placement (see brand-visual-generator).
testing
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
development
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
testing
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.