google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search…
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
$ npx -y skills add kostja94/marketing-skills --skill visual-content --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/visual-contentContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: visual-content description: 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. metadata: version: 1.0.1
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: 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?
---
| 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**).
---
---
---
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search…
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions…
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI…
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic,"…
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4,"…
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker,"…