Xpersona
agentCLAWHUBUnverified

qa-stakeholder-communication

当需要告诉开发"这个 Bug 必须修"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。 触发场景：怎么沟通、跟开发说、跟PM说、跟领导说、沟通策略、向上汇报、干系人沟通、推动问题解决需要有效沟通时。 Use when the user asks about: communicating test findings to engineers, product managers, and management using role-tailored templates and escalation strategy. Skill: qa-stakeholder-communication Owner: kokxi Summary: 当需要告诉开发"这个 Bug 必须修"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。 触发场景：怎么沟通、跟开发说、跟PM说、跟领导说、沟通策略、向上汇报、干系人沟通、推动问题解决需要有效沟通时。 Use when the user asks about: communicating test findings to engineers, product managers, and management using role-tailored templates and esca

OpenClaw
View on ClawHubHomepage

Rank

62

Safety

84

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.8.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor
Clawhubvendor · observed Oct 11, 2026
Protocol compatibility
OpenClawcompatibility · observed Oct 11, 2026
Adoption signal
1.1K downloadsadoption · observed Oct 11, 2026
Latest release
1.8.0release · observed Sep 29, 2026
Handshake status
UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-stakeholder-communication
  1. Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/snapshot"

Documentation

CLAWHUB

57,687 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: qa-stakeholder-communication
description: >-
  当需要告诉开发"这个 Bug 必须修"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。 触发场景：怎么沟通、跟开发说、跟PM说、跟领导说、沟通策略、向上汇报、干系人沟通、推动问题解决需要有效沟通时。 Use when the user asks about: communicating test findings to engineers, product managers, and management using role-tailored templates and escalation strategy.
license: MIT
allowed-tools: Read Grep Glob
metadata:
  display-name: "Stakeholder Communication"
  version: "1.8.0"
  when-to-use: "用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时"
  related-skills: "{\"upstream\":[\"qa-bug-reporting\",\"qa-release-risk-governance\",\"qa-quality-metrics\"],\"downstream\":[]}"
  references: "[\"references/comms-patterns.md\"]"
  input-format: "{\"required\":[{\"name\":\"测试报告\",\"type\":\"object\",\"description\":\"来自qa-test-reporting的测试报告\"},{\"name\":\"受众分析\",\"type\":\"string\",\"description\":\"报告接收方的角色和信息需求\"}],\"optional\":[{\"name\":\"沟通渠道\",\"type\":\"string\",\"description\":\"可用的沟通渠道和频率\"}]}"
  output-format: "{\"traceability\":[\"每份沟通策略带唯一ID（COMM-XXXX）\"],\"structure\":[\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\"全覆盖/100%\\\"绝对化表述；缺失模块标注\\\"未覆盖+原因\\\"\",{\"communication_plan\":\"沟通计划\"},{\"tailored_report\":\"定制化报告\"},{\"key_metrics\":\"关键指标呈现\"},{\"risk_highlight\":\"风险提示\"}]}"
  error-recovery-guidance: "{\"on_failure\":\"沟通策略未能推动问题解决时回退到问题定位补充\",\"retry_behavior\":\"补充定位后重新设计沟通策略\"}"
  categories: "[\"Development\",\"Team\"]"
  depth-requirement: "{\"reference_value\":\"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\",\"minimum\":\"至少覆盖开发、PM、领导3类角色的沟通策略\"}"
---
> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills

> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。
> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。
> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。

# 干系人沟通

## 核心原则

同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。

## 加载时机

| 什么时候读 | 读哪个 |
|-----------|--------|
| 按受众选沟通话术时 | [`references/comms-patterns.md`](references/comms-patterns.md) |

> `三类沟通模式`的完整内容已下沉至 `references/comms-patterns.md`，避免每次触发都占用上下文。

## 高危表达对比

