Token导航 LogoToken导航TokenDH.com
运维和基础设施需要联网github未标认证来源可访问许可证需确认审计通过

crisis-response危机应对

Agent Skill

crisis-response 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

564

周安装

24

GitHub Stars

66

下载量

198
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill crisis-response

简介

crisis-response 评估危机严重性并生成结构化应对计划,包括受众分析与传播时间表。

  • 适用于在 Codex、Claude、Cursor、Gemini CLI 中快速响应服务中断或负面舆论事件。
  • 自动分类 P1-P4 级别,输出各利益相关方沟通脚本与责任分工建议。
  • 需用户提供事件详情与当前进展,输出为文本预案,需人工复核后执行。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

/dm:crisis-response

Purpose

Provide rapid crisis assessment and a structured response plan. Classifies severity, identifies stakeholders, drafts messaging for each audience, and builds a communication timeline to contain damage and rebuild trust.

Input Required

The user must provide (or will be prompted for):

  • What happened: Description of the crisis or incident
  • When it started: Timeline of events so far
  • Current exposure: How widely known is it (internal only, social media, press coverage)
  • Stakeholders affected: Customers, employees, investors, partners, public
  • Actions taken so far: Any statements, fixes, or responses already issued
  • Spokesperson: Who will speak for the brand

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/dm:brand-setup)?" — or proceed with defaults.
  2. Severity classification: Level 1 (monitor), Level 2 (respond), Level 3 (full mobilization) based on reach, impact, and trajectory
  3. Assess the narrative: What is being said? What is the public sentiment? What is the worst-case escalation?
  4. Identify all stakeholder groups and prioritize communication order
  5. Draft holding statement for immediate release (within first hour)
  6. Draft tailored messaging per stakeholder: customers, employees, media, partners, social media
  7. Build communication timeline: first hour, first 24 hours, first week, ongoing
  8. Define channel strategy: which messages go where (social, email, press, internal comms)
  9. Outline recovery plan: corrective actions, transparency updates, trust-rebuilding initiatives
  10. Set monitoring cadence and escalation triggers

Output

A structured crisis response plan containing:

  • Severity classification with rationale
  • Situation assessment and narrative analysis
  • Holding statement (ready to publish)
  • Stakeholder-specific messaging (customers, media, employees, partners)
  • Communication timeline with milestones and decision points
  • Channel deployment plan
  • Social media response guidelines (what to reply, what to ignore, when to escalate)
  • Recovery and trust-rebuilding roadmap
  • Monitoring plan with escalation triggers

Agents Used

  • brand-guardian — Brand protection, messaging consistency, stakeholder communication, compliance
  • pr-outreach — Media relations, press statement, journalist engagement strategy

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

31.44%
按下载量换算62

Claude

29.3%
按下载量换算58

Cursor

19.6%
按下载量换算39

Gemini CLI

10.1%
按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills