skillboardUpdated every 6 hours
skillboardWhen 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.
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.
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 for company story and key messages.
Identify:
| 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.
| 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 |
| 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.
| 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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/press-coverage · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/press-coverage"
cp -r "skills/pages/marketing/press-coverage" ".claude/skills/press-coverage"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.