Token导航 LogoToken导航

Agent Skill · 研究检索

response-coordinator(响应协调员)

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

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

总安装 1,952周安装 83GitHub Stars 85下载 684核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill response-coordinator

这个 Skill 是做什么的

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

response-coordinator 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。它支持通过资源标记实现信息的分类与过滤,提升检索效率。

可通过 npx skills add 命令从指定 GitHub 仓库安装该技能。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill response-c…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

response-coordinator 怎么安装?

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

response-coordinator 支持哪些 AI 工具?

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

response-coordinator 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

response-coordinator 是免费的吗?

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

response-coordinator 用的人多吗?

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

response-coordinator 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
response-coordinator

响应协调员 · 本页

1,95285只读未明确通过

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

SKILL.md 原文

Crisis Response Coordinator

Orchestrate effective crisis response through structured playbooks, clear communication templates, and coordinated team actions.

When to Use This Skill

  • Active crisis situations
  • Building crisis playbooks
  • Training response teams
  • Creating communication templates
  • Post-crisis improvement

Methodology Foundation

Based on Burson-Marsteller crisis playbook and PPRR model (Prevention, Preparedness, Response, Recovery), combining:

  • Incident command structure
  • Stakeholder communication
  • Timeline management
  • Documentation practices

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures response playbookGo/no-go decisions
Drafts communicationsApproval authority
Coordinates timelinesResource deployment
Documents actionsSpokesperson selection
Suggests escalation pathsLegal implications

Instructions

Step 1: Activate Crisis Protocol

Activation Checklist:

  • Confirm crisis status (not false alarm)
  • Identify crisis type and scope
  • Assemble core response team
  • Establish communication channels
  • Begin documentation log

Step 2: Establish Command Structure

Crisis Team Roles:

RoleResponsibilityTypical Owner
Crisis LeadOverall coordinationCEO/COO
Comms LeadExternal messagingCMO/PR Head
Operations LeadFix the problemCTO/VP Ops
Legal CounselLegal guidanceGeneral Counsel
Customer LeadCustomer communicationVP CX
HR LeadInternal/employeeCHRO

Step 3: Execute Response

Response Phases:

PhaseDurationFocus
Contain0-2 hoursStop bleeding, assess scope
Communicate2-4 hoursStakeholder notifications
Resolve4-24 hoursFix root cause
Recover1-7 daysReturn to normal
Learn7-30 daysPost-mortem, improvements

Step 4: Manage Communications

Stakeholder Priority:

StakeholderWhen to NotifyChannel
Internal teamImmediatelySlack/Teams
Board/InvestorsWithin 1 hourCall/Email
Affected customersWithin 2 hoursDirect
All customersWithin 4 hoursEmail/Social
MediaReactivePress statement
PublicAs neededWebsite/Social

Step 5: Document Everything

Crisis Log Template:

TIME | ACTION | OWNER | OUTCOME
-----|--------|-------|--------
10:00 | Alert received | [Name] | Verified
10:15 | Team assembled | [Name] | 5/6 present
10:30 | Root cause identified | [Name] | DB issue
...

Examples

Example 1: Crisis Response Playbook

Input:

Create a crisis response playbook for a data breach scenario.

Output:

## Crisis Playbook: Data Breach

### Severity Classification

| Level | Criteria | Response |
|-------|----------|----------|
| **Critical** | PII exposed, >10K records | Full activation |
| **High** | PII exposed, <10K records | Partial activation |
| **Medium** | Non-PII data exposed | Contained response |
| **Low** | Attempted breach, blocked | Monitor and report |

---

### Activation Trigger

**Automatic activation when:**
- Confirmed unauthorized data access
- Evidence of data exfiltration
- Regulatory notification required
- Media awareness possible

---

## Phase 1: CONTAIN (0-2 Hours)

### Immediate Actions

| Time | Action | Owner | Checklist |
|------|--------|-------|-----------|
| +0 min | Isolate affected systems | IT Security | [ ] |
| +0 min | Preserve forensic evidence | IT Security | [ ] |
| +15 min | Assemble crisis team | Crisis Lead | [ ] |
| +30 min | Brief team on situation | IT Security | [ ] |
| +30 min | Legal notification | Legal | [ ] |
| +1 hr | Scope assessment complete | IT Security | [ ] |
| +1 hr | Impact assessment complete | Ops Lead | [ ] |

### Crisis Team Assembly

**Mandatory Attendees:**
- [ ] CEO (Crisis Lead)
- [ ] CTO (Technical Lead)
- [ ] CISO (Security Lead)
- [ ] General Counsel (Legal Lead)
- [ ] CMO (Communications Lead)
- [ ] VP Customer Success (Customer Lead)

**Optional (as needed):**
- [ ] CHRO (if employee data)
- [ ] CFO (if financial impact)
- [ ] Board liaison

