Write press releases for product launches, funding announcements, partnerships, executive hires, and milestones using the Inverted Pyramid (AP journalism) and Ogilvy on Headlines (David Ogilvy, Ogilvy on Advertising). The lede answers Who/What/When/Where/Why in 40 words or fewer. The headline selects the right audience and promises a specific benefit. Use when the user asks for a press release, media release, news announcement, PR for X, launch announcement, funding announcement, or "write a press release". Reads brand voice and positioning from knowledge/. For pitching it to a journalist, see pr-pitch-writer. For the customer story behind it, see case-study-writer.
Writes press releases in AP style using the Inverted Pyramid structure and Ogilvy's headline principles. Optimized for journalists who scan, not read. The most important information is always first. The headline selects the right audience and promises a concrete benefit - not a label.
Framework: Inverted Pyramid + Ogilvy on Headlines
Inverted Pyramid (AP journalism)
Put the most important information first, then supporting details, then background. The structure
exists because of how newsrooms work: journalists scan, and editors cut from the bottom to fit
space. If the news is in paragraph 4, it does not survive the cut.
Level
Paragraphs
Contains
Word budget
Survives an editor's cut?
Lede
1
Who, what, when, where, why - the whole story
40 or fewer
Never cut
Supporting detail
2 to 3
Why now, the problem solved, first quote
50 to 80 each
Usually kept
Background
4 to 6
Specifics, deal terms, second quote, what is next
30 to 80 each
Cut when space is tight
Boilerplate
last
About the company
50 to 80
Cut first, every time
Two tests, both run on the finished draft:
Lede test: can someone read only the first paragraph and understand the full story? If not, rewrite the lede rather than adding to paragraph 2.
Cut-from-the-bottom test: delete the last 2 paragraphs. Is the story still complete and accurate? It must be. If deleting them removes a fact the story needs, that fact is in the wrong place.
Ogilvy on Headlines (Ogilvy on Advertising, David Ogilvy, 1983)
"On average, five times as many people read the headline as read the body copy." Ogilvy's point is
that the headline is not a title, it is the ad. In a press release the headline is what decides
whether a journalist opens the email at all.
Ogilvy rule
Applied to a press release
Fails when
The headline selects the audience
The reader knows in one line whether this is their beat
It names the company and nothing else
The headline promises a benefit or creates curiosity
It states what someone can now do
It labels the topic: "Company Announces Product Update"
Never a blind headline
No wordplay the reader must decode
A pun carries the news
Specifics beat generalities
The round size, the number, the named thing
"Significant funding", "major partnership"
Ogilvy's best-performing headline formulas, in the order worth trying for a release:
News: announces something genuinely new, using a specific verb: Introduces, Launches, Names, Raises, Acquires
How-to: "How [company] [does X] for [audience]" - strongest for product launches with a clear job
Command: "Reduce [pain] by [specific amount]" - only with a number the user has supplied
Question: a question the target audience asks themselves - weakest here, because news beats curiosity for a journalist on deadline
Press release headline formula (AP plus Ogilvy combined):
[Company] [verb: announces/launches/names/raises] [specific thing], [immediate benefit or impact]
Example: "Threadline Raises $32M Series B to Help PLG Teams Ship Onboarding Without Engineering"
Audience selected: PLG teams
Benefit stated: ship onboarding without engineering
News verb used: Raises
Specific: $32M, Series B
The example above is a fictional company used to show the shape of the formula. Never carry any
figure from it into a real release.
Before you draft: is there enough to announce?
A press release with a thin news hook does not fail quietly, it burns a journalist relationship.
Signal
Threshold
If below
Attributed quotes supplied by the user
2, one internal and one external
Draft with [QUOTE NEEDED FROM <Name>, <Title>] in place and tell the user the release cannot go out until both are real
Hard facts: figures, dates, names, titles
All confirmed by the user
Stop on the unconfirmed one. Ask. Never draft a round size, a customer count, a founding year, or an HQ city
Boilerplate in knowledge/company.md
Present
Ask the user for it. Do not assemble one from the positioning doc, because boilerplate is a legal and factual statement, not marketing copy
Something a reader can do or get that they could not before
1 required
Say plainly that this is an internal milestone, not news, and offer a LinkedIn post or a customer email instead. That is a better outcome than a release nobody covers
Warning signs, in priority order:
The headline needs the subheadline to make sense. The headline is doing labelling, not news.
Every number in the draft came from the skill rather than the user. Stop and get them confirmed, one by one.
The lede is the headline rewritten. It must add the five Ws the headline omits.
The most interesting sentence is in paragraph 5. The pyramid is upside down, so restructure before polishing.
When to use
"Write a press release for our Series B"
"Draft a media release announcing the partnership with X"
"Write the launch announcement for "
"We need a press release for the new CMO hire"
Release types this skill handles
Product launch
Funding round
Partnership / integration
Executive hire or appointment
Customer milestone (Xth customer, $Y ARR, etc.)
Acquisition (buyer side or sell side)
Award or certification
Inputs needed (ask if missing)
Type of release (from list above)
Headline news (the one sentence)
Date and dateline city
Key facts: numbers, names, titles, dates
Quote 1 (executive at company): name, title, full quote
Boilerplate: pull from knowledge/company.md. If missing, ask the user - never draft a founding year, HQ city, customer name or scale figure. The same never-invent rule applies to every number in the release.
Identify the benefit: what can they now do or get that they could not before?
Apply the formula: [Company] [verb] [specific thing], [immediate benefit]
Self-check: does the headline select the right audience? Does it promise a specific benefit? Is the news verb specific (not "announces exciting update")?
Write the lede. One paragraph, 40 words or fewer. Must answer: Who, What, When, Where, Why.
Apply the lede test: someone reading only this paragraph should understand the full story.
Write the release in Inverted Pyramid structure:
FOR IMMEDIATE RELEASE
<Headline: Ogilvy formula applied. 60-80 chars, sentence case, news-led, benefit-stated>
<Subheadline: 100-130 chars, adds the "why this matters">
<DATELINE CITY, DD-MM-YYYY> -- <Lede: 30-40 words. Who, what, when, where, why. Full story in one paragraph.>
<Paragraph 2: 50-80 words. The most important supporting context. Why now? What problem does this solve? Include one supporting stat if available.>
<Quote 1: from company executive. Full attribution: "Quote," said <Name>, <Title> at <Company>. "Continued quote." 40-60 words total.>
<Paragraph 4: 50-80 words. Specifics. Product details, deal terms, timeline. Likely paragraph to be cut by editors - make it skippable without breaking the story.>
<Quote 2: from external party. Same attribution format. 30-50 words.>
<Paragraph 6: 30-50 words. What's next. Availability, rollout plan, how to learn more.>
###
About <Company>
<Boilerplate from knowledge/company.md, 50-80 words. Name, what they do, founded, HQ, notable customers or scale, website.>
Press contact:
<Name>
<Title>
<Email>
<Phone if provided>
Style rules:
AP style: spell out numbers under 10, use figures for 10+
Dates: spell out month in the body, e.g. "April 25, 2026" (AP requires this; use DD-MM-YYYY for filename and frontmatter only)
Titles capitalized only before names ("Chief Executive Officer Jane Doe" but "Jane Doe, chief executive officer")
No exclamation points
No marketing language in the body ("revolutionary", "industry-leading", "best-in-class")
Past tense for the news ("announced today")
Active voice
Self-check. Every item is checkable against the draft itself. Where an item names a number,
count it rather than asserting it.
Headline: name the audience it selects and the benefit it promises, in the working notes. If either cannot be named from the headline alone, rewrite it
Headline verb is one of the specific news verbs, and the headline is 60 to 80 characters. Count them
Lede: count the words. 40 or fewer, and each of the five Ws is present. Mark which clause carries each W
Lede test run: read paragraph 1 alone and write the one-sentence story it gives. If it is missing a W, the lede fails
Cut-from-the-bottom test run: delete the last 2 paragraphs and confirm no fact the story needs disappeared
Exactly 2 or more quotes, each with a full name, a title and an organisation. Every quote is either supplied by the user verbatim or is a [QUOTE NEEDED FROM ...] placeholder. Count the placeholders and state the count to the user
Every figure in the draft traces to a user-supplied fact or knowledge/company.md. List the figures and their sources in the working notes
Boilerplate present, last, and taken from knowledge/company.md unedited
Press contact block has a name and an email
Search the body for "we", "our" and "us" outside quotation marks. Zero hits
Total length 400 to 600 words. Count them
Search the body for the banned marketing words: revolutionary, industry-leading, best-in-class, game-changing, seamless, robust, cutting-edge. Zero hits outside quotes
Save to output/press-release/<DD-MM-YYYY>-<slug>.md with frontmatter:
Email pitch to journalists (3 sentences + the release attached)
LinkedIn announcement post
Internal Slack message
Customer email if relevant
Rules
Never invent quotes. If the user does not have a quote yet, leave a placeholder: [QUOTE NEEDED FROM <Name>, <Title>] and tell the user.
Never embargo without confirming the embargo time and timezone explicitly.
For funding announcements, confirm the round size, lead investor, and use of funds with the user before drafting. These are factual claims that cannot be wrong.
For executive hires, confirm the start date, prior role, and reporting line.
The lede is not the headline rewritten. It must add the 5 Ws that the headline omits.
If the most important information is not in the first paragraph, the structure is wrong - fix it before saving.
Never invent a number. Round sizes, valuations, customer counts, ARR, headcount, uptime, percentage improvements, founding year, HQ city. Every one is a factual claim in a public document that a journalist may verify and a regulator may read. Unsupplied is [NEEDS INPUT: <the exact fact>], never an estimate.
Never invent a name, a title, an investor, or a partner organisation, and never adjust a supplied title to sound better. Titles in a release are checked.
Never soften a placeholder to make the draft read smoothly. A draft that reads finished but contains an invented quote is the worst artifact this skill can produce, because it is the one most likely to be published as-is.
Do not write a customer name into the release without confirming the customer has approved being named.
Files this skill reads and writes
This skill writes to output/press-release/ only. It has no shared-knowledge write path and no
ownership collision with any sibling skill, which is deliberate: a release is a dated artifact, not
canon.
File
Access
Owner
knowledge/company.md
Read only, and boilerplate is copied unedited
/brand-context
knowledge/brand/voice.md
Read only
/brand-context
knowledge/markets/positioning.md
Read only
/positioning-doc
output/press-release/<DD-MM-YYYY>-<slug>.md
Write
This skill
If the boilerplate in knowledge/company.md is wrong or stale, say so and route the user to
/brand-context. Do not correct it from here, and do not write a better version into the release
while leaving the knowledge file untouched, because the next release would then disagree with this
one.
What this skill cannot know
These are the limitations that bite in practice. Where one applies to the artifact, write it into the document as an open question rather than leaving the reader to assume it was verified.
Whether the news is legally clear to announce. Funding rounds, acquisitions, customer names and executive departures usually need counsel, investor or customer sign-off. This skill has no visibility into what has been cleared.
Whether a journalist will care. Newsworthiness depends on the beat, the week, and what else is announcing that day. The structure here maximises the chance a release survives a scan, and it cannot manufacture a hook that is not in the facts.
Whether the supplied figures are accurate or current. The skill can refuse to invent a number and can demand a source. It cannot audit one.
Embargo mechanics. Whether an outlet honours an embargo, and what was promised to whom, lives in the relationship, not in the document. Confirm the time and timezone with the user explicitly, and never assume one.
Related skills
/pr-pitch-writer for the email that puts this release in front of a journalist, and it is what actually gets it read
/case-study-writer for the customer story a launch release should point to, when the proof is a customer outcome rather than a figure
/brand-context for creating or fixing the knowledge/company.md boilerplate this skill copies unedited
/positioning-doc for when the release keeps describing the product differently from the positioning file
/linkedin-post for the founder or executive announcement post that runs alongside the release
/social-calendar for scheduling the announcement day across channels once the embargo time is fixed
/thought-leadership-writer for when the check above found an internal milestone rather than news, and the story is better told as a point of view
1---2name: press-release-writer3description: Write press releases for product launches, funding announcements, partnerships, executive hires, and milestones using the Inverted Pyramid (AP journalism) and Ogilvy on Headlines (David Ogilvy, Ogilvy on Advertising). The lede answers Who/What/When/Where/Why in 40 words or fewer. The headline selects the right audience and promises a specific benefit. Use when the user asks for a press release, media release, news announcement, PR for X, launch announcement, funding announcement, or "write a press release". Reads brand voice and positioning from knowledge/. For pitching it to a journalist, see pr-pitch-writer. For the customer story behind it, see case-study-writer.4---56# press-release-writer78Writes press releases in AP style using the Inverted Pyramid structure and Ogilvy's headline principles. Optimized for journalists who scan, not read. The most important information is always first. The headline selects the right audience and promises a concrete benefit - not a label.910## Framework: Inverted Pyramid + Ogilvy on Headlines1112### Inverted Pyramid (AP journalism)1314Put the most important information first, then supporting details, then background. The structure15exists because of how newsrooms work: journalists scan, and editors cut from the bottom to fit16space. If the news is in paragraph 4, it does not survive the cut.1718| Level | Paragraphs | Contains | Word budget | Survives an editor's cut? |19|---|---|---|---|---|20| **Lede** | 1 | Who, what, when, where, why - the whole story | 40 or fewer | Never cut |21| **Supporting detail** | 2 to 3 | Why now, the problem solved, first quote | 50 to 80 each | Usually kept |22| **Background** | 4 to 6 | Specifics, deal terms, second quote, what is next | 30 to 80 each | Cut when space is tight |23| **Boilerplate** | last | About the company | 50 to 80 | Cut first, every time |2425Two tests, both run on the finished draft:26271. **Lede test**: can someone read only the first paragraph and understand the full story? If not, rewrite the lede rather than adding to paragraph 2.282. **Cut-from-the-bottom test**: delete the last 2 paragraphs. Is the story still complete and accurate? It must be. If deleting them removes a fact the story needs, that fact is in the wrong place.2930### Ogilvy on Headlines (*Ogilvy on Advertising*, David Ogilvy, 1983)3132"On average, five times as many people read the headline as read the body copy." Ogilvy's point is33that the headline is not a title, it is the ad. In a press release the headline is what decides34whether a journalist opens the email at all.3536| Ogilvy rule | Applied to a press release | Fails when |37|---|---|---|38| The headline selects the audience | The reader knows in one line whether this is their beat | It names the company and nothing else |39| The headline promises a benefit or creates curiosity | It states what someone can now do | It labels the topic: "Company Announces Product Update" |40| Never a blind headline | No wordplay the reader must decode | A pun carries the news |41| Specifics beat generalities | The round size, the number, the named thing | "Significant funding", "major partnership" |4243Ogilvy's best-performing headline formulas, in the order worth trying for a release:44451. **News**: announces something genuinely new, using a specific verb: Introduces, Launches, Names, Raises, Acquires462. **How-to**: "How [company] [does X] for [audience]" - strongest for product launches with a clear job473. **Command**: "Reduce [pain] by [specific amount]" - only with a number the user has supplied484. **Question**: a question the target audience asks themselves - weakest here, because news beats curiosity for a journalist on deadline4950Press release headline formula (AP plus Ogilvy combined):51`[Company] [verb: announces/launches/names/raises] [specific thing], [immediate benefit or impact]`5253Example: "Threadline Raises $32M Series B to Help PLG Teams Ship Onboarding Without Engineering"54- Audience selected: PLG teams55- Benefit stated: ship onboarding without engineering56- News verb used: Raises57- Specific: $32M, Series B5859The example above is a fictional company used to show the shape of the formula. Never carry any60figure from it into a real release.6162## Before you draft: is there enough to announce?6364A press release with a thin news hook does not fail quietly, it burns a journalist relationship.6566| Signal | Threshold | If below |67|---|---|---|68| Attributed quotes supplied by the user | 2, one internal and one external | Draft with `[QUOTE NEEDED FROM <Name>, <Title>]` in place and tell the user the release cannot go out until both are real |69| Hard facts: figures, dates, names, titles | All confirmed by the user | Stop on the unconfirmed one. Ask. Never draft a round size, a customer count, a founding year, or an HQ city |70| Boilerplate in `knowledge/company.md` | Present | Ask the user for it. Do not assemble one from the positioning doc, because boilerplate is a legal and factual statement, not marketing copy |71| Something a reader can do or get that they could not before | 1 required | Say plainly that this is an internal milestone, not news, and offer a LinkedIn post or a customer email instead. That is a better outcome than a release nobody covers |7273Warning signs, in priority order:74751. The headline needs the subheadline to make sense. The headline is doing labelling, not news.762. Every number in the draft came from the skill rather than the user. Stop and get them confirmed, one by one.773. The lede is the headline rewritten. It must add the five Ws the headline omits.784. The most interesting sentence is in paragraph 5. The pyramid is upside down, so restructure before polishing.7980## When to use8182- "Write a press release for our Series B"83- "Draft a media release announcing the partnership with X"84- "Write the launch announcement for <product>"85- "We need a press release for the new CMO hire"8687## Release types this skill handles8889- Product launch90- Funding round91- Partnership / integration92- Executive hire or appointment93- Customer milestone (Xth customer, $Y ARR, etc.)94- Acquisition (buyer side or sell side)95- Award or certification9697## Inputs needed (ask if missing)9899- **Type** of release (from list above)100- **Headline news** (the one sentence)101- **Date and dateline city**102- **Key facts**: numbers, names, titles, dates103- **Quote 1** (executive at company): name, title, full quote104- **Quote 2** (external: investor, partner, customer, board): name, title, organization, full quote105- **Boilerplate**: pull from `knowledge/company.md`. If missing, **ask the user** - never draft a founding year, HQ city, customer name or scale figure. The same never-invent rule applies to every number in the release.106- **Press contact**: name, email107108If quotes are missing, ask. Never invent.109110## Process1111121. **Load context.** Read `knowledge/company.md`, `knowledge/brand/voice.md`, `knowledge/markets/positioning.md`.1131142. **Write the headline first using Ogilvy's formula.**115 - Identify the audience: who is this news for?116 - Identify the benefit: what can they now do or get that they could not before?117 - Apply the formula: `[Company] [verb] [specific thing], [immediate benefit]`118 - Self-check: does the headline select the right audience? Does it promise a specific benefit? Is the news verb specific (not "announces exciting update")?1191203. **Write the lede.** One paragraph, 40 words or fewer. Must answer: Who, What, When, Where, Why.121 Apply the lede test: someone reading only this paragraph should understand the full story.1221234. **Write the release in Inverted Pyramid structure**:124125 ```126 FOR IMMEDIATE RELEASE127128 <Headline: Ogilvy formula applied. 60-80 chars, sentence case, news-led, benefit-stated>129 <Subheadline: 100-130 chars, adds the "why this matters">130131 <DATELINE CITY, DD-MM-YYYY> -- <Lede: 30-40 words. Who, what, when, where, why. Full story in one paragraph.>132133 <Paragraph 2: 50-80 words. The most important supporting context. Why now? What problem does this solve? Include one supporting stat if available.>134135 <Quote 1: from company executive. Full attribution: "Quote," said <Name>, <Title> at <Company>. "Continued quote." 40-60 words total.>136137 <Paragraph 4: 50-80 words. Specifics. Product details, deal terms, timeline. Likely paragraph to be cut by editors - make it skippable without breaking the story.>138139 <Quote 2: from external party. Same attribution format. 30-50 words.>140141 <Paragraph 6: 30-50 words. What's next. Availability, rollout plan, how to learn more.>142143 ###144145 About <Company>146 <Boilerplate from knowledge/company.md, 50-80 words. Name, what they do, founded, HQ, notable customers or scale, website.>147148 Press contact:149 <Name>150 <Title>151 <Email>152 <Phone if provided>153 ```1541555. **Style rules**:156 - AP style: spell out numbers under 10, use figures for 10+157 - Dates: spell out month in the body, e.g. "April 25, 2026" (AP requires this; use DD-MM-YYYY for filename and frontmatter only)158 - Titles capitalized only before names ("Chief Executive Officer Jane Doe" but "Jane Doe, chief executive officer")159 - No exclamation points160 - No marketing language in the body ("revolutionary", "industry-leading", "best-in-class")161 - Past tense for the news ("announced today")162 - Active voice1631646. **Self-check.** Every item is checkable against the draft itself. Where an item names a number,165 count it rather than asserting it.166167 - [ ] Headline: name the audience it selects and the benefit it promises, in the working notes. If either cannot be named from the headline alone, rewrite it168 - [ ] Headline verb is one of the specific news verbs, and the headline is 60 to 80 characters. Count them169 - [ ] Lede: count the words. 40 or fewer, and each of the five Ws is present. Mark which clause carries each W170 - [ ] Lede test run: read paragraph 1 alone and write the one-sentence story it gives. If it is missing a W, the lede fails171 - [ ] Cut-from-the-bottom test run: delete the last 2 paragraphs and confirm no fact the story needs disappeared172 - [ ] Exactly 2 or more quotes, each with a full name, a title and an organisation. Every quote is either supplied by the user verbatim or is a `[QUOTE NEEDED FROM ...]` placeholder. Count the placeholders and state the count to the user173 - [ ] Every figure in the draft traces to a user-supplied fact or `knowledge/company.md`. List the figures and their sources in the working notes174 - [ ] Boilerplate present, last, and taken from `knowledge/company.md` unedited175 - [ ] Press contact block has a name and an email176 - [ ] Search the body for "we", "our" and "us" outside quotation marks. Zero hits177 - [ ] Total length 400 to 600 words. Count them178 - [ ] Search the body for the banned marketing words: revolutionary, industry-leading, best-in-class, game-changing, seamless, robust, cutting-edge. Zero hits outside quotes1791807. **Save** to `output/press-release/<DD-MM-YYYY>-<slug>.md` with frontmatter:181 ```yaml182 ---183 format: press-release184 type: <launch|funding|partnership|hire|milestone|acquisition|award>185 headline: <full headline>186 embargo: <none|until DD-MM-YYYY HH:MM TZ>187 created: DD-MM-YYYY188 ---189 ```1901918. **Offer companion assets**:192 - Email pitch to journalists (3 sentences + the release attached)193 - LinkedIn announcement post194 - Internal Slack message195 - Customer email if relevant196197## Rules198199- Never invent quotes. If the user does not have a quote yet, leave a placeholder: `[QUOTE NEEDED FROM <Name>, <Title>]` and tell the user.200- Never embargo without confirming the embargo time and timezone explicitly.201- For funding announcements, confirm the round size, lead investor, and use of funds with the user before drafting. These are factual claims that cannot be wrong.202- For executive hires, confirm the start date, prior role, and reporting line.203- The lede is not the headline rewritten. It must add the 5 Ws that the headline omits.204- If the most important information is not in the first paragraph, the structure is wrong - fix it before saving.205- **Never invent a number.** Round sizes, valuations, customer counts, ARR, headcount, uptime, percentage improvements, founding year, HQ city. Every one is a factual claim in a public document that a journalist may verify and a regulator may read. Unsupplied is `[NEEDS INPUT: <the exact fact>]`, never an estimate.206- Never invent a name, a title, an investor, or a partner organisation, and never adjust a supplied title to sound better. Titles in a release are checked.207- Never soften a placeholder to make the draft read smoothly. A draft that reads finished but contains an invented quote is the worst artifact this skill can produce, because it is the one most likely to be published as-is.208- Do not write a customer name into the release without confirming the customer has approved being named.209210## Files this skill reads and writes211212This skill writes to `output/press-release/` only. It has no shared-knowledge write path and no213ownership collision with any sibling skill, which is deliberate: a release is a dated artifact, not214canon.215216| File | Access | Owner |217|---|---|---|218| `knowledge/company.md` | Read only, and boilerplate is copied unedited | `/brand-context` |219| `knowledge/brand/voice.md` | Read only | `/brand-context` |220| `knowledge/markets/positioning.md` | Read only | `/positioning-doc` |221| `output/press-release/<DD-MM-YYYY>-<slug>.md` | Write | This skill |222223If the boilerplate in `knowledge/company.md` is wrong or stale, say so and route the user to224`/brand-context`. Do not correct it from here, and do not write a better version into the release225while leaving the knowledge file untouched, because the next release would then disagree with this226one.227228## What this skill cannot know229230These are the limitations that bite in practice. Where one applies to the artifact, write it into the document as an open question rather than leaving the reader to assume it was verified.2312321. **Whether the news is legally clear to announce.** Funding rounds, acquisitions, customer names and executive departures usually need counsel, investor or customer sign-off. This skill has no visibility into what has been cleared.2332. **Whether a journalist will care.** Newsworthiness depends on the beat, the week, and what else is announcing that day. The structure here maximises the chance a release survives a scan, and it cannot manufacture a hook that is not in the facts.2343. **Whether the supplied figures are accurate or current.** The skill can refuse to invent a number and can demand a source. It cannot audit one.2354. **Embargo mechanics.** Whether an outlet honours an embargo, and what was promised to whom, lives in the relationship, not in the document. Confirm the time and timezone with the user explicitly, and never assume one.236237## Related skills238239- `/pr-pitch-writer` for the email that puts this release in front of a journalist, and it is what actually gets it read240- `/case-study-writer` for the customer story a launch release should point to, when the proof is a customer outcome rather than a figure241- `/brand-context` for creating or fixing the `knowledge/company.md` boilerplate this skill copies unedited242- `/positioning-doc` for when the release keeps describing the product differently from the positioning file243- `/linkedin-post` for the founder or executive announcement post that runs alongside the release244- `/social-calendar` for scheduling the announcement day across channels once the embargo time is fixed245- `/thought-leadership-writer` for when the check above found an internal milestone rather than news, and the story is better told as a point of view
Run npx skillmds@latest add qa-aman/press-release-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Write press releases for product launches, funding announcements, partnerships, executive hires, and milestones using the Inverted Pyramid (AP journalism) and Ogilvy on Headlines (David Ogilvy, Ogilvy on Advertising). The lede answers Who/What/When/Where/Why in 40 words or fewer. The headline selects the right audience and promises a specific benefit. Use when the user asks for a press release, media release, news announcement, PR for X, launch announcement, funding announcement, or "write a press release". Reads brand voice and positioning from knowledge/. For pitching it to a journalist, see pr-pitch-writer. For the customer story behind it, see case-study-writer. It is listed under Marketing & Growth on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
qa-aman (@qa-aman) published this skill. Their other Agent Skills are listed on their SkillMD profile.
qa-aman