press-release
The press-release skill generates journalist-ready press releases structured around the actual news angle rather than promotional messaging. Use it when drafting press releases, media announcements, news releases, or press statements. It requires the news itself, company name, announcement date, executive quote, relevance to readers, target media type, and contact details, then produces a formatted release with headline, dateline, body paragraphs, boilerplate, and media contact information.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/press-release && cp -r /tmp/press-release/plugins/pm-cross/skills/press-release ~/.claude/skills/press-releaseSKILL.md
# Press Release Skill Writes press releases that journalists actually read — structured around the news angle, not the desire to promote. ## Required Inputs - **The news** (what is actually happening — be specific) - **Company name** - **Date of announcement / embargo date** - **Key quote** (from which executive and approximately what they want to say) - **Why this matters** (to the reader, not the company) - **Target media** (trade / national / local / consumer / investor) - **Media contact details** ## Output Structure --- FOR IMMEDIATE RELEASE / EMBARGOED UNTIL: [Date and time] --- # [Headline — active verb, specific news, under 10 words] ## [Subheadline — the so-what in one sentence, adds context not repetition] **[City, Date]** — [Opening paragraph: Who, What, When, Where, Why in 2-3 sentences. A journalist should be able to run this paragraph alone. No background, no context, no company history.] [Second paragraph: the significance. Why does this matter? What does it mean for customers or the industry?] [Third paragraph: quote from executive. Human and specific. Not a restatement of the headline.] "[Quote text — specific, adds something the facts do not say]," said [Name], [Title] at [Company]. "[Second sentence extending the thought]." [Fourth paragraph: supporting detail — data, customer names with permission, additional context] [Fifth paragraph optional: what happens next, when it goes live, what people can do] --- ENDS --- **Notes to editors:** **About [Company]** [Boilerplate: 3-4 sentences. What the company does, when founded, where based, key facts. Factual not promotional.] **Media contact:** [Name] | [Title] | [Email] | [Phone] | [Hours/timezone] --- ## Headline Rules - Active voice: "Company launches X" not "X is launched by Company" - Specific: "raises 5M" not "secures significant investment" - Under 10 words - Never start with the company name — lead with the news ## Journalist Test Would a journalist care? Is the headline the full story? Is there a human angle? Is the quote something a human would say? Can the first paragraph stand alone? ## Quality Checks - [ ] Headline uses active voice and is under 10 words - [ ] First paragraph stands alone as the complete story - [ ] Quote adds something the facts don't say (not a restatement) - [ ] Boilerplate is factual, not promotional - [ ] Embargo date and media contact are included ## Anti-Patterns - [ ] Do not bury the news — the most important information must appear in the first paragraph (inverted pyramid) - [ ] Do not use promotional language or superlatives — press releases must read as news, not advertising copy - [ ] Do not omit the boilerplate — every press release needs the standard "About [Company]" paragraph at the end - [ ] Do not forget the embargo date and media contact — journalists need both to use the release - [ ] Do not write a headline longer than 12 words — it must be scannable and specific ## Example Trigger Phrases - "Write a press release announcing [news]" - "Draft a media statement about [event]" - "We are launching [product] — write the press release" - "Turn this announcement into a press release: [paste notes]"
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.