media-kit-page-generator
The media-kit-page-generator skill creates and optimizes media kit and press pages that provide journalists with self-service brand assets, company information, and key contacts. Use this skill when building or improving a media kit, press kit, or press resources page, or when the user mentions related terms like brand assets, logo downloads, or press resources. It differs from press coverage aggregation by focusing on providing assets and company information rather than collecting third-party mentions.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/media-kit-page-generator && cp -r /tmp/media-kit-page-generator/skills/pages/marketing/media-kit ~/.claude/skills/media-kit-page-generatorSKILL.md
# Pages: Media Kit
Guides media kit and press page content, structure, and accessibility for journalists. Media kits provide self-service brand assets; consistent presentation builds trust (companies with strong guidelines are 20% more valuable). **Distinct from press-coverage-page-generator**: Media kit = assets for journalists; press coverage = aggregation of third-party mentions for visitor trust.
**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.
## Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for company story, metrics, key messages, and Section 12 (Visual Identity).
Identify:
1. **Audience**: Journalists, bloggers, analysts
2. **Update frequency**: Before launches, events, announcements
3. **Assets**: Logos, brand guidelines, favicon, photos, videos
## Best Practices
### Essential Elements
**Evergreen content:**
- Company overview (background, mission, origin)
- Key team bios and headshots
- High-res logos (multiple sizes, light/dark backgrounds, transparent PNG)
- Brand guidelines document (typography, colors, logo usage)
- Key statistics (customers, growth, metrics)
**Regularly updated:**
- Recent press releases
- Product photos and video clips
- Link to press coverage page (or "As Seen In" section) for media mentions
- Contact for press inquiries
**Note**: Press coverage (third-party mentions) is often a separate page or section. See **press-coverage-page-generator** for aggregating "As Seen In" / "In the News" content.
### Logo Assets (per Alignify-style media kit)
| Asset | Format | Use |
|-------|--------|-----|
| **Main logo** | PNG, SVG; light and dark bg | Primary branding |
| **Icon** | PNG; light and dark bg | Favicon, social, compact use |
| **Brand pattern** | PNG | Visual identity element |
| **Brand guidelines** | PDF or PNG | Typography, colors, usage rules |
### Usage Guidelines
**Allowed**: Media coverage, blog posts, social sharing, product comparisons, educational use. Assets free to download without additional authorization.
**Requirements**: Maintain logo proportions and colors; ensure adequate white space; do not use in contexts that harm brand. For commercial or special use, contact for authorization.
### Media Assets
| Asset | Format |
|-------|--------|
| **Logos** | PNG (transparent), SVG; horizontal and square |
| **Photos** | High-res; horizontal for web, square for social |
| **Videos** | Product demos, interviews |
| **Credits** | Photo credits, usage rights |
### Structure
- **Dedicated page**: Press/Media section on website
- **Self-service**: Journalists find what they need without emailing
- **Concise**: 3-4 pages typical; each element adds value
- **Downloadable**: ZIP or individual asset downloads
### Timing
- **Update before**: Launches, events, announcements
- **Keep current**: Stale info damages credibility
### Placement
- **Discoverable**: Link in footer, About, or dedicated Press section
- **Clear label**: "Press," "Media Kit," "For Journalists"
## Output Format
- **Structure** outline
- **Asset** checklist (logos, brand guidelines, favicon, photos, bios)
- **Copy** for company overview
- **Usage guidelines** (allowed, requirements)
- **Contact** for press inquiries
- **SEO**: Often noindex; or index for "company name press" queries
## Related Skills
- **press-coverage-page-generator**: Aggregation of third-party coverage ("As Seen In"); media kit can link to it; distinct (media kit = assets for journalists; press coverage = social proof for visitors)
- **about-page-generator**: Media kit extends About for press
- **contact-page-generator**: Press contact info
- **customer-stories-page-generator**: Press may reference case studies
- **logo-generator**: Logo assets, placement rules; media kit hosts logo files
- **favicon-generator**: Favicon for browser/app; media kit can link or include
- **brand-visual-generator**: Typography, colors, spacing; brand guidelines document
- **indexing**: noindex vs. index for press page
- **directory-submission**: Media kit required for Product Hunt and directory submissionsWhen 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 Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
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 "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
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," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.