| 场景 | 不要说 | 可以说 |
|------|--------|--------|
| Bug修复延迟 | "开发没时间" | "这个Bug涉及核心逻辑，需要更多时间确保质量" |
| 测试延期 | "测试做不完" | "为了保证质量，建议延长2天测试时间" |
| 质量问题 | "质量很差" "这个功能有风险" | "这个功能需要更多测试时间" |
| 资源不足 | "人不够" | "为了按时交付，建议增加1名测试人员" |
| 需求变更 | "需求又变了" | "这个变更会影响测试范围，建议重新评估时间" |

## 沟通场景模板

### 场景1：Bug评审会

```text
参会角色：开发、测试、PM
沟通内容：
├─ 测试：Bug描述、复现步骤、影响范围
├─ 开发：根因分析、修复方案、修复时间
└─ PM：优先级评估、资源协调
```

### 场景2：发布评审会

```text
参会角色：开发、测试、PM、运维
沟通内容：
├─ 测试：测试结果、质量评估、风险提示
├─ 开发：变更内容、技术风险
├─ PM：业务影响、发布决策
└─ 运维：部署方案、回滚方案
```

### 场景3：质量报告

```text
报告对象：老板、PM
报告内容：
├─ 质量指标：缺陷密度、漏测率
├─ 质量趋势：改善/稳定/恶化
├─ 风险提示：高风险区域
└─ 改进建议：建议措施
```

## 应用场景

**发现一个支付Bug，需要同步给不同角色**
→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）
→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）
→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）

**Bug评审会上开发说"这个没问题"**
→ 沟通场景应对：用数据和截图说话，避免"我觉得"，使用"数据显示"

## 自检清单

