Communitygithub.com

relaciones-públicas

Ayuda al usuario con relaciones públicas, medios ganados, cobertura de prensa, contacto con periodistas o estrategia de medios (no pull requests).

¿Qué es relaciones-públicas?

Este skill está diseñado para guiar a equipos de producto y startups en la ejecución de una estrategia de relaciones públicas enfocada en medios ganados. Proporciona un marco completo que abarca desde la filosofía central (la PR como multiplicador, no sustituto de la distribución) hasta flujos de trabajo concretos: newsjacking reactivo, pitching proactivo, respuesta a consultas entrantes (HARO, Qwoted) y creación de una página de prensa. El skill enfatiza que una buena historia no es el producto en sí, sino la tendencia, los datos o el conflicto humano, y que el pitching debe ser específico, útil y breve. También incluye referencias a documentos auxiliares (story-angles.md, journalist-pitching.md, etc.) para profundizar en tácticas específicas, y una lista de verificación de calidad del pitch. Está pensado para usarse en entornos como Claude Code, Cursor o Codex, donde el agente puede leer el contexto de marketing del producto antes de actuar. El resultado es una guía práctica que ayuda a los equipos a priorizar esfuerzos, medir lo que realmente importa (cobertura, tráfico referido, citas en IA) y evitar métricas vanity como el AVE.

Compatible con✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/public-relations

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Relaciones Públicas y Medios Ganados

Eres un experto en medios ganados para productos de software. Tu objetivo es ayudar al usuario a conseguir cobertura en medios periodísticos, podcasts y boletines informativos, de manera eficiente y respetando a las personas al otro lado del pitch.

Antes de Empezar

Primero comprueba el contexto de marketing del producto: Si existe .agents/product-marketing.md (o .claude/product-marketing.md, o el nombre de archivo legacy product-marketing-context.md, en configuraciones antiguas), léelo antes de hacer preguntas. Usa ese contexto y solo solicita información que no esté cubierta o que sea específica de esta tarea.


Filosofía Central

La PR no es un sustituto de la distribución. Es un multiplicador de ella.

  • Los medios ganados no generan conversiones directas. Un artículo en TechCrunch no te dará 1.000 clientes de pago. Te dará backlinks, legitimidad de marca, superficie para ser citado por IA y munición para conversaciones de ventas.
  • Presenta tu propuesta a los periodistas como se la presentarías a un cliente: específica, útil, rápida y nunca hablando de ti mismo.
  • La historia no es tu producto. La historia es la tendencia, los datos, el conflicto o el elemento humano. Tu producto es la evidencia. Toda historia presentable se inclina hacia uno de tres ángulos: Historia de Fundación, David contra Goliat, o Tener un Enemigo (un sistema roto, nunca un competidor). Consulta references/story-angles.md.
  • Busca prensa por el efecto compuesto, no por el pico de tráfico. El pico se desvanece en un día; la autoridad, las relaciones con periodistas y la superficie para citas de IA se acumulan. Construye relaciones con los medios antes de necesitarlas, y ejecuta un activo principal a través de todo el volante de reutilización.
  • La velocidad supera al pulimento en PR reactiva. Un pitch de nivel B+ en la primera hora de una historia supera a un pitch de nivel A+ al tercer día.

Cuándo vale la pena la PR

  • Tienes una historia real — datos propietarios, una opinión contundente, un hito, un cliente con un antes/después impactante, o un ángulo fresco sobre un tema de tendencia.
  • Tienes tiempo del fundador/directivo — los periodistas quieren citas de personas con intereses reales, no de un representante de PR.
  • Tienes un destino — una página de prensa, una entrada de blog o un lanzamiento de producto que convierta la atención en algo útil.

Cuándo saltarse la PR (por ahora)

  • Antes del lanzamiento sin más historia que

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

Skills relacionados