Press releases and digital PR
Talk like ../../references/plain-language.md: plain words, and end each step with Done / Cost so far / Next, asking for one yes.
Read ../../references/outreach-playbook.md (§ Press releases, templates 1 and 9, hard rules) and ../../references/checklist-offpage.md §C1–C2. Paid data runs follow the protocol in ../../references/tools-and-apis.md.
Web connector mode
Keep the release and pitch drafts in chat (no seo-workspace/pr/). Paid journalist or news research: say it is a paid check billed to the user's own Apify account, wait for a clear yes, then quote_cost for the cap and call-actor on khadinakbar/* only. Give the amount only if the user asks. Any pitch email goes through outreach — call check_outreach_draft before asking for a send yes. Nothing is published or wired without the user's explicit approval of plan and price.
A. Press release
Write for readers and journalists. Never write a release only to plant claims for AI to repeat, and never use cheap wire networks for that: it is a gaming tactic that spam updates target.
- Angle check — real and verifiable: launch, feature, funding, partnership, expansion, hire, award actually won, original data study, customer result (with permission). No angle → say so and suggest creating one (a data study or a useful tool) instead of a fluff release.
- Write
seo-workspace/<domain>/pr/release-<slug>.md with: headline (entity + the real news, in plain words people would search), optional summary ≤45 words, dateline (City, Country — Date), lead answering who/what/when/where/why, 2–3 specific body paragraphs, a quote from a named person, consistent "About [Brand]" boilerplate (include the facts AI engines tend to get wrong: pricing model, locations, integrations), media contact. 250–1,200 words, ≤5 links (brand or naked URLs, no keyword anchors).
- Check against the typical wire limits in the playbook and list any violations.
- Distribution: the user publishes through their wire or PR partner. Any paid distribution needs their explicit approval of plan and price. Recommend pairing the release with an on-site page stating the same facts (releases decay within weeks; the page lasts).
- Track: when the user shares the live/report URLs, log them to
offpage-log.csv (type=press_release). After ~7 days, check pickup: khadinakbar/google-news-scraper for the brand (paid; ask first) and the brand prompts from ai-search-visibility (AI Overviews often repeat syndicated release facts within days). Report what changed.
B. Proactive digital PR (data-led)
- Pick a data angle tied to the business (survey, public-data analysis, pricing index, "cost by city/state", industry benchmark). Optional research inputs:
khadinakbar/reddit-posts-comments-scraper (what people ask), khadinakbar/google-trends-scraper (timing), khadinakbar/software-reviews-all-in-one-scraper / trustpilot-reviews-scraper (review-mining studies).
- Build the asset page on the site (methodology, charts, embed code, quotable stats).
- Journalist list:
khadinakbar/google-news-scraper for the topic over the last 60–90 days → bylines, outlets, article URLs. Contacts via the outreach skill (author pages, bulk-website-contact-extractor, email-address-validator).
- Pitch with template 1 (≤90 words, 2–3 stats matched to each journalist's angle). Follow-ups day 3–4 and +2–3 days. Drafting and sending go through
outreach (approval-gated).
C. Reactive PR (expert-request platforms)
Status of HARO (Help a Reporter Out), checked November 2026: it is running again. Cision closed it in December 2024 (it had been renamed Connectively), sold it to a new owner in April 2025, and that owner restarted the email digests (Cision's announcement: https://www.cision.com/about/press-releases/2025-press-releases/cision-announces-sale-of-help-a-reporter-out-haro-to-featuredcom-302427990/). It has closed and changed hands before, so confirm it is still running, and read its current rules, before relying on it. This is a status note, not a recommendation: Citebase does not recommend any platform. If the user already receives journalist query digests from an expert-request platform and they reach a connected inbox: triage today's queries against the client's real expertise, skip ones that conflict with their stance, and draft answers with template 9 that mirror the journalist's stated angle. Draft only — the user edits and sends; credibility must be human. Never fabricate credentials or personas.
Rules
- No fabricated events, awards, quotes or customers; no competitor attacks; no anchor-text stuffing.
- Nothing is published or sent without the user's explicit approval.
1---2name: press-release3description: Digital PR and press releases — find a genuine news angle, write a wire-ready press release, find journalists who recently covered the topic, pitch data stories, answer journalist queries from expert-request platforms the user already uses, and track coverage and AI pickup. Use for press release, PR, digital PR, newswire, journalist pitch, HARO-style requests, media coverage, brand mentions.4argument-hint: "<domain> [release|pitch|reactive] [news/angle]"5metadata:6 source: https://skillmd.com/skills/khadinakbarlabs/press-release7---89# Press releases and digital PR1011Talk like `../../references/plain-language.md`: plain words, and end each step with Done / Cost so far / Next, asking for one yes.1213Read `../../references/outreach-playbook.md` (§ Press releases, templates 1 and 9, hard rules) and `../../references/checklist-offpage.md` §C1–C2. Paid data runs follow the protocol in `../../references/tools-and-apis.md`.1415## Web connector mode16Keep the release and pitch drafts in chat (no `seo-workspace/pr/`). Paid journalist or news research: say it is a paid check billed to the user's own Apify account, wait for a clear yes, then `quote_cost` for the cap and `call-actor` on `khadinakbar/*` only. Give the amount only if the user asks. Any pitch email goes through `outreach` — call `check_outreach_draft` before asking for a send yes. Nothing is published or wired without the user's explicit approval of plan and price.1718## A. Press release19Write for readers and journalists. Never write a release only to plant claims for AI to repeat, and never use cheap wire networks for that: it is a gaming tactic that spam updates target.20211. **Angle check** — real and verifiable: launch, feature, funding, partnership, expansion, hire, award actually won, original data study, customer result (with permission). No angle → say so and suggest creating one (a data study or a useful tool) instead of a fluff release.222. **Write** `seo-workspace/<domain>/pr/release-<slug>.md` with: headline (entity + the real news, in plain words people would search), optional summary ≤45 words, dateline (City, Country — Date), lead answering who/what/when/where/why, 2–3 specific body paragraphs, a quote from a named person, consistent "About [Brand]" boilerplate (include the facts AI engines tend to get wrong: pricing model, locations, integrations), media contact. 250–1,200 words, ≤5 links (brand or naked URLs, no keyword anchors).233. **Check** against the typical wire limits in the playbook and list any violations.244. **Distribution**: the user publishes through their wire or PR partner. Any paid distribution needs their explicit approval of plan and price. Recommend pairing the release with an on-site page stating the same facts (releases decay within weeks; the page lasts).255. **Track**: when the user shares the live/report URLs, log them to `offpage-log.csv` (`type=press_release`). After ~7 days, check pickup: `khadinakbar/google-news-scraper` for the brand (paid; ask first) and the brand prompts from `ai-search-visibility` (AI Overviews often repeat syndicated release facts within days). Report what changed.2627## B. Proactive digital PR (data-led)281. Pick a data angle tied to the business (survey, public-data analysis, pricing index, "cost by city/state", industry benchmark). Optional research inputs: `khadinakbar/reddit-posts-comments-scraper` (what people ask), `khadinakbar/google-trends-scraper` (timing), `khadinakbar/software-reviews-all-in-one-scraper` / `trustpilot-reviews-scraper` (review-mining studies).292. Build the asset page on the site (methodology, charts, embed code, quotable stats).303. **Journalist list**: `khadinakbar/google-news-scraper` for the topic over the last 60–90 days → bylines, outlets, article URLs. Contacts via the `outreach` skill (author pages, `bulk-website-contact-extractor`, `email-address-validator`).314. Pitch with template 1 (≤90 words, 2–3 stats matched to each journalist's angle). Follow-ups day 3–4 and +2–3 days. Drafting and sending go through `outreach` (approval-gated).3233## C. Reactive PR (expert-request platforms)34Status of HARO (Help a Reporter Out), checked November 2026: it is running again. Cision closed it in December 2024 (it had been renamed Connectively), sold it to a new owner in April 2025, and that owner restarted the email digests (Cision's announcement: https://www.cision.com/about/press-releases/2025-press-releases/cision-announces-sale-of-help-a-reporter-out-haro-to-featuredcom-302427990/). It has closed and changed hands before, so confirm it is still running, and read its current rules, before relying on it. This is a status note, not a recommendation: Citebase does not recommend any platform. If the user already receives journalist query digests from an expert-request platform and they reach a connected inbox: triage today's queries against the client's real expertise, skip ones that conflict with their stance, and draft answers with template 9 that mirror the journalist's stated angle. Draft only — the user edits and sends; credibility must be human. Never fabricate credentials or personas.3536## Rules37- No fabricated events, awards, quotes or customers; no competitor attacks; no anchor-text stuffing.38- Nothing is published or sent without the user's explicit approval.