沟通完成后检查：
- [ ] 是否针对受众定制了信息？
- [ ] 是否包含了对方需要的决策信息？
- [

_meta.json

{
  "ownerId": "kn71y9b23csfx0ykgm55d5m9x5891zt8",
  "slug": "qa-stakeholder-communication",
  "version": "1.8.0",
  "publishedAt": 1790656112831
}

references/comms-patterns.md

# 三类沟通模式详解

> 本文是 `qa-stakeholder-communication` 的**三类沟通模式详解**。按受众选沟通话术时读本文；
其余部分留在 SKILL.md，不必读本文。

---


### 模式1：跟开发说（技术视角）

```text
沟通重点：
├─ 精确的复现步骤：每一步操作
├─ 日志/截图：错误信息、异常堆栈
├─ 根因推测：可能的原因
├─ 环境信息：浏览器、系统、配置
└─ 影响范围：哪些功能受影响

沟通格式：
[Bug标题] [严重程度]
复现步骤：
1. ...
2. ...
3. ...
错误日志：[日志内容]
截图：[截图描述]
推测原因：[原因分析]
影响范围：[影响描述]
```

### 模式2：跟PM说（业务视角）

```text
沟通重点：
├─ 用户影响：哪些用户受影响
├─ 严重程度：业务影响多大
├─ 修复优先级：建议优先级
├─ 对其他功能的阻塞
└─ 预计修复时间

沟通格式：
[Bug标题]
影响：[用户范围]
严重程度：[业务影响]
优先级：[P0-P3]
阻塞：[是否阻塞其他功能]
预计修复：[时间估算]
```

### 模式3：跟老板说（决策视角）

```text
沟通重点：
├─ 业务影响：对业务的影响
├─ 发布风险：是否影响发布
├─ 建议决策：建议怎么做
├─ 要什么资源：需要什么支持
└─ 时间节点：什么时候能解决

沟通格式：
[问题描述]
业务影响：[影响描述]
发布风险：[风险评估]
建议决策：[建议方案]
资源需求：[需要什么]
时间节点：[时间计划]
```

skill-card.md

## Description:

Helps QA teams communicate test findings and release risks to engineers, product managers, and leaders with audience-specific templates.

This skill is ready for commercial/non-commercial use.

## Publisher:

[kokxi](https://clawhub.ai/user/kokxi)

### License/Terms of Use:

MIT-0

## Use Case:

QA practitioners use this skill to tailor bug reports, quality updates, and release-risk discussions for developers, product managers, and decision-makers.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: QA examples may expose customer, payment, identity, or production details if copied into prompts.

Mitigation: Mask sensitive data and use synthetic or sanitized examples instead of real production evidence.

Risk: The optional installation suggestion does not pin a source version.

Mitigation: Verify the publisher, source, and version before running the suggested installation command.

## Reference(s):

- [Stakeholder communication patterns](references/comms-patterns.md)
- [ClawHub skill listing](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)

## Skill Output:

**Output Type(s):** [Text, Markdown, Guidance]

**Output Format:** [Audience-tailored communication plans and report templates]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Communication strategy IDs use COMM-XXXX; coverage statements state their basis and identify uncovered areas.]

## Skill Version(s):

1.8.0 (source: frontmatter and release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Related agents

Same protocol, similar job.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW
Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW
Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW
Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular

OPENCLAW

Machine-readable data

The same record, as JSON, for agents and crawlers.

{
  "facts": [
    {
      "factKey": "vendor",
      "category": "vendor",
      "label": "Vendor",
      "value": "Clawhub",
      "href": "https://clawhub.ai/kokxi/skills/qa-stakeholder-communication",
      "sourceUrl": "https://clawhub.ai/kokxi/skills/qa-stakeholder-communication",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-10-11T07:35:12.729Z",
      "isPublic": true
    },
    {
      "factKey": "protocols",
      "category": "compatibility",
      "label": "Protocol compatibility",
      "value": "OpenClaw",
      "href": "https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/contract",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/contract",
      "sourceType": "contract",
      "confidence": "medium",
      "observedAt": "2026-10-11T07:35:12.729Z",
      "isPublic": true
    },
    {
      "factKey": "traction",
      "category": "adoption",
      "label": "Adoption signal",
      "value": "1.1K downloads",
      "href": "https://clawhub.ai/kokxi/qa-stakeholder-communication",
      "sourceUrl": "https://clawhub.ai/kokxi/qa-stakeholder-communication",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-10-11T07:35:12.729Z",
      "isPublic": true
    },
    {
      "factKey": "latest_release",
      "category": "release",
      "label": "Latest release",
      "value": "1.8.0",
      "href": "https://clawhub.ai/kokxi/qa-stakeholder-communication",
      "sourceUrl": "https://clawhub.ai/kokxi/qa-stakeholder-communication",
      "sourceType": "release",
      "confidence": "medium",
      "observedAt": "2026-09-29T04:28:32.831Z",
      "isPublic": true
    },
    {
      "factKey": "handshake_status",
      "category": "security",
      "label": "Handshake status",
      "value": "UNKNOWN",
      "href": "https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/trust",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/trust",
      "sourceType": "trust",
      "confidence": "medium",
      "observedAt": null,
      "isPublic": true
    }
  ],
  "events": [
    {
      "eventType": "release",
      "title": "Release 1.8.0",
      "description": "**Summary:** Major refactor for modularization and streamlined context management. - Moved all \"三类沟通模式\"（stakeholder communication patterns）content from SKILL.md to a new references/comms-patterns.md file to reduce context size and enable on-demand loading. - Refactored SKILL.md metadata: now includes license info, compact fields, and machine-readable formats for tool integration. - Updated and clarified usage description, triggers, and improved English summary. - Dropped the deprecated skill-card.md file, reducing duplication. - No functional changes to outputs; all role-specific communication templates still available via reference file.",
      "href": "https://clawhub.ai/kokxi/qa-stakeholder-communication",
      "sourceUrl": "https://clawhub.ai/kokxi/qa-stakeholder-communication",
      "sourceType": "release",
      "confidence": "medium",
      "observedAt": "2026-09-29T04:28:32.831Z",
      "isPublic": true
    }
  ]
}

Record generated Oct 11, 2026.

Sponsored

Ads related to qa-stakeholder-communication and adjacent AI workflows.