Skip to content

ShenyuanNext/wepr-growth-skills / skills/pr-strategy-workbench

pr-strategy-workbench

Verified

规划和审校有证据支撑的公关策略、客户传播方案、媒体叙事、发布前风险控制、公开文案、新闻稿、声明、问答和声誉行动。适用于公关方案、传播策略、议题与舆情评估、竞品或媒体叙事分析、发布风险预案、发言人口径、公共语境文案审校和新闻稿撰写。正在发生的危机应转交 diagnose-pr-crisis。不得虚构事实、来源、引语、公众反应、法律结论或效果承诺。

references/narrative-and-public-copy.md

View on GitHub
# Narrative, public copy, and release workflow

## Narrative analysis

Do not summarize the source. Identify:

1. Main attributable claim and implied audience conclusion.
2. Evidence, sources, comparisons, and missing context.
3. Beneficiary, disadvantaged party, and assumed standard of judgment.
4. Timing, format, distribution, and whether repetition is independently verified.
5. Effect on trust, category expectations, partner decisions, regulatory context, or explanation cost.
6. Recommendation: no action, monitor, correct facts, build an alternative evidence base, engage selectively, or escalate.

Keep three layers separate:

- **observable editorial choices:** ordering, sourcing, comparison, vocabulary, included conditions, and relevant omissions that can be located in the text;
- **possible audience effect:** the interpretation these choices may encourage, which is not proof of actual audience response;
- **intent hypothesis:** only when it changes the recommendation, with supporting evidence, alternatives, and disconfirming signals.

Calibrate the evidence path rather than judging an outlet by reputation. Record whether the item carries public material, adds explanation, contains independent interviews/data, or performs multi-party verification. This describes editorial processing, not a universal quality or truth score. A beneficiary, positive tone, same-day publication, or corporate source dependence does not independently prove paid placement or coordination.

Quote only the minimum necessary text and preserve context. Label motive or coordination claims as unverified unless supported.

## Public-context copy review

Review copy in this order:

1. State intended audience, objective, channel, occasion, and call to action.
2. Extract every factual, comparative, performance, credential, and social-proof claim.
3. Test literal meaning, foreseeable ambiguity, excluded audience interpretation, cropped screenshot, headline, hostile reading, and long-term precedent.
4. Check identity, dignity, vulnerability, tragedy, health, safety, minors, family, labor, class, region, culture, and public-interest sensitivity where relevant.
5. Decide: publish, revise before publishing, or change the underlying concept.
6. Preserve the legitimate objective while removing unsupported or needlessly harmful framing.

Do not treat keywords as proof of risk. Explain the mechanism, affected stakeholder, likelihood, impact, and mitigation.

## Press release workflow

### Intake gate

Confirm who did what, when and where, what changed for whom, the communication objective, target media/audience, and proof available. If the central action is not supported, do not draft a finished release.

### News value

Choose one lead: verified result, new product/service, partnership outcome, research finding, public-interest action, event outcome, or accountable next step. An event itself is rarely the news; identify what was announced, changed, measured, or made available.

Choose one primary release type and keep its evidence logic intact:

- product or service: changed capability, availability, user effect, limits, and proof;
- public-interest action: affected group, actual intervention, governance, resources, and accountable outcome;
- event: decision, launch, agreement, evidence, or material change produced by the event;
- expert view: attributable proposition, reasoning, evidence, countercondition, and relevance;
- annual review: comparable period, important actions, verified results, limitations, and next commitment.

Adapt relevance by audience: consumer-facing releases explain perceptible change; business releases explain operating, channel, or industry effect; public-sector releases explain governance, rules, and public value. Do not change the underlying facts by audience.

### Structure

1. Headline with actor, action, and meaningful result/scope.
2. Lead with essential facts and audience relevance.
3. Evidence and mechanism explaining what changed.
4. Context necessary to interpret the facts.
5. Attributable quote only when it adds a decision, explanation, boundary, or next step.
6. Limitations, availability, eligibility, methodology, or next milestone.
7. Boilerplate and contact information when requested.

### Editing rules

- Prefer concrete actions, data, scope, and mechanisms over self-description.
- Keep plans, pilots, launches, and results in their correct status.
- Preserve measurement definitions, date ranges, comparison bases, and sample limits.
- Do not invent dates, quotes, credentials, endorsements, policies, customer stories, or market conclusions.
- Remove unsupported superlatives, vague corporate jargon, manufactured consensus, and promotional claims disguised as third-party reporting.
- When asked to imitate a publication, analyze user-supplied samples or current examples; do not claim an exact editorial voice from memory.

## Delivery formats

For a review, provide verdict, objective, evidence gaps, material risks, stakeholder readings, screenshot/headline test, recommended edits, and final revised copy. For a release, provide the finished draft plus a short evidence/approval checklist; do not expose internal chain-of-thought or hidden scoring.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall