Token导航 LogoToken导航

Agent Skill · 研究检索

pr-crisis-response(公关危机应对)

pr-crisis-response 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

pr-crisis-response 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 59,000。

总安装 396周安装 16GitHub Stars 125下载 124核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pr-crisis-response(公关危机应对)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/pr-crisis-response
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill pr-crisis-response
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill pr-crisis-response

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

pr-crisis-response 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/pr-crisis-response

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/asgard-ai-platform/skills --skill pr-crisis-re…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

pr-crisis-response 怎么安装?

在终端执行 npx skills add https://github.com/asgard-ai-platform/skills --skill pr-crisis-response。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

pr-crisis-response 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

pr-crisis-response 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

pr-crisis-response 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

pr-crisis-response 用的人多吗?

公开数据是累计安装 396 次,近一周安装 16 次,下载 124 次,GitHub 125 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

pr-crisis-response 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
pr-crisis-response

公关危机应对 · 本页

396125需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

PR Crisis Management

Framework

IRON LAW: First Response Within 1 Hour

The first hour after a crisis becomes public is the "golden hour."
Silence in this window = others control the narrative. A holding
statement ("We are aware of [issue] and are investigating. We will
provide an update by [time].") is infinitely better than silence.

Crisis Classification

LevelDescriptionExamplesResponse
Level 1: NoiseMinor complaint, limited reachSingle negative review, individual social postMonitor, respond if needed
Level 2: IssueGrowing attention, media interest possibleMultiple complaints on same topic, minor influencer postProactive response, prepare statement
Level 3: CrisisWidespread media coverage, significant reputation damageProduct recall, data breach, viral scandal, executive misconductFull crisis protocol, C-suite involvement

Crisis Response Protocol

Hour 1: Contain

  1. Activate crisis team (PR, Legal, CEO, relevant department head)
  2. Issue holding statement (acknowledge, don't speculate)
  3. Secure all internal communications (no unauthorized statements)
  4. Begin fact-gathering

Hours 2-6: Respond

  1. Draft full statement using 3C framework
  2. Legal review (balance transparency with liability)
  3. Publish on owned channels first, then distribute to media
  4. Brief customer-facing teams (CS, sales) with talking points

Days 1-7: Manage

  1. Monitor media reaction to response
  2. Issue updates as new information emerges
  3. Respond to media inquiries consistently
  4. Address social media individually where appropriate

Weeks 2-4: Recover

  1. Implement corrective actions (not just promises)
  2. Communicate actions taken
  3. Re-engage positive narratives
  4. Post-mortem: what happened, why, how to prevent

3C Crisis Statement Framework

[CONCERN] We are deeply concerned about [specific situation].
Our thoughts are with [affected parties].

[COMMITMENT] We are taking immediate action:
1. [Specific action 1]
2. [Specific action 2]
3. [Investigation/review underway]

[CONTROL] We have [crisis team/process] in place. We will provide
updates [when and where]. For questions: [contact info].

What NOT to Say

Don'tWhyInstead
"No comment"Implies guilt or indifference"We are investigating and will share findings"
"We're sorry IF anyone was offended"Non-apology, dismissive"We apologize for [specific thing]"
Blame othersLooks defensiveTake responsibility for your part
SpeculateMay be wrong, creates new problems"Here is what we know so far"
MinimizeAlienates affected peopleAcknowledge the seriousness

Output Format

# Crisis Response: {Situation}

## Classification
- Level: 1 (Noise) / 2 (Issue) / 3 (Crisis)
- Type: Product / Personnel / Operational / External
- Current media coverage: {scope}

## Holding Statement (< 1 hour)
{Draft}

## Full Statement (< 6 hours)
{3C framework draft}

## Talking Points (for CS/Sales)
1. {key message}
2. {key message}
3. {redirect: "For further questions, please contact [PR]"}

## Anticipated Questions & Answers
| Question | Answer |
|----------|--------|
| {likely question} | {prepared answer} |

## Recovery Plan
1. {corrective action + timeline}

Gotchas

  • Speed vs accuracy trade-off: In hour 1, prioritize speed with a holding statement. In hours 2-6, prioritize accuracy with the full statement. Never sacrifice accuracy for speed in the full statement.
  • Social media crises escalate in minutes: A viral TikTok or PTT post can reach millions before your crisis team assembles. Pre-written holding statements for common scenarios save critical minutes.
  • Internal leaks are the second crisis: Employees sharing internal discussions on social media compounds the problem. Brief all staff: "All external communication goes through PR."
  • Taiwan media cycle: Taiwan's 24-hour news channels (TVBS, SET, CTV) and online outlets (ETtoday, UDN) amplify stories rapidly. The PTT → news outlet pipeline means a PTT hot post becomes TV news within hours.
  • Apology culture varies: In Taiwan/Japan, a sincere public apology (including bowing) is expected and effective. In the US, apologies are often viewed as liability admission. Calibrate to cultural context.

References

  • For social media crisis playbook, see references/social-crisis.md
  • For post-crisis reputation rebuilding, see references/reputation-recovery.md

平台分布

Codex

35.75%
按下载量换算44

Claude

28.46%
按下载量换算35

Cursor

17.61%
按下载量换算22

Gemini CLI

10.23%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills