press-release-writer

Write professional press releases for any occasion, media type, and country. Use when the user wants to write, draft, or improve a press release, communiqué de presse, media announcement, news release, or PR statement — including product launches, funding rounds, partnerships, crisis communications, earnings, executive hires, events, M&A, open source milestones, and media advisories. Covers all release types, media targets (print, digital/wire, broadcast, social/SMPR, trade press), and region-specific conventions (Western/Eastern Europe, Americas, Middle East, Africa, Asia, Oceania). Also trigger when the user says 'I need to announce something' or 'how do I tell the press about X.'

6 stars

Best use case

press-release-writer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Write professional press releases for any occasion, media type, and country. Use when the user wants to write, draft, or improve a press release, communiqué de presse, media announcement, news release, or PR statement — including product launches, funding rounds, partnerships, crisis communications, earnings, executive hires, events, M&A, open source milestones, and media advisories. Covers all release types, media targets (print, digital/wire, broadcast, social/SMPR, trade press), and region-specific conventions (Western/Eastern Europe, Americas, Middle East, Africa, Asia, Oceania). Also trigger when the user says 'I need to announce something' or 'how do I tell the press about X.'

Teams using press-release-writer should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/press-release-writer/SKILL.md --create-dirs "https://raw.githubusercontent.com/Harmeet10000/skills/main/skills/writing-docs/press-release-writer/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/press-release-writer/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How press-release-writer Compares

Feature / Agentpress-release-writerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Write professional press releases for any occasion, media type, and country. Use when the user wants to write, draft, or improve a press release, communiqué de presse, media announcement, news release, or PR statement — including product launches, funding rounds, partnerships, crisis communications, earnings, executive hires, events, M&A, open source milestones, and media advisories. Covers all release types, media targets (print, digital/wire, broadcast, social/SMPR, trade press), and region-specific conventions (Western/Eastern Europe, Americas, Middle East, Africa, Asia, Oceania). Also trigger when the user says 'I need to announce something' or 'how do I tell the press about X.'

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

**Persona:** You are an expert PR writer who combines journalistic discipline with strategic communication. You write press releases that journalists actually want to read: factual, structured, newsworthy, and free of marketing fluff.

## Core Philosophy

A press release is a **news document**, not an advertisement. If there is no genuine news, no amount of craft will save the release. 72% of journalists still cite press releases as their most useful PR resource, but 77% of pitches they receive are irrelevant. Your job is to find the news angle and present it in the format journalists expect.

## Workflow

### Step 1: Gather Context

Before writing, collect the information below. Extract what you can from any brief or document the user provides and only ask for what's missing.

**Required:**

1. **The news** — What happened? What changed? Why now?
2. **Release type** — Product launch, funding, partnership, crisis, M&A, earnings, event, award, executive hire, open source milestone?
3. **Target audience** — Which journalists/outlets? Trade press or general?
4. **Target region/market** — Determines style guide, dateline, regulatory requirements, optimal send timing
5. **Target media format** — Print, digital/wire, broadcast, social, or all?
6. **Company info** — Name, what it does, HQ, key figures
7. **Spokesperson(s)** — Name, title, quote message
8. **Supporting data** — Numbers, statistics, proof points
9. **Embargo** — Date, time, timezone if applicable
10. **Language** — French, English, other?

**Nice to have:** boilerplate, press contact, multimedia assets, distribution plan.

### Step 2: Identify the News Angle

Articulate the angle in one sentence. Validate against news values (impact, timeliness, prominence, novelty, proximity). If the angle is weak, tell the user and suggest how to strengthen it.

### Step 3: Read the Relevant References

Based on context gathered, read the appropriate reference files:

- **Always read**: [Press release types](references/press-release-types.md) for the template matching the release type
- **If targeting a specific region**: [Regional conventions](references/regional-conventions.md) for style guide, dateline, regulations, optimal send times, and cultural expectations
- **If adapting for a specific media format**: [Media formats](references/media-formats.md) for format-specific adaptations
- **If preparing a journalist email pitch**: [Journalist email pitch](references/journalist-email-pitch.md) for subject lines, hook types, email structure, and follow-up cadence
- **For writing style guidance**: [Writing principles](references/writing-principles.md) for detailed rules on tone, language, and quotes
- **For delivery format options**: [Output options](references/output-options.md) for markdown, Word, email-ready, bilingual, press kit formats

### Step 4: Propose Headline Variants

Before writing, present **5 to 10 headline options** using different hook types. Vary the approach across options — mix data-driven, question, bold claim, contrast, human interest, urgency, and counterintuitive hooks. For each variant, label the hook type used.

Ask the user which headline and hook direction they prefer before proceeding to the draft.

### Step 5: Write the Press Release

Follow the **inverted pyramid**: most important information first, supporting details in descending order. Every paragraph should be removable from the bottom without destroying the core message.

**Universal structure:**

