agentleFS
dalrootdalroot/agentic-seo/skills/content/visual-content/SKILL.md

visual-content

Skill23 starsChanged 2 months agoMITView on GitHub

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.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Section 12 (Visual Identity) for …

    line 24
  2. Distinctive:

    Plan images in content calendar: Don't add visuals as afterthought.

    line 90
  3. Distinctive:

    Batch by theme: Create visuals for a topic cluster or campaign together for consistency

    line 91
  4. Distinctive:

    Text overlay: Keep minimal; many platforms deprecate text-heavy images

    line 107
  5. Distinctive:

    Alt text: Add for LinkedIn, Pinterest, X (accessibility + Pinterest SEO).

    line 109

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 TypeVisual NeedNotes
Article / BlogHero image, in-article images, screenshotsSee image-optimization for web (alt, WebP, LCP)
Social postSingle image, carousel, or link previewPlatform-specific specs below
InfographicPrimary format; data visualizationRepurpose to social (cropped), blog (full)
Case studyCustomer photo, results chart, logoRepurpose to LinkedIn carousel, blog
Product updateScreenshot, feature graphicChangelog, email, social
EmailHeader image, inline graphicsKeep lightweight; many clients block images
Landing pageHero, trust badges, screenshotsSee hero-generator, image-optimization

2. Website vs Social vs Email

ContextPrioritySkill
WebsiteAlt text, WebP, LCP, responsive, lazy loadingimage-optimization
Social postsPlatform dimensions, aspect ratio, file sizePlatform skills (X, LinkedIn, Pinterest, etc.)
OG / Twitter Cards1200×630, 1200×675 for link previewsopen-graph, twitter-cards
EmailInline-friendly; avoid heavy images; alt for blockedemail-marketing

3. Platform Image Specs (Social)

PlatformPost ImageStories / ReelsProfileNotes
X (Twitter)1200×675 (16:9), 800×800—400×400See twitter-x-posts
LinkedIn1200×627, 1200×1200; carousel up to 20—400×400See linkedin-posts; vertical preferred on mobile
Pinterest1000×1500 (2:3)—165×165Alt text ~25% more impressions; see pinterest-posts
Instagram1080×1350 (4:5), 1080×10801080×1920 (9:16)320×3204:5 outperforms square on feed
Facebook1200×630, 1080×10801080×1920320×320
YouTubeThumbnail 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 VisualAdaptationsChannels
InfographicFull (blog), cropped sections (Instagram, LinkedIn carousel), square (X)Blog, LinkedIn, Instagram, X
Case study graphicHero (blog), single slide (LinkedIn), story (Instagram)Blog, LinkedIn, Instagram
Product screenshotHero (landing), post (X, LinkedIn), email headerWebsite, social, email
Quote graphicSquare (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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.