skills/channels/partnerships/public-relations/SKILL.md
When the user wants to plan PR, write a press release, or manage media relations. Also use when the user mentions "public relations," "PR," "press release," "media relations," "news release," "journalist," "media coverage," "product announcement," or "earned media." For on-site "As Seen In" or logos page, use press-coverage-page-generator.
npx skillsauth add kostja94/marketing-skills public-relationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guides PR and press release strategy. Journalists use ~3% of releases they receive; proper structure is critical. Use this skill when writing press releases, planning product announcements, or building media relations.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 2 (Positioning), 3 (Value Proposition), 8 (Brand & Voice).
Identify:
| Section | Guideline | |---------|-----------| | Header | Logo; contact (name, title, email, phone); "FOR IMMEDIATE RELEASE" or embargo | | Headline | Under 100 chars; strong action verbs; "Why should I care?" | | Subheadline | Optional; additional context | | Dateline | City, state, date | | Lead | 50–75 words; all 5 W's (Who, What, When, Where, Why) | | Body | 1–2 paragraphs; inverted pyramid; most newsworthy first | | Quote | Executive/stakeholder; perspective, not fact repetition | | Boilerplate | 2–3 sentence company description | | Media contact | Name, email, phone |
Journalist should understand the full story from the lead alone. Specific details, not vague language ("important update" → what changed and impact).
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.