press-release-writer

por samber

Redacta comunicados de prensa profesionales para cualquier ocasión, tipo de medio y país. Úsalo cuando el usuario quiera escribir, redactar o mejorar un comunicado de prensa, communiqué de presse, anuncio para medios, noticia de prensa o declaración de relaciones públicas, incluidos lanzamientos de productos, rondas de financiación, asociaciones, comunicaciones de crisis, resultados financieros, contrataciones ejecutivas, eventos, fusiones y adquisiciones, hitos de código abierto y avisos para medios. Abarca todos los tipos de comunicados, objetivos mediáticos (impresos, digitales/cable, transmisión, redes sociales/SMPR, prensa especializada) y...

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

Más skills de 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
Patrones de diseño idiomáticos en Golang: opciones funcionales, constructores, flujo y cascada de errores, gestión y ciclo de vida de recursos, apagado elegante, resiliencia, arquitectura, inyección de dependencias, manejo de datos, streaming y más. Aplicar al elegir explícitamente entre patrones arquitectónicos, implementar opciones funcionales, diseñar APIs de constructores, configurar un apagado elegante, aplicar patrones de resiliencia o preguntar qué patrón idiomático de Go se ajusta a un problema específico.
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
Patrones y metodología de optimización de rendimiento en Golang: si hay un cuello de botella X, entonces aplica Y. Cubre reducción de asignaciones, eficiencia de CPU, diseño de memoria, ajuste de GC, pooling, caching y optimización de rutas críticas. Úsalo cuando el perfilado o los benchmarks hayan identificado un cuello de botella y necesites el patrón de optimización adecuado para solucionarlo. También úsalo al realizar una revisión de código de rendimiento para sugerir mejoras o benchmarks que ayuden a identificar ganancias rápidas de rendimiento. No es para metodología de medición (→...
developmentcode-review
golang-security
samber
Prácticas recomendadas de seguridad y prevención de vulnerabilidades para Golang. Abarca inyección (SQL, comandos, XSS), criptografía, seguridad del sistema de archivos, seguridad de red, cookies, gestión de secretos, seguridad de memoria y registro. Aplicar al escribir, revisar o auditar código Go por seguridad, o al trabajar en cualquier código riesgoso que involucre criptografía, E/S, gestión de secretos, manejo de entrada de usuario o autenticación. Incluye configuración de herramientas de seguridad.
securitycode-reviewdevelopment
golang-database
samber
Guía completa para el acceso a bases de datos en Go: consultas parametrizadas, escaneo de estructuras, columnas anulables, transacciones, niveles de aislamiento, SELECT FOR UPDATE, pool de conexiones, procesamiento por lotes, propagación de contexto y herramientas de migración. Úsela al escribir, revisar o depurar código Golang que interactúe con PostgreSQL, MariaDB, MySQL o SQLite; para pruebas de bases de datos; o para preguntas sobre database/sql, sqlx o pgx. NO genera esquemas de bases de datos ni SQL de migración.
developmentdatabase
golang-lint
samber
Mejores prácticas de linting y configuración de golangci-lint para proyectos Golang: ejecutar linters, configurar .golangci.yml, suprimir advertencias con directivas nolint, interpretar la salida de lint y seleccionar linters. Úselo al configurar golangci-lint, preguntar sobre advertencias de lint o supresiones nolint, configurar herramientas de calidad de código o elegir linters. También úselo cuando el usuario mencione golangci-lint, go vet, staticcheck o revive.
developmentcode-reviewtesting