press-release-writer

作者: samber

为任何场合、媒体类型和国家撰写专业新闻稿。当用户想要撰写、起草或改进新闻稿、公报、媒体公告、新闻发布或公关声明时使用——包括产品发布、融资轮次、合作伙伴关系、危机沟通、财报、高管任命、活动、并购、开源里程碑和媒体咨询。涵盖所有发布类型、媒体目标(印刷、数字/通讯社、广播、社交/SMPR、行业媒体)以及……

npx skills add https://github.com/samber/cc-skills --skill press-release-writer

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 for the template matching the release type
  • If targeting a specific region: Regional conventions for style guide, dateline, regulations, optimal send times, and cultural expectations
  • If adapting for a specific media format: Media formats for format-specific adaptations
  • If preparing a journalist email pitch: Journalist email pitch for subject lines, hook types, email structure, and follow-up cadence
  • For writing style guidance: Writing principles for detailed rules on tone, language, and quotes
  • For delivery format options: Output options 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 6b: Humanize

Invoke a humanizer skill (e.g. "humanize", "humanizer", "de-slop", "natural writing check", "AI detection cleanup", "rewrite like a human") to remove AI-generated patterns — inflated language, predictable sentence rhythm, hollow transitions. Journalists spot AI copy immediately and discard it.

Preserve the headline and lead. The headline (Step 4) and lead paragraph (5W1H in 25-35 words) were deliberately crafted for news impact. Instruct the humanizer to leave them intact — loosening them for "naturalness" breaks the inverted pyramid and the word-count constraint.

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)
  • 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

来自 samber 的更多技能

golang-code-style
samber
Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).
developmentcode-review
golang-testing
samber
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see...
developmenttestingcode-review
golang-design-patterns
samber
惯用的Go设计模式——函数选项、构造函数、错误流与级联、资源管理与生命周期、优雅关闭、弹性、架构、依赖注入、数据处理、流式处理等。适用于在架构模式间明确选择、实现函数选项、设计构造函数API、设置优雅关闭、应用弹性模式,或询问哪种惯用Go模式适合特定问题时。
developmentdesigncode-review
golang-error-handling
samber
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops`...
developmentcode-review
golang-performance
samber
Golang性能优化模式与方法论——若存在X瓶颈,则应用Y方案。涵盖分配减少、CPU效率、内存布局、GC调优、池化、缓存及热路径优化。适用于性能分析或基准测试已识别瓶颈时,需采用正确优化模式进行修复。亦适用于执行性能代码审查时,提出改进建议或可帮助快速识别性能增益的基准测试。不适用于测量方法论(→...
developmentcode-review
golang-security
samber
Golang的安全最佳实践与漏洞防护,涵盖注入(SQL、命令、XSS)、密码学、文件系统安全、网络安全、Cookie、密钥管理、内存安全及日志记录。适用于编写、审查或审计Go代码的安全性,或处理涉及加密、I/O、密钥管理、用户输入处理或身份验证的高风险代码。包含安全工具的配置。
securitycode-reviewdevelopment
golang-database
samber
Go数据库访问全面指南——参数化查询、结构体扫描、可空列、事务、隔离级别、SELECT FOR UPDATE、连接池、批处理、上下文传播及迁移工具。适用于编写、审查或调试与PostgreSQL、MariaDB、MySQL或SQLite交互的Golang代码;数据库测试;或关于database/sql、sqlx或pgx的问题。不生成数据库模式或迁移SQL。
developmentdatabase
golang-lint
samber
Golang项目的lint最佳实践与golangci-lint配置——运行linter、配置.golangci.yml、使用nolint指令抑制警告、解读lint输出以及选择linter。适用于配置golangci-lint、询问lint警告或nolint抑制、设置代码质量工具或选择linter时使用。当用户提及golangci-lint、go vet、staticcheck或revive时也可使用。
developmentcode-reviewtesting