### Initial Assessment Template

BREACH ASSESSMENT

Discovery Time: [TIME] Breach Window: [START] to [END]

Data Involved:

  • Names
  • Email addresses
  • Phone numbers
  • Passwords
  • Payment data
  • SSN/Government ID
  • Health information
  • Other: ___________

Records Affected: [NUMBER] Customers Affected: [NUMBER]

Attack Vector: [DESCRIPTION] Current Status: [CONTAINED/ONGOING] Confidence Level: [HIGH/MEDIUM/LOW]

---

## Phase 2: COMMUNICATE (2-4 Hours)

### Communication Sequence

| Priority | Stakeholder | When | Channel | Owner |
|----------|-------------|------|---------|-------|
| 1 | Board/Investors | +2hr | Call | CEO |
| 2 | Regulators | +2hr | Formal notice | Legal |
| 3 | Affected customers | +3hr | Email | CX Lead |
| 4 | All employees | +3hr | All-hands | HR |
| 5 | Media (if inquiries) | +4hr | Statement | Comms |
| 6 | Public | +4hr | Website | Comms |

---

### Communication Templates

#### Customer Notification (Direct Victims)

Subject: Important Security Notice - Action Required

Dear [Name],

We're writing to inform you about a security incident that may have involved your personal information.

WHAT HAPPENED On [DATE], we discovered unauthorized access to [SYSTEM]. The incident occurred between [DATE] and [DATE].

WHAT INFORMATION WAS INVOLVED Based on our investigation, the following information may have been accessed:

  • [List specific data types]

WHAT WE'RE DOING

  • We immediately secured our systems
  • We engaged cybersecurity experts to investigate
  • We notified law enforcement
  • We are providing [credit monitoring/identity protection]

WHAT YOU CAN DO

  1. [Specific action 1]
  2. [Specific action 2]
  3. [Specific action 3]

CONTACT US If you have questions, please contact our dedicated support line:

  • Phone: [NUMBER] (24/7 for next 30 days)
  • Email: [EMAIL]
  • FAQ: [URL]

We sincerely apologize for this incident and any concern it causes.

[Signature]

#### All-Customer Notification

Subject: Security Update from [Company]

Dear [Customer],

We're writing with an important security update.

On [DATE], we discovered a security incident affecting some customer accounts. We want to be transparent about what happened and what we're doing.

THE INCIDENT [2-3 sentence summary of what happened]

YOUR ACCOUNT Based on our investigation, your account [was / was not] affected. [If affected: See separate email with specific details]

OUR RESPONSE

  • [Action taken 1]
  • [Action taken 2]
  • [Action taken 3]

GOING FORWARD [Steps being taken to prevent future incidents]

We're deeply sorry this occurred and are committed to earning back your trust.

[Signature]

#### Media Statement

STATEMENT FROM [COMPANY] REGARDING SECURITY INCIDENT

[DATE]

[Company] recently discovered unauthorized access to certain company systems. Upon discovery, we immediately took steps to secure our systems and engaged leading cybersecurity experts to investigate.

Based on our investigation:

  • [Key fact 1]
  • [Key fact 2]
  • [Key fact 3]

We have notified the appropriate authorities and are working closely with law enforcement.

Affected individuals are being notified directly and we are providing [specific remediation].

We take the security of our customers' information extremely seriously. We apologize for this incident and are taking steps to prevent similar incidents in the future.

For more information, please visit: [URL]

Media Contact: [Name], [Email]

---

## Phase 3: RESOLVE (4-24 Hours)

### Technical Remediation

| Action | Owner | Deadline | Status |
|--------|-------|----------|--------|
| Patch vulnerability | Security | +6hr | [ ] |
| Reset affected credentials | IT | +8hr | [ ] |
| Deploy additional monitoring | Security | +12hr | [ ] |
| Third-party security audit | Security | +7 days | [ ] |

### Customer Remediation

| Action | Owner | Deadline | Status |
|--------|-------|----------|--------|
| Credit monitoring enrollment | CX | +24hr | [ ] |
| Password reset flow | Product | +24hr | [ ] |
| Support surge staffing | CX | +24hr | [ ] |
| FAQ page live | Marketing | +6hr | [ ] |

---

## Phase 4: RECOVER (1-7 Days)

### Operational Recovery

| Milestone | Target | Owner |
|-----------|--------|-------|
| Normal operations | +24hr | Ops |
| Support queue normal | +72hr | CX |
| Security audit complete | +7 days | Security |
| All notifications sent | +72hr | Legal |

### Communication Recovery

| Activity | Timing | Owner |
|----------|--------|-------|
| Progress update #1 | +24hr | Comms |
| Progress update #2 | +72hr | Comms |
| Final resolution notice | +7 days | Comms |
| Thank you to customers | +14 days | CEO |

---

## Phase 5: LEARN (7-30 Days)