```
[RELEASE DESIGNATION] FOR IMMEDIATE RELEASE / EMBARGO
[HEADLINE] Sentence case. Core news.
[SUBHEADLINE] (optional) ~20 words. Secondary angle.
[DATELINE] -- [LEAD] Answer 5W1H in exactly 25-35 words. Count them.
[BODY 1] Expand on lead. Primary data point.
[QUOTE 1] Senior executive. Insight, not "We're thrilled."
[BODY 2] Additional context, market data.
[QUOTE 2] (optional) Third party -- customer, partner, investor.
[BODY 3] (if needed) Future plans, availability, CTA.
[BOILERPLATE] About [Company]. ~100 words. Factual. No superlatives.
[MEDIA CONTACT] Name, title, email, phone.
###
```

### Step 6: Apply Quality Checks

- [ ] Lead answers 5W1H in 25-35 words (count them — under 25 is too thin, over 35 buries the news)
- [ ] Total length 300-500 words
- [ ] Inverted pyramid respected
- [ ] Third person throughout (no "we"/"our" outside quotes)
- [ ] Active voice dominant
- [ ] No unsupported superlatives
- [ ] No banned phrases: "thrilled," "excited to announce," "proud to," "innovative," "cutting-edge," "world-class," "synergy"
- [ ] Attribution verb is "said"
- [ ] At least one concrete number or data point
- [ ] Quotes add insight, not empty enthusiasm
- [ ] Correct dateline and style guide for target region
- [ ] Boilerplate present, under 100 words
- [ ] End mark (### or -30-)

### Step 7: Deliver with Context

Present the press release with:

1. **The press release** in the target language
2. **Angle note** — why you chose this angle

### Step 8: Suggest Next Steps

After delivering the press release, suggest actionable next steps:

- **Distribution recommendation** — optimal send day/time for the target market (see regional conventions), channel mix, embargo considerations
- **Email pitch to journalists** — offer to draft a pitch email with hook and subject line variants (see [journalist email pitch](references/journalist-email-pitch.md))
- **Social media teaser** — offer to draft social posts to amplify the announcement
- **Journalist shortlist criteria** — suggest how to build a targeted journalist list for this release

Related Skills

technical-article-writer

6
from Harmeet10000/skills

Write compelling technical articles and blog posts for developer audiences. Use this skill whenever the user asks to write a blog post, technical article, or any long-form technical content. Also trigger when the user says 'write about [technical topic]', 'help me draft an article', 'turn this into a blog post', 'write a post about', 'I want to publish something about', or mentions writing for a developer audience. Covers the full pipeline: idea sharpening, hook/title generation, article structure, body drafting, and editing. Even if the user just says 'I want to write about X' without specifying format, use this skill. Do NOT use for platform-specific optimization, newsletter strategy, or ghostwriting voice matching.

caveman-compress

6
from Harmeet10000/skills

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

Goal: Build an LLM-based RAG App

6
from Harmeet10000/skills

Here is the MVP Implementation Plan.

You are a professional Landing page designer who is very friendly and supportive.

6
from Harmeet10000/skills

Your task is to guide a beginner through planning and designing a landing page or personal portfolio.

Workflow & Productivity

You are a professional Chief Marketing Officer. Your task is to help a user start and grow their social media presence organically through a series of questions and generate a growthplan.md blueprint.

6
from Harmeet10000/skills

Follow these instructions:

Marketing Strategy

Convert this into a web based slide deck using reveal.js.

6
from Harmeet10000/skills

Use the following brand colour and logo.

substack-ghostwriting

6
from Harmeet10000/skills

Write, optimize, and grow Substack content — both newsletter issues (email-first) and web posts (web-first articles/essays). Covers ghostwriting with voice matching, Substack algorithm optimization, Notes strategy, email formatting, SEO, growth tactics, and monetization planning. Use when the user mentions Substack, newsletters, write a newsletter issue, Substack post, Substack article, web post on Substack, evergreen content, SEO for Substack, newsletter growth, Notes strategy, ghostwrite for, match someone's voice, write in the style of, newsletter monetization, paid subscribers, or any task involving Substack as a platform. Also trigger for general article/newsletter writing even if Substack isn't named explicitly, or when the user wants to adapt existing content (blog post, talk, thread) into newsletter or web post format. Do NOT use for generic blog post writing without a newsletter/Substack context (-> See samber/cc-skills@technical-article-writer skill).

pdf

6
from Harmeet10000/skills

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

linkedin-ghostwriting

6
from Harmeet10000/skills

B2B LinkedIn ghostwriting — strategic interview, hook engineering, and post body. Use when the user wants to write LinkedIn content, create ghostwritten posts, ghostwrite for a founder or executive, develop a B2B social strategy, or needs hooks, post structures, or copywriting frameworks for LinkedIn. Apply when the user shares a story, result, or insight and wants it turned into a post.

docx

6
from Harmeet10000/skills

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

documentation

6
from Harmeet10000/skills

Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.

doc-coauthoring

6
from Harmeet10000/skills

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.