visual-content
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.
Best use case
visual-content is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using visual-content should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/visual-content/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How visual-content Compares
| Feature / Agent | visual-content | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
AI Agent for YouTube Script Writing
Find AI agent skills for YouTube script writing, video research, content outlining, and repeatable channel production workflows.
SKILL.md Source
# Content: Visual Content 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. ## Scope - **When to use images**: By content type and format - **Specs by context**: Website vs social vs email - **Platform image specs**: X, LinkedIn, Pinterest, Instagram, Facebook, YouTube - **Repurposing**: One visual → multiple formats and channels - **Visual-first planning**: Content calendar with image planning ## Initial Assessment **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: 1. **Context**: Article, social post, infographic, email, landing page 2. **Channels**: Which platforms will use this visual 3. **Repurposing**: Will this visual be adapted for other formats? --- ## 1. When to Use Images | 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** | --- ## 2. Website vs Social vs Email | 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** | --- ## 3. Platform Image Specs (Social) | 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. --- ## 4. Visual Repurposing **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**). --- ## 5. Visual-First Content Planning - **Plan images in content calendar**: Don't add visuals as afterthought; visuals drive engagement - **Batch by theme**: Create visuals for a topic cluster or campaign together for consistency - **Repurposing column**: In calendar, note which core piece becomes which visual format for which channel - **Asset library**: Organize by campaign/theme; tag for reuse --- ## 6. Format-Specific Notes ### Infographics - **Dimensions**: 800–1200px width; height varies by content - **Export**: PNG for web; PDF for download - **Repurpose**: Slice into 3–5 slides for LinkedIn carousel; single stat for X/Instagram ### Social Post Images - **Text overlay**: Keep minimal; many platforms deprecate text-heavy images - **Branding**: Logo in corner; consistent with **brand-visual-generator** - **Alt text**: Add for LinkedIn, Pinterest, X (accessibility + Pinterest SEO); see **image-optimization** for alt best practices ### Article / Blog Images - **Hero**: Often LCP candidate; optimize per **image-optimization** - **In-article**: Support narrative; alt text, captions per **image-optimization** - **Screenshots**: Annotate when helpful; keep file size low --- ## Output Format - **Visual plan** (what images for what content) - **Specs** by context (platform dimensions, format) - **Repurposing** map (one visual → multiple outputs) - **References** to platform skills and image-optimization ## Related Skills ### Content & Strategy - **content-marketing**: Content types, formats, repurposing; visual content is part of content mix - **content-strategy**: SEO topic clusters; article visuals - **copywriting**: Copy pairs with visuals; headlines for image posts ### Platform (Image Specs) - **twitter-x-posts**: X post image specs - **linkedin-posts**: LinkedIn image specs - **pinterest-posts**: Pinterest Pin dimensions, alt text - **reddit-posts**: Reddit image post context ### Website & SEO - **image-optimization**: Web images (alt, captions, WebP, LCP, responsive); central skill for image SEO - **open-graph, twitter-cards**: Link preview images - **hero-generator**: Hero section visuals ### Other - **brand-visual-generator**: Typography, colors, imagery tone; visual consistency - **video-marketing**: Video thumbnails; video as visual format - **video-optimization**: Video SEO; VideoObject; video sitemap; YouTube prioritization
Related Skills
content-marketing
When the user wants to plan content marketing across channels, define content types and formats, or create a content repurposing strategy. Also use when the user mentions "content marketing strategy," "content types," "content formats," "content repurposing," "content calendar," "content mix," "owned content," "content distribution," "content funnel," or "content planning across channels." For SEO calendar, use content-strategy.
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.
content-optimization
When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content structure." For keywords, use keyword-research.
article-content
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
brand-visual-generator
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font choices," "spacing system," "design tokens," "motion," "distinctive design," "frontend aesthetics," "PowerPoint theme," "Google Slides brand," or "slide master colors." For brand story, positioning, and voice, use branding.
employee-generated-content
When the user wants to plan, implement, or optimize employee-generated content (EGC) or employee advocacy. Also use when the user mentions "EGC," "employee advocacy," "employee content," "internal brand ambassadors," "employee social media," "employee advocacy program," "staff advocacy," "LinkedIn employee posts," or "brand ambassador program." For LinkedIn, use linkedin-posts.
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.