Visual Content
Plan channel-specific image specs, repurposing, and visual-first slots in a content calendar without guessing platform dimensions.
Overview
Visual Content is an agent skill most often used in Grow (also Launch, Validate) that plans, specs, and repurposes images and infographics across web, social, and email.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill visual-contentWhat is this skill?
- Maps when to use images by content type and format across website, social, and email
- Platform image specs for X, LinkedIn, Pinterest, Instagram, Facebook, and YouTube
- Repurposing workflow: one visual → multiple formats and channels
- Visual-first planning hooks into content calendars for higher engagement
- Reads `.claude/project-context.md` or `.cursor/project-context.md` when present for brand alignment
- Covers 6 named social platforms plus website and email contexts
- 4 scope pillars: when to use images, specs, repurposing, visual-first planning
Adoption & trust: 1.1k installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are publishing across channels but keep resizing the wrong assets, missing specs, and treating visuals as an afterthought in the calendar.
Who is it for?
Solo builders running multi-channel content who want spec-correct social and web visuals and a clear one-to-many repurposing plan.
Skip if: Teams that only need Pinterest post strategy—use pinterest-posts—or already have a locked brand kit and production pipeline with no repurposing gaps.
When should I use this skill?
User wants to plan, create, or repurpose visual content or mentions content images, infographics, social post images, image specs, or visual repurposing.
What do I get? / Deliverables
You get context-aware visual plans with per-platform specs, repurposing paths, and calendar-ready image decisions aligned to project context when available.
- Per-context and per-platform image spec recommendations
- Repurposing map from a primary visual to derivative formats
- Visual-first content calendar guidance aligned to engagement goals
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because the skill centers on ongoing engagement visuals, calendars, and cross-channel repurposing—not a one-time ship checklist. Content subphase matches visual-first planning, infographics, and social/email/website asset workflows called out in scope.
Where it fits
Define hero, thumbnail, and social preview image specs before publishing a validation landing page.
Batch-export launch announcement visuals sized for X, LinkedIn, and YouTube community posts.
Slot visual-first themes into the monthly calendar and map one infographic into email header plus three social crops.
Repurpose a product screenshot set into onboarding email banners and re-engagement social cards with consistent crops.
How it compares
Channel planning and spec guidance for visuals—not generative image creation tools or Pinterest-only post playbooks.
Common Questions / FAQ
Who is visual-content for?
Indie founders, marketers-of-one, and small teams who create their own social, email, and site visuals and need correct dimensions and repurposing without a design ops function.
When should I use visual-content?
Use it when planning content images, infographics, or social post art; during Launch distribution prep; in Grow content calendar work; or at Validate when landing pages need hero and OG-style visuals with consistent specs.
Is visual-content safe to install?
It is procedural guidance that may read local project context files; review the Security Audits panel on this catalog page and inspect the skill package before enabling filesystem access in your agent.
SKILL.md
READMESKILL.md - Visual Content
# 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*