### Post-Incident Review

**Schedule within 7 days of resolution**

Agenda:
1. Timeline reconstruction
2. What worked well
3. What needs improvement
4. Action items for prevention
5. Communication effectiveness
6. Documentation updates

### Playbook Updates

Based on learnings, update:
- [ ] Detection capabilities
- [ ] Response procedures
- [ ] Communication templates
- [ ] Team training
- [ ] Vendor relationships

Example 2: Real-Time Response Coordination

Input:

We're in the middle of a crisis - product recall needed.
Contaminated ingredient found in batch.
What do we do now?

Output:

## ACTIVE CRISIS: Product Recall

### STATUS: PHASE 1 - CONTAIN

---

### IMMEDIATE ACTIONS (Next 60 Minutes)

| # | Action | Owner | Done |
|---|--------|-------|------|
| 1 | STOP all shipments of affected batch | Operations | [ ] |
| 2 | Identify batch numbers affected | QC | [ ] |
| 3 | Pull from retail shelves (notify partners) | Sales | [ ] |
| 4 | Count units sold vs. in inventory | Operations | [ ] |
| 5 | Assemble full crisis team | CEO | [ ] |
| 6 | Contact legal counsel | CEO | [ ] |
| 7 | Notify regulatory authority (FDA/etc) | Legal | [ ] |

---

### INFORMATION NEEDED NOW

Fill in as you gather:

AFFECTED BATCH:

  • Batch number(s): _______________
  • Production date(s): _______________
  • Contamination type: _______________
  • Health risk level: [] Low [] Medium [] High [] Critical

DISTRIBUTION:

  • Units produced: _______________
  • Units shipped: _______________
  • Units in warehouse: _______________
  • Retailers received: _______________
  • Units sold to consumers (est): _______________

CUSTOMERS AT RISK:

  • Can you identify purchasers? [] Yes [] No
  • Geographic distribution: _______________
---

### COMMUNICATION PRIORITY

| Priority | Who | When | Message |
|----------|-----|------|---------|
| 1 | Retail partners | NOW | Stop sales, pull from shelves |
| 2 | Regulatory body | Within 1hr | Formal notification |
| 3 | Identified customers | Within 2hr | Direct recall notice |
| 4 | All customers | Within 4hr | Public recall announcement |
| 5 | Media | As needed | Press statement ready |

---

### HOLDING STATEMENT (Use if media calls NOW)

"We are aware of an issue with [product] and are taking immediate action. Customer safety is our top priority. We will have a full statement within [X] hours.

In the meantime, customers who have purchased [product] should [specific action].

Questions: [contact]"

---

### CUSTOMER COMMUNICATION TEMPLATE

URGENT PRODUCT RECALL NOTICE

[Company] is voluntarily recalling [Product Name] due to potential contamination with [substance].

AFFECTED PRODUCTS:

  • Product: [Name]
  • Batch #: [Numbers]
  • Expiration dates: [Dates]
  • Sold at: [Retailers]

WHAT TO DO:

  1. STOP using the product immediately
  2. [Disposal instructions OR return instructions]
  3. Contact us for full refund: [phone/email/url]

IF YOU'VE CONSUMED THE PRODUCT:

  • [Symptoms to watch for]
  • [When to seek medical attention]
  • [Who to call]

We sincerely apologize for this situation and are taking all steps to ensure this doesn't happen again.

Questions: [24/7 Hotline Number]

---

### NEXT CHECK-IN: 30 MINUTES

At that time, confirm:
- [ ] All shipments stopped
- [ ] Batch scope finalized
- [ ] Retail partners notified
- [ ] Regulatory notification sent
- [ ] Customer communication ready

Skill Boundaries

What This Skill Does Well

  • Structuring response playbooks
  • Creating communication templates
  • Coordinating response timelines
  • Organizing team actions

What This Skill Cannot Do

  • Make legal determinations
  • Access your systems
  • Speak on your behalf
  • Know regulatory requirements

Iteration Guide

Follow-up Prompts:

  • "Create a playbook for [crisis type]"
  • "Draft communication for [stakeholder]"
  • "What should our next 30 minutes look like?"
  • "How do we communicate [specific development]?"

References

  • Burson Crisis Communications
  • PPRR Crisis Management Model
  • FEMA Incident Command System
  • Harvard Business Review Crisis Response

Related Skills

  • crisis-detector - Early warning
  • social-listening - Monitoring
  • reputation-recovery - Post-crisis

Skill Metadata

  • Domain: Crisis
  • Complexity: Advanced
  • Mode: centaur
  • Time to Value: Immediate in crisis
  • Prerequisites: Stakeholder alignment, authority to act

平台分布

Codex

37.15%
按下载量换算254

Claude

30.56%
按下载量换算209

Cursor

19.64%
按下载量换算134

Gemini CLI

8.96%
按下载量换算61

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills