/press-coverage
When the user wants to create a press coverage page, "As Seen In" section, or media mentions aggregation. Also use when the user mentions "press coverage," "media mentions," "as seen in," "as featured in," "in the news," "press mentions," "media coverage page," or "trusted by
$ npx -y skills add kostja94/marketing-skills --skill press-coverage --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/press-coverage
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to create a press coverage page, "As Seen In" section, or media mentions aggregation. Also use when the user mentions "press coverage," "media mentions," "as seen in," "as featured in," "in the news," "press mentions," "media coverage page," or "trusted by
SKILL.md
press-coverage.SKILL.mdname: press-coverage-page-generator
description: When the user wants to create a press coverage page, "As Seen In" section, or media mentions aggregation. Also use when the user mentions "press coverage," "media mentions," "as seen in," "as featured in," "in the news," "press mentions," "media coverage page," or "trusted by publications." For pitching journalists and press releases, use public-relations.
metadata:
version: 1.1.0
Pages: Press Coverage
Guides press coverage and media mentions aggregation—showcasing third-party coverage from authoritative sites to build trust. Optional page; when coverage is sparse, implement as a small "As Seen In" or "As Featured In" section on homepage or elsewhere. Distinct from **media-kit-page-generator** (assets for journalists). For conceptual overview and comparison table, see [reference.md](reference.md).
**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 for company story and key messages.
Identify: 1. **Coverage volume**: Few mentions vs substantial 2. **Format**: Full page vs section 3. **Sources**: Publications, podcasts, awards, industry lists
Full Page vs Section
| Format | When to Use | Placement | |--------|-------------|-----------| | **Full page** | Substantial coverage (10+ mentions); journalists visit for expert contacts; "inbound PR" | /press, /news, /in-the-news | | **Section** | Sparse coverage (1–10); quick credibility; logo strip or quote carousel | Homepage below hero; About page; footer |
**Rule**: Homepage section = logos only, minimal, below main CTA. Full page = headlines, links, dates, contact.
Full Page Structure
| Element | Guideline | |---------|-----------| | **Coverage list** | Chronological or by publication; headline, outlet, date, link | | **Separation** | Press coverage (third-party) vs press releases (company-authored); coverage carries more credibility | | **Types** | News, podcasts, video features, awards, "Best X" lists | | **Contact** | Media inquiries; link to media kit | | **Dates** | Optional on evergreen content; omit to keep timeless |
Section Structure ("As Seen In" / "As Featured In")
| Element | Guideline | |---------|-----------| | **Logos** | Publication logos; high-contrast, consistent size | | **Placement** | Below hero/CTA; above fold or just below | | **Quote** | Optional: one compelling snippet; extract from best coverage | | **Link** | Optional: "See all coverage" → full page if exists |
**Avoid**: Clutter; too many logos; low-authority outlets that dilute trust.
Content Types to Aggregate
| Type | Example | |------|---------| | **News articles** | Forbes, Bloomberg, TechCrunch, industry trade | | **Podcasts** | Interview features, guest appearances | | **Video** | TV segments, YouTube features | | **Awards** | "Best X 2024," "Top 10 Startups" | | **Reviews** | Product reviews, roundups |
Trust Principles
- **Third-party > self-authored**: Media mentions beat press releases for credibility
- **Authority matters**: Forbes, Bloomberg > unknown blogs
- **Recency**: Recent coverage signals active business; update regularly
Output Format
- **Format** (full page vs section) recommendation
- **Structure** (elements, order)
- **Copy** (headline, intro if full page)
- **Placement** (URL, page location)
- **SEO**: Index for "company name press" / "company name news"; or noindex if thin
Related Skills
- **media-kit-page-generator**: Press assets for journalists; press coverage page can link to media kit; distinct purposes (coverage = social proof for visitors; media kit = assets for press)
- **homepage-generator**: "As Seen In" section often on homepage
- **about-page-generator**: Press quotes can appear on About
- **customer-stories-page-generator**: Social proof; different from press (customer success vs media coverage)
- **trust-badges-generator**: "Trusted by" logos; similar visual treatment
- **public-relations**: Press release creation; coverage is outcome of PR
Read more
name: press-coverage-page-generator description: When the user wants to create a press coverage page, "As Seen In" section, or media mentions aggregation. Also use when the user mentions "press coverage," "media mentions," "as seen in," "as featured in," "in the news," "press mentions," "media coverage page," or "trusted by publications." For pitching journalists and press releases, use public-relations. metadata: version: 1.1.0
Pages: Press Coverage
Guides press coverage and media mentions aggregation—showcasing third-party coverage from authoritative sites to build trust. Optional page; when coverage is sparse, implement as a small "As Seen In" or "As Featured In" section on homepage or elsewhere. Distinct from **media-kit-page-generator** (assets for journalists). For conceptual overview and comparison table, see [reference.md](reference.md).
**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 for company story and key messages.
Identify: 1. **Coverage volume**: Few mentions vs substantial 2. **Format**: Full page vs section 3. **Sources**: Publications, podcasts, awards, industry lists
Full Page vs Section
| Format | When to Use | Placement | |--------|-------------|-----------| | **Full page** | Substantial coverage (10+ mentions); journalists visit for expert contacts; "inbound PR" | /press, /news, /in-the-news | | **Section** | Sparse coverage (1–10); quick credibility; logo strip or quote carousel | Homepage below hero; About page; footer |
**Rule**: Homepage section = logos only, minimal, below main CTA. Full page = headlines, links, dates, contact.
Full Page Structure
| Element | Guideline | |---------|-----------| | **Coverage list** | Chronological or by publication; headline, outlet, date, link | | **Separation** | Press coverage (third-party) vs press releases (company-authored); coverage carries more credibility | | **Types** | News, podcasts, video features, awards, "Best X" lists | | **Contact** | Media inquiries; link to media kit | | **Dates** | Optional on evergreen content; omit to keep timeless |
Section Structure ("As Seen In" / "As Featured In")
| Element | Guideline | |---------|-----------| | **Logos** | Publication logos; high-contrast, consistent size | | **Placement** | Below hero/CTA; above fold or just below | | **Quote** | Optional: one compelling snippet; extract from best coverage | | **Link** | Optional: "See all coverage" → full page if exists |
**Avoid**: Clutter; too many logos; low-authority outlets that dilute trust.
Content Types to Aggregate
| Type | Example | |------|---------| | **News articles** | Forbes, Bloomberg, TechCrunch, industry trade | | **Podcasts** | Interview features, guest appearances | | **Video** | TV segments, YouTube features | | **Awards** | "Best X 2024," "Top 10 Startups" | | **Reviews** | Product reviews, roundups |
Trust Principles
- **Third-party > self-authored**: Media mentions beat press releases for credibility
- **Authority matters**: Forbes, Bloomberg > unknown blogs
- **Recency**: Recent coverage signals active business; update regularly
Output Format
- **Format** (full page vs section) recommendation
- **Structure** (elements, order)
- **Copy** (headline, intro if full page)
- **Placement** (URL, page location)
- **SEO**: Index for "company name press" / "company name news"; or noindex if thin
Related Skills
- **media-kit-page-generator**: Press assets for journalists; press coverage page can link to media kit; distinct purposes (coverage = social proof for visitors; media kit = assets for press)
- **homepage-generator**: "As Seen In" section often on homepage
- **about-page-generator**: Press quotes can appear on About
- **customer-stories-page-generator**: Social proof; different from press (customer success vs media coverage)
- **trust-badges-generator**: "Trusted by" logos; similar visual treatment
- **public-relations**: Press release creation; coverage is outcome of PR
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
Other skills on kostja94-marketing-skills.
- /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 Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
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,"
Open skill - /ai-traffic
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
Open skill - /traffic
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
Open skill - /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
Open skill - /community-forum
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,"
Open skill