public-relations
This skill guides the creation and strategy of press releases and media relations by applying journalist-focused best practices. Use it when drafting press releases, planning product announcements, building media outreach campaigns, or discussing PR strategy. It provides structured templates for headlines, leads, body copy, and quotes, along with guidance on news angles, audience targeting, and timing to increase the likelihood that journalists will use the release.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/public-relations && cp -r /tmp/public-relations/skills/channels/partnerships/public-relations ~/.claude/skills/public-relationsSKILL.md
# Channels: Public Relations
Guides PR and press release strategy. Journalists use ~3% of releases they receive; proper structure is critical. Use this skill when writing press releases, planning product announcements, or building media relations.
**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 Sections 2 (Positioning), 3 (Value Proposition), 8 (Brand & Voice).
Identify:
1. **News angle**: Product launch, funding, partnership, milestone
2. **Audience**: Trade press, mainstream, bloggers
3. **Timing**: Embargo or immediate
## Press Release Structure
| Section | Guideline |
|---------|-----------|
| **Header** | Logo; contact (name, title, email, phone); "FOR IMMEDIATE RELEASE" or embargo |
| **Headline** | Under 100 chars; strong action verbs; "Why should I care?" |
| **Subheadline** | Optional; additional context |
| **Dateline** | City, state, date |
| **Lead** | 50–75 words; all 5 W's (Who, What, When, Where, Why) |
| **Body** | 1–2 paragraphs; inverted pyramid; most newsworthy first |
| **Quote** | Executive/stakeholder; perspective, not fact repetition |
| **Boilerplate** | 2–3 sentence company description |
| **Media contact** | Name, email, phone |
## Lead Paragraph
Journalist should understand the full story from the lead alone. Specific details, not vague language ("important update" → what changed and impact).
## Quote Quality
- Add perspective or emotion
- Avoid generic corporate-speak
- Don't repeat facts already stated
## Writing Style
- AP style
- Short paragraphs (one idea each)
- Clear language for easy journalist adaptation
- Data and context to support claims
## Output Format
- **Headline** and subheadline
- **Lead** paragraph
- **Body** copy
- **Quote** suggestion
- **Boilerplate**
## Related Skills
- **media-kit-page-generator**: Media kit for press (assets)
- **press-coverage-page-generator**: Aggregation of coverage; outcome of PR; "As Seen In"
- **branding**: Brand voice for PR copy
- **cold-start-strategy**: Product Hunt, launch channels
- **product-launch**: GTM; PR as launch channelWhen 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.