Public Relations
When the user wants to plan PR, write a press release, or manage media relations.
Install
npx skills add kostja94/marketing-skills --skill public-relations -g -a claude-code -y- Repository
- kostja94/marketing-skills1.1k
- Category
- Git and review
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 614 tokens
- Runs scripts
- No, instructions only
What it does
When the user wants to plan PR, write a press release, or manage media relations. Also use when the user mentions "public relations," "PR," "press release," "media relations," "news release," "journalist," "media coverage," "product announcement," or "earned media." For on-site "As Seen In" or logos page, use press-coverage-page-generator.
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
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
- News angle: Product launch, funding, partnership, milestone
- Audience: Trade press, mainstream, bloggers
- 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
