PR Strategy & Planning

Public relations

by kostja94 · MIT license · ★ 1,006 on GitHub

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…

---
name: public-relations
description: 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.
metadata:
  version: 1.1.0
---

# 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:

Overview

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.

What you get

Headlineand subheadline
Leadparagraph
Bodycopy
Quotesuggestion
Boilerplate

Manual install (npx, ZIP)

Claude Codenpx skills add kostja94/marketing-skills --skill public-relations -g -a claude-code

Claude Code (degit)

npx degit kostja94/marketing-skills/skills/channels/partnerships/public-relations#main ~/.claude/skills/public-relations-kostja94

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.8 KB

Read SKILL.md here

kostja94/main1 file shown

SKILL.md2.8 KB

Browse every file on GitHub↗

SKILL.md

Show the full text69 lines

public-relations-kostja94/SKILL.md69 lines · 2.8 KB

PreviewCode

Outline

RawView on GitHub

Channels: Public 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

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

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 channel

1	---
2	name: public-relations
3	description: 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.
4	metadata:
5	version: 1.1.0
6	---
7
8	# Channels: Public Relations
9
10	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.
11
12	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.
13
14	## Initial Assessment
15
16	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.
17
18	Identify:
19	1. News angle: Product launch, funding, partnership, milestone
20	2. Audience: Trade press, mainstream, bloggers
21	3. Timing: Embargo or immediate
22
23	## Press Release Structure
24
25	\| Section \| Guideline \|
26	\|---------\|-----------\|
27	\| Header \| Logo; contact (name, title, email, phone); "FOR IMMEDIATE RELEASE" or embargo \|
28	\| Headline \| Under 100 chars; strong action verbs; "Why should I care?" \|
29	\| Subheadline \| Optional; additional context \|
30	\| Dateline \| City, state, date \|
31	\| Lead \| 50–75 words; all 5 W's (Who, What, When, Where, Why) \|
32	\| Body \| 1–2 paragraphs; inverted pyramid; most newsworthy first \|
33	\| Quote \| Executive/stakeholder; perspective, not fact repetition \|
34	\| Boilerplate \| 2–3 sentence company description \|
35	\| Media contact \| Name, email, phone \|
36
37	## Lead Paragraph
38
39	Journalist should understand the full story from the lead alone. Specific details, not vague language ("important update" → what changed and impact).
40
41	## Quote Quality
42
43	- Add perspective or emotion
44	- Avoid generic corporate-speak
45	- Don't repeat facts already stated
46
47	## Writing Style
48
49	- AP style
50	- Short paragraphs (one idea each)
51	- Clear language for easy journalist adaptation
52	- Data and context to support claims
53
54	## Output Format
55
56	- Headline and subheadline
57	- Lead paragraph
58	- Body copy
59	- Quote suggestion
60	- Boilerplate
61
62	## Related Skills
63
64	- media-kit-page-generator: Media kit for press (assets)
65	- press-coverage-page-generator: Aggregation of coverage; outcome of PR; "As Seen In"
66	- branding: Brand voice for PR copy
67	- cold-start-strategy: Product Hunt, launch channels
68	- product-launch: GTM; PR as launch channel
69