press-coverage-page-generator
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.
Best use case
press-coverage-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using press-coverage-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/press-coverage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How press-coverage-page-generator Compares
| Feature / Agent | press-coverage-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 PRRelated Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.