{"id":"65c36005-372a-427d-a3cd-3ec460c3f0d4","entityType":"agent","slug":"clawhub-kokxi-qa-stakeholder-communication","name":"qa-stakeholder-communication","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kokxi-qa-stakeholder-communication","canonicalPath":"/agent/clawhub-kokxi-qa-stakeholder-communication","generatedAt":"2026-10-11T10:51:31.410Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T07:35:12.729Z","emptyReason":null},"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. 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","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-stakeholder-communication","sourceUrl":"https://clawhub.ai/kokxi/qa-stakeholder-communication","homepage":"https://clawhub.ai/kokxi/skills/qa-stakeholder-communication","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kokxi/qa-stakeholder-communication","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kokxi/skills/qa-stakeholder-communication","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:35:12.729Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:35:12.729Z","emptyReason":null},"stars":null,"forks":null,"downloads":1122,"packageName":null,"latestVersion":"1.8.0","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:35:12.662Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T07:35:12.729Z","lastCrawledAt":"2026-10-11T07:35:12.662Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T07:35:12.662Z","lastVerifiedAt":null,"highlights":[{"version":"1.8.0","createdAt":"2026-09-29T04:28:32.831Z","changelog":"**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.","fileCount":4,"zipByteSize":5353},{"version":"1.7.7","createdAt":"2026-09-27T14:41:03.241Z","changelog":"1.7.7","fileCount":3,"zipByteSize":4641},{"version":"1.7.6","createdAt":"2026-09-01T12:45:59.444Z","changelog":"显示名改中文","fileCount":3,"zipByteSize":4860},{"version":"1.7.5","createdAt":"2026-08-30T15:19:03.470Z","changelog":"1.7.5: 版本号升级","fileCount":3,"zipByteSize":4735},{"version":"1.7.0","createdAt":"2026-08-16T14:32:46.867Z","changelog":"- Removed skill-card.md file. - Updated SKILL.md metadata to version 1.7.0. - No changes to skill functionality or content structure. - Minor maintenance and file cleanup.","fileCount":3,"zipByteSize":4454},{"version":"1.6.3","createdAt":"2026-08-12T15:27:59.667Z","changelog":"- Updated SKILL.md with metadata fields \"slug\" and \"displayName\" - Incremented version to 1.6.3 - Removed the skill-card.md file - No changes to core communication templates or strategies","fileCount":3,"zipByteSize":4483},{"version":"1.6.0","createdAt":"2026-07-06T17:17:39.881Z","changelog":"Version 1.6.0 (qa-stakeholder-communication) - Expanded \"when_to_use\" keywords，新增“干系人沟通”等 - Updated output_format: 现包含沟通策略唯一ID（COMM-XXXX）以强化可追溯性 - 增加categories分类标签（Development, Team） - 明确沟通深度要求，并提供参考倍数/最低标准说明 - 新增error_recovery_guidance：沟通失败时指引回到问题定位并补充 - 增加安全警告，提醒脱敏数据处理和结果局限 - 新增最终检查清单，进一步细化沟通确认项 - 移除 skill-card.md 文件","fileCount":3,"zipByteSize":4581},{"version":"1.5.0","createdAt":"2026-06-29T12:43:37.696Z","changelog":"qa-stakeholder-communication 1.5.0 - Refined and expanded skill description with more explicit role-based communication guidance. - Added version field to SKILL.md and restructured input/output format specifications to use structured fields. - Improved clarity of sample scenarios and examples, aligning them with audience-specific communication best practices. - Removed skill-card.md for simplification.","fileCount":3,"zipByteSize":3988}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-stakeholder-communication","setupComplexity":"low","setupSteps":["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.","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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T10:51:31.409Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-stakeholder-communication/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T07:35:12.729Z","emptyReason":null},"readme":"Skill: qa-stakeholder-communication\n\nOwner: kokxi\n\nSummary: 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。 触发场景：怎么沟通、跟开发说、跟PM说、跟领导说、沟通策略、向上汇报、干系人沟通、推动问题解决需要有效沟通时。 Use when the user asks about: communicating test findings to engineers, product managers, and management using role-tailored templates and escalation strategy.\n\nTags: latest:1.8.0\n\nVersion history:\n\nv1.8.0 | 2026-09-29T04:28:32.831Z | auto\n\n**Summary:** Major refactor for modularization and streamlined context management.\n\n- 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.\n- Refactored SKILL.md metadata: now includes license info, compact fields, and machine-readable formats for tool integration.\n- Updated and clarified usage description, triggers, and improved English summary.\n- Dropped the deprecated skill-card.md file, reducing duplication.\n- No functional changes to outputs; all role-specific communication templates still available via reference file.\n\nv1.7.7 | 2026-09-27T14:41:03.241Z | user\n\n1.7.7\n\nv1.7.6 | 2026-09-01T12:45:59.444Z | user\n\n显示名改中文\n\nv1.7.5 | 2026-08-30T15:19:03.470Z | user\n\n1.7.5: 版本号升级\n\nv1.7.0 | 2026-08-16T14:32:46.867Z | auto\n\n- Removed skill-card.md file.\n- Updated SKILL.md metadata to version 1.7.0.\n- No changes to skill functionality or content structure.\n- Minor maintenance and file cleanup.\n\nv1.6.3 | 2026-08-12T15:27:59.667Z | auto\n\n- Updated SKILL.md with metadata fields \"slug\" and \"displayName\"\n- Incremented version to 1.6.3\n- Removed the skill-card.md file\n- No changes to core communication templates or strategies\n\nv1.6.0 | 2026-07-06T17:17:39.881Z | auto\n\nVersion 1.6.0 (qa-stakeholder-communication)\n\n- Expanded \"when_to_use\" keywords，新增“干系人沟通”等\n- Updated output_format: 现包含沟通策略唯一ID（COMM-XXXX）以强化可追溯性\n- 增加categories分类标签（Development, Team）\n- 明确沟通深度要求，并提供参考倍数/最低标准说明\n- 新增error_recovery_guidance：沟通失败时指引回到问题定位并补充\n- 增加安全警告，提醒脱敏数据处理和结果局限\n- 新增最终检查清单，进一步细化沟通确认项\n- 移除 skill-card.md 文件\n\nv1.5.0 | 2026-06-29T12:43:37.696Z | auto\n\nqa-stakeholder-communication 1.5.0\n\n- Refined and expanded skill description with more explicit role-based communication guidance.\n- Added version field to SKILL.md and restructured input/output format specifications to use structured fields.\n- Improved clarity of sample scenarios and examples, aligning them with audience-specific communication best practices.\n- Removed skill-card.md for simplification.\n\nv1.4.1 | 2026-06-25T16:56:41.959Z | auto\n\n- Summary: Refined skill documentation and removed redundant files for clarity and accuracy.\n- Updated SKILL.md description for improved clarity and focus on use cases.\n- Removed the redundant skill-card.md file.\n- No changes to functionality or communication templates—content, structure, and examples remain consistent.\n- Documentation is now more concise and better aligned with actual user triggers and outputs.\n\nv1.4.0 | 2026-06-24T05:12:24.375Z | auto\n\nVersion 1.4.0 - Enhanced scope and streamlined content\n\n- Expanded description and trigger conditions for broader communication scenarios (包括向上汇报、冲突解决等).\n- Added keywords to clarify use cases and improve discoverability.\n- Improved clarity and structure in guidelines, modes, and examples.\n- Updated \"when_to_use\" and description to cover more real-world stakeholder communication triggers.\n- Removed redundant file: skill-card.md.\n\nv1.3.0 | 2026-06-23T00:35:39.225Z | auto\n\n- Added comprehensive communication templates tailored for developers, PMs, and executives.\n- Defined core principles and audience-specific focus areas for stakeholder conversations.\n- Included scenario-based templates for bug reviews, release meetings, and quality reports.\n- Provided high-risk vs. recommended phrasing guidelines to avoid communication pitfalls.\n- Introduced a communication checklist to ensure effective and targeted messaging.\n\nArchive index:\n\nArchive v1.8.0: 4 files, 5353 bytes\n\nFiles: references/comms-patterns.md (1589b), skill-card.md (1786b), SKILL.md (5746b), _meta.json (147b)\n\nFile v1.8.0:SKILL.md\n\n---\nname: qa-stakeholder-communication\ndescription: >-\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。 触发场景：怎么沟通、跟开发说、跟PM说、跟领导说、沟通策略、向上汇报、干系人沟通、推动问题解决需要有效沟通时。 Use when the user asks about: communicating test findings to engineers, product managers, and management using role-tailored templates and escalation strategy.\nlicense: MIT\nallowed-tools: Read Grep Glob\nmetadata:\n display-name: \"Stakeholder Communication\"\n version: \"1.8.0\"\n when-to-use: \"用户说\\\"怎么沟通\\\"、\\\"跟开发说\\\"、\\\"跟PM说\\\"、\\\"跟领导说\\\"、\\\"沟通策略\\\"、\\\"向上汇报\\\"、\\\"干系人沟通\\\"、需要与不同角色沟通、推动问题解决需要有效沟通时\"\n related-skills: \"{\\\"upstream\\\":[\\\"qa-bug-reporting\\\",\\\"qa-release-risk-governance\\\",\\\"qa-quality-metrics\\\"],\\\"downstream\\\":[]}\"\n references: \"[\\\"references/comms-patterns.md\\\"]\"\n input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"测试报告\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-reporting的测试报告\\\"},{\\\"name\\\":\\\"受众分析\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"报告接收方的角色和信息需求\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"沟通渠道\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"可用的沟通渠道和频率\\\"}]}\"\n output-format: \"{\\\"traceability\\\":[\\\"每份沟通策略带唯一ID（COMM-XXXX）\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"communication_plan\\\":\\\"沟通计划\\\"},{\\\"tailored_report\\\":\\\"定制化报告\\\"},{\\\"key_metrics\\\":\\\"关键指标呈现\\\"},{\\\"risk_highlight\\\":\\\"风险提示\\\"}]}\"\n error-recovery-guidance: \"{\\\"on_failure\\\":\\\"沟通策略未能推动问题解决时回退到问题定位补充\\\",\\\"retry_behavior\\\":\\\"补充定位后重新设计沟通策略\\\"}\"\n categories: \"[\\\"Development\\\",\\\"Team\\\"]\"\n depth-requirement: \"{\\\"reference_value\\\":\\\"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少覆盖开发、PM、领导3类角色的沟通策略\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 干系人沟通\n\n## 核心原则\n\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 按受众选沟通话术时 | [`references/comms-patterns.md`](references/comms-patterns.md) |\n\n> `三类沟通模式`的完整内容已下沉至 `references/comms-patterns.md`，避免每次触发都占用上下文。\n\n## 高危表达对比\n\n| 场景 | 不要说 | 可以说 |\n|------|--------|--------|\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\n\n## 沟通场景模板\n\n### 场景1：Bug评审会\n\n```text\n参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调\n```\n\n### 场景2：发布评审会\n\n```text\n参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案\n```\n\n### 场景3：质量报告\n\n```text\n报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施\n```\n\n## 应用场景\n\n**发现一个支付Bug，需要同步给不同角色**\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\n\n**Bug评审会上开发说\"这个没问题\"**\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\n\n## 自检清单\n\n沟通完成后检查：\n- [ ] 是否针对受众定制了信息？\n- [ ] 是否包含了对方需要的决策信息？\n- [ ] 是否避免了高危表达？\n- [ ] 是否达成了沟通目标？\n\n\n## 检查清单\n\n- [ ] 受众角色是否识别？\n- [ ] 沟通策略是否定制？\n- [ ] 关键信息是否突出？\n- [ ] 推动方案是否可行？\n- [ ] 反馈机制是否建立？\n\nFile v1.8.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.8.0\",\n \"publishedAt\": 1790656112831\n}\n\nFile v1.8.0:references/comms-patterns.md\n\n# 三类沟通模式详解\n\n> 本文是 `qa-stakeholder-communication` 的**三类沟通模式详解**。按受众选沟通话术时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 模式1：跟开发说（技术视角）\n\n```text\n沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]\n```\n\n### 模式2：跟PM说（业务视角）\n\n```text\n沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]\n```\n\n### 模式3：跟老板说（决策视角）\n\n```text\n沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]\n```\n\nFile v1.8.0:skill-card.md\n\n## Description:\n\nHelps QA teams communicate test findings and release risks to engineers, product managers, and leaders with audience-specific templates.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA practitioners use this skill to tailor bug reports, quality updates, and release-risk discussions for developers, product managers, and decision-makers.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: QA examples may expose customer, payment, identity, or production details if copied into prompts.\n\nMitigation: Mask sensitive data and use synthetic or sanitized examples instead of real production evidence.\n\nRisk: The optional installation suggestion does not pin a source version.\n\nMitigation: Verify the publisher, source, and version before running the suggested installation command.\n\n## Reference(s):\n\n- [Stakeholder communication patterns](references/comms-patterns.md)\n- [ClawHub skill listing](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Audience-tailored communication plans and report templates]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Communication strategy IDs use COMM-XXXX; coverage statements state their basis and identify uncovered areas.]\n\n## Skill Version(s):\n\n1.8.0 (source: frontmatter and release evidence)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.7.7: 3 files, 4641 bytes\n\nFiles: skill-card.md (1724b), SKILL.md (6664b), _meta.json (147b)\n\nFile v1.7.7:SKILL.md\n\n---\nname: qa-stakeholder-communication\nslug: qa-stakeholder-communication\ndisplayName: Stakeholder Communication\nversion: 1.7.7\ndescription: >-\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\n\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时\nallowed-tools: Read Grep Glob\nrelated_skills:\n upstream:\n - qa-bug-reporting # 输入：Bug报告\n - qa-release-risk-governance # 输入：发布风险评估\n - qa-quality-metrics # 输入：质量度量数据\n downstream: [] # 输出用于沟通\ninput_format:\n required:\n - name: 测试报告\n type: object\n description: 来自qa-test-reporting的测试报告\n - name: 受众分析\n type: string\n description: 报告接收方的角色和信息需求\n optional:\n - name: 沟通渠道\n type: string\n description: 可用的沟通渠道和频率\noutput_format:\n traceability:\n - 每份沟通策略带唯一ID（COMM-XXXX）\n structure:\n - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n - communication_plan: 沟通计划\n - tailored_report: 定制化报告\n - key_metrics: 关键指标呈现\n - risk_highlight: 风险提示\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n reference_value: \"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖开发、PM、领导3类角色的沟通策略\"\nerror_recovery_guidance:\n on_failure: \"沟通策略未能推动问题解决时回退到问题定位补充\"\n retry_behavior: \"补充定位后重新设计沟通策略\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 干系人沟通\n\n## 核心原则\n\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\n\n## 三类沟通模式\n\n### 模式1：跟开发说（技术视角）\n\n```text\n沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]\n```\n\n### 模式2：跟PM说（业务视角）\n\n```text\n沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]\n```\n\n### 模式3：跟老板说（决策视角）\n\n```text\n沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]\n```\n\n## 高危表达对比\n\n| 场景 | 不要说 | 可以说 |\n|------|--------|--------|\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\n\n## 沟通场景模板\n\n### 场景1：Bug评审会\n\n```text\n参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调\n```\n\n### 场景2：发布评审会\n\n```text\n参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案\n```\n\n### 场景3：质量报告\n\n```text\n报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施\n```\n\n## 应用场景\n\n**发现一个支付Bug，需要同步给不同角色**\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\n\n**Bug评审会上开发说\"这个没问题\"**\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\n\n## 自检清单\n\n沟通完成后检查：\n- [ ] 是否针对受众定制了信息？\n- [ ] 是否包含了对方需要的决策信息？\n- [ ] 是否避免了高危表达？\n- [ ] 是否达成了沟通目标？\n\n\n## 检查清单\n\n- [ ] 受众角色是否识别？\n- [ ] 沟通策略是否定制？\n- [ ] 关键信息是否突出？\n- [ ] 推动方案是否可行？\n- [ ] 反馈机制是否建立？\n\nFile v1.7.7:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.7.7\",\n \"publishedAt\": 1790520063241\n}\n\nFile v1.7.7:skill-card.md\n\n## Description:\n\nProvides Chinese-language communication strategies and templates for presenting QA findings to developers, product managers, and leadership.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA practitioners use this skill to tailor bug reports, release-risk updates, and quality summaries for developers, product managers, and leadership.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Bug reports, screenshots, and examples may expose customer, payment, identification, or production data.\n\nMitigation: Redact sensitive details before supplying reports, logs, or screenshots to the skill.\n\nRisk: Broad communication triggers may invoke the skill for unrelated generic questions.\n\nMitigation: Confirm that the request concerns QA stakeholder communication before using its templates.\n\n## Reference(s):\n\n- [QA Stakeholder Communication on ClawHub](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Role-specific communication templates and reports in Markdown]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Communication plans, key metrics, risk highlights, and COMM-XXXX traceability IDs.]\n\n## Skill Version(s):\n\n1.7.7 (source: frontmatter and server-resolved release)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.7.6: 3 files, 4860 bytes\n\nFiles: skill-card.md (1856b), SKILL.md (7144b), _meta.json (147b)\n\nFile v1.7.6:SKILL.md\n\n---\r\nname: qa-stakeholder-communication\r\nslug: qa-stakeholder-communication\r\ndisplayName: 测试干系人沟通\r\nversion: 1.7.5\r\ndescription: >-\r\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\r\n 本技能属于 QA Test Skills 技能集（49 个技能之一），完整工作流体验需安装全套：npx skills add Kokxi/qa-test-skills\r\n\r\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时\r\nallowed-tools: Read Grep Glob\r\nrelated_skills:\r\n upstream:\r\n - qa-bug-reporting # 输入：Bug报告\r\n - qa-release-risk-governance # 输入：发布风险评估\r\n - qa-quality-metrics # 输入：质量度量数据\r\n downstream: [] # 输出用于沟通\r\ninput_format:\r\n required:\r\n - name: 测试报告\r\n type: object\r\n description: 来自qa-test-reporting的测试报告\r\n - name: 受众分析\r\n type: string\r\n description: 报告接收方的角色和信息需求\r\n optional:\r\n - name: 沟通渠道\r\n type: string\r\n description: 可用的沟通渠道和频率\r\noutput_format:\r\n traceability:\r\n - 每份沟通策略带唯一ID（COMM-XXXX）\r\n structure:\r\n - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\r\n - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\r\n - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\r\n - communication_plan: 沟通计划\r\n - tailored_report: 定制化报告\r\n - key_metrics: 关键指标呈现\r\n - risk_highlight: 风险提示\r\ncategories: ['Development','Team']\r\ndepth_requirement_quantification:\r\n reference_value: \"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\"\r\n minimum: \"至少覆盖开发、PM、领导3类角色的沟通策略\"\r\nerror_recovery_guidance:\r\n on_failure: \"沟通策略未能推动问题解决时回退到问题定位补充\"\r\n retry_behavior: \"补充定位后重新设计沟通策略\"\r\n---\r\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\r\n\r\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\r\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 干系人沟通\r\n\r\n## 核心原则\r\n\r\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\r\n\r\n## 三类沟通模式\r\n\r\n### 模式1：跟开发说（技术视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 精确的复现步骤：每一步操作\r\n├─ 日志/截图：错误信息、异常堆栈\r\n├─ 根因推测：可能的原因\r\n├─ 环境信息：浏览器、系统、配置\r\n└─ 影响范围：哪些功能受影响\r\n\r\n沟通格式：\r\n[Bug标题] [严重程度]\r\n复现步骤：\r\n1. ...\r\n2. ...\r\n3. ...\r\n错误日志：[日志内容]\r\n截图：[截图描述]\r\n推测原因：[原因分析]\r\n影响范围：[影响描述]\r\n```\r\n\r\n### 模式2：跟PM说（业务视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 用户影响：哪些用户受影响\r\n├─ 严重程度：业务影响多大\r\n├─ 修复优先级：建议优先级\r\n├─ 对其他功能的阻塞\r\n└─ 预计修复时间\r\n\r\n沟通格式：\r\n[Bug标题]\r\n影响：[用户范围]\r\n严重程度：[业务影响]\r\n优先级：[P0-P3]\r\n阻塞：[是否阻塞其他功能]\r\n预计修复：[时间估算]\r\n```\r\n\r\n### 模式3：跟老板说（决策视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 业务影响：对业务的影响\r\n├─ 发布风险：是否影响发布\r\n├─ 建议决策：建议怎么做\r\n├─ 要什么资源：需要什么支持\r\n└─ 时间节点：什么时候能解决\r\n\r\n沟通格式：\r\n[问题描述]\r\n业务影响：[影响描述]\r\n发布风险：[风险评估]\r\n建议决策：[建议方案]\r\n资源需求：[需要什么]\r\n时间节点：[时间计划]\r\n```\r\n\r\n## 高危表达对比\r\n\r\n| 场景 | 不要说 | 可以说 |\r\n|------|--------|--------|\r\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\r\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\r\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\r\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\r\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\r\n\r\n## 沟通场景模板\r\n\r\n### 场景1：Bug评审会\r\n\r\n```text\r\n参会角色：开发、测试、PM\r\n沟通内容：\r\n├─ 测试：Bug描述、复现步骤、影响范围\r\n├─ 开发：根因分析、修复方案、修复时间\r\n└─ PM：优先级评估、资源协调\r\n```\r\n\r\n### 场景2：发布评审会\r\n\r\n```text\r\n参会角色：开发、测试、PM、运维\r\n沟通内容：\r\n├─ 测试：测试结果、质量评估、风险提示\r\n├─ 开发：变更内容、技术风险\r\n├─ PM：业务影响、发布决策\r\n└─ 运维：部署方案、回滚方案\r\n```\r\n\r\n### 场景3：质量报告\r\n\r\n```text\r\n报告对象：老板、PM\r\n报告内容：\r\n├─ 质量指标：缺陷密度、漏测率\r\n├─ 质量趋势：改善/稳定/恶化\r\n├─ 风险提示：高风险区域\r\n└─ 改进建议：建议措施\r\n```\r\n\r\n## 应用场景\r\n\r\n**发现一个支付Bug，需要同步给不同角色**\r\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\r\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\r\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\r\n\r\n**Bug评审会上开发说\"这个没问题\"**\r\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\r\n\r\n## 自检清单\r\n\r\n沟通完成后检查：\r\n- [ ] 是否针对受众定制了信息？\r\n- [ ] 是否包含了对方需要的决策信息？\r\n- [ ] 是否避免了高危表达？\r\n- [ ] 是否达成了沟通目标？\r\n\r\n\r\n## 检查清单\r\n\r\n- [ ] 受众角色是否识别？\r\n- [ ] 沟通策略是否定制？\r\n- [ ] 关键信息是否突出？\r\n- [ ] 推动方案是否可行？\r\n- [ ] 反馈机制是否建立？\n\nFile v1.7.6:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.7.6\",\n \"publishedAt\": 1788266759444\n}\n\nFile v1.7.6:skill-card.md\n\n## Description:\n\nHelps QA practitioners tailor stakeholder communication for developers, product managers, and leaders when explaining bugs, requirement changes, quality risks, and release decisions.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers and test leads use this skill to adapt bug, quality, and release-risk communication for technical, product, and management audiences. It provides audience-specific message structures, report templates, and checklists for driving decisions.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The optional full QA Test Skills install command is unpinned.\n\nMitigation: Review the source before installation and prefer a pinned version or immutable commit.\n\nRisk: Communication examples may involve customer, payment, identity, or production data.\n\nMitigation: Mask or remove sensitive data before using the skill in prompts or generated reports.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n- [ClawHub publisher profile](https://clawhub.ai/user/kokxi)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown and structured communication templates]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include communication plans, tailored reports, key metrics, risk highlights, and checklist items.]\n\n## Skill Version(s):\n\n1.7.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.7.5: 3 files, 4735 bytes\n\nFiles: skill-card.md (2017b), SKILL.md (6664b), _meta.json (147b)\n\nFile v1.7.5:SKILL.md\n\n---\nname: qa-stakeholder-communication\nslug: qa-stakeholder-communication\ndisplayName: Stakeholder Communication\nversion: 1.7.5\ndescription: >-\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\n\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时\nallowed-tools: Read Grep Glob\nrelated_skills:\n upstream:\n - qa-bug-reporting # 输入：Bug报告\n - qa-release-risk-governance # 输入：发布风险评估\n - qa-quality-metrics # 输入：质量度量数据\n downstream: [] # 输出用于沟通\ninput_format:\n required:\n - name: 测试报告\n type: object\n description: 来自qa-test-reporting的测试报告\n - name: 受众分析\n type: string\n description: 报告接收方的角色和信息需求\n optional:\n - name: 沟通渠道\n type: string\n description: 可用的沟通渠道和频率\noutput_format:\n traceability:\n - 每份沟通策略带唯一ID（COMM-XXXX）\n structure:\n - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n - communication_plan: 沟通计划\n - tailored_report: 定制化报告\n - key_metrics: 关键指标呈现\n - risk_highlight: 风险提示\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n reference_value: \"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖开发、PM、领导3类角色的沟通策略\"\nerror_recovery_guidance:\n on_failure: \"沟通策略未能推动问题解决时回退到问题定位补充\"\n retry_behavior: \"补充定位后重新设计沟通策略\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 干系人沟通\n\n## 核心原则\n\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\n\n## 三类沟通模式\n\n### 模式1：跟开发说（技术视角）\n\n```text\n沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]\n```\n\n### 模式2：跟PM说（业务视角）\n\n```text\n沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]\n```\n\n### 模式3：跟老板说（决策视角）\n\n```text\n沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]\n```\n\n## 高危表达对比\n\n| 场景 | 不要说 | 可以说 |\n|------|--------|--------|\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\n\n## 沟通场景模板\n\n### 场景1：Bug评审会\n\n```text\n参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调\n```\n\n### 场景2：发布评审会\n\n```text\n参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案\n```\n\n### 场景3：质量报告\n\n```text\n报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施\n```\n\n## 应用场景\n\n**发现一个支付Bug，需要同步给不同角色**\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\n\n**Bug评审会上开发说\"这个没问题\"**\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\n\n## 自检清单\n\n沟通完成后检查：\n- [ ] 是否针对受众定制了信息？\n- [ ] 是否包含了对方需要的决策信息？\n- [ ] 是否避免了高危表达？\n- [ ] 是否达成了沟通目标？\n\n\n## 检查清单\n\n- [ ] 受众角色是否识别？\n- [ ] 沟通策略是否定制？\n- [ ] 关键信息是否突出？\n- [ ] 推动方案是否可行？\n- [ ] 反馈机制是否建立？\n\nFile v1.7.5:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.7.5\",\n \"publishedAt\": 1788103143470\n}\n\nFile v1.7.5:skill-card.md\n\n## Description:\n\nThis skill helps QA practitioners tailor communication templates and reporting language for developers, product managers, and leaders when discussing bugs, requirement changes, and quality risks.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers and test leads use this skill to prepare audience-specific stakeholder communications, including developer-facing bug details, product-facing impact summaries, and leadership-facing quality risk reports.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Users may include real customer data, payment details, screenshots, identity numbers, or production logs in QA communication examples.\n\nMitigation: Redact sensitive customer, financial, identity, screenshot, and production log data before using the skill.\n\nRisk: Broad activation phrases may apply the skill to general communication requests outside QA stakeholder reporting.\n\nMitigation: Confirm the request is QA-focused and identify the intended audience before relying on the generated templates.\n\n## Reference(s):\n\n- [ClawHub skill page: qa-stakeholder-communication](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Markdown with structured communication templates and role-specific talking points]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include COMM-XXXX traceability identifiers, communication plans, tailored reports, key metrics, and risk highlights.]\n\n## Skill Version(s):\n\n1.7.5 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.7.0: 3 files, 4454 bytes\n\nFiles: skill-card.md (1913b), SKILL.md (6223b), _meta.json (147b)\n\nFile v1.7.0:SKILL.md\n\n---\nname: qa-stakeholder-communication\nslug: qa-stakeholder-communication\ndisplayName: Stakeholder Communication\nversion: 1.7.0\ndescription: >-\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\n\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时\nallowed-tools: Read Grep Glob\nrelated_skills:\n upstream:\n - qa-bug-reporting # 输入：Bug报告\n - qa-release-risk-governance # 输入：发布风险评估\n - qa-quality-metrics # 输入：质量度量数据\n downstream: [] # 输出用于沟通\ninput_format:\n required:\n - name: 测试报告\n type: object\n description: 来自qa-test-reporting的测试报告\n - name: 受众分析\n type: string\n description: 报告接收方的角色和信息需求\n optional:\n - name: 沟通渠道\n type: string\n description: 可用的沟通渠道和频率\noutput_format:\n traceability:\n - 每份沟通策略带唯一ID（COMM-XXXX）\n structure:\n - communication_plan: 沟通计划\n - tailored_report: 定制化报告\n - key_metrics: 关键指标呈现\n - risk_highlight: 风险提示\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n reference_value: \"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖开发、PM、领导3类角色的沟通策略\"\nerror_recovery_guidance:\n on_failure: \"沟通策略未能推动问题解决时回退到问题定位补充\"\n retry_behavior: \"补充定位后重新设计沟通策略\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 干系人沟通\n\n## 核心原则\n\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\n\n## 三类沟通模式\n\n### 模式1：跟开发说（技术视角）\n\n```text\n沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]\n```\n\n### 模式2：跟PM说（业务视角）\n\n```text\n沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]\n```\n\n### 模式3：跟老板说（决策视角）\n\n```text\n沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]\n```\n\n## 高危表达对比\n\n| 场景 | 不要说 | 可以说 |\n|------|--------|--------|\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\n\n## 沟通场景模板\n\n### 场景1：Bug评审会\n\n```text\n参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调\n```\n\n### 场景2：发布评审会\n\n```text\n参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案\n```\n\n### 场景3：质量报告\n\n```text\n报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施\n```\n\n## 应用场景\n\n**发现一个支付Bug，需要同步给不同角色**\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\n\n**Bug评审会上开发说\"这个没问题\"**\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\n\n## 自检清单\n\n沟通完成后检查：\n- [ ] 是否针对受众定制了信息？\n- [ ] 是否包含了对方需要的决策信息？\n- [ ] 是否避免了高危表达？\n- [ ] 是否达成了沟通目标？\n\n\n## 检查清单\n\n- [ ] 受众角色是否识别？\n- [ ] 沟通策略是否定制？\n- [ ] 关键信息是否突出？\n- [ ] 推动方案是否可行？\n- [ ] 反馈机制是否建立？\n\nFile v1.7.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.7.0\",\n \"publishedAt\": 1786890766867\n}\n\nFile v1.7.0:skill-card.md\n\n## Description:\n\nHelps QA practitioners tailor bug, release-risk, and quality updates for developers, product managers, and leadership.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers and test leads use this skill to turn testing findings, bug reports, and quality risks into audience-specific communication for developers, product managers, and management stakeholders.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Communication examples and QA reports may contain customer, payment, identity, incident, or production data.\n\nMitigation: Mask or remove sensitive data before using the skill, especially in bug reports, screenshots, logs, payment examples, and quality reports.\n\nRisk: Broad communication prompts may activate the skill outside a QA stakeholder communication workflow.\n\nMitigation: Use the skill for QA and testing communication tasks, and confirm the audience and decision context before relying on its templates.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n- [Publisher profile](https://clawhub.ai/user/kokxi)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown-style communication plans, tailored reports, metric summaries, and risk highlights]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include traceable communication IDs such as COMM-XXXX.]\n\n## Skill Version(s):\n\n1.7.0 (source: server release metadata and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.6.3: 3 files, 4483 bytes\n\nFiles: skill-card.md (1932b), SKILL.md (6223b), _meta.json (147b)\n\nFile v1.6.3:SKILL.md\n\n---\nname: qa-stakeholder-communication\nslug: qa-stakeholder-communication\ndisplayName: Stakeholder Communication\nversion: 1.6.3\ndescription: >-\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\n\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时\nallowed-tools: Read Grep Glob\nrelated_skills:\n upstream:\n - qa-bug-reporting # 输入：Bug报告\n - qa-release-risk-governance # 输入：发布风险评估\n - qa-quality-metrics # 输入：质量度量数据\n downstream: [] # 输出用于沟通\ninput_format:\n required:\n - name: 测试报告\n type: object\n description: 来自qa-test-reporting的测试报告\n - name: 受众分析\n type: string\n description: 报告接收方的角色和信息需求\n optional:\n - name: 沟通渠道\n type: string\n description: 可用的沟通渠道和频率\noutput_format:\n traceability:\n - 每份沟通策略带唯一ID（COMM-XXXX）\n structure:\n - communication_plan: 沟通计划\n - tailored_report: 定制化报告\n - key_metrics: 关键指标呈现\n - risk_highlight: 风险提示\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n reference_value: \"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖开发、PM、领导3类角色的沟通策略\"\nerror_recovery_guidance:\n on_failure: \"沟通策略未能推动问题解决时回退到问题定位补充\"\n retry_behavior: \"补充定位后重新设计沟通策略\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 干系人沟通\n\n## 核心原则\n\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\n\n## 三类沟通模式\n\n### 模式1：跟开发说（技术视角）\n\n```text\n沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]\n```\n\n### 模式2：跟PM说（业务视角）\n\n```text\n沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]\n```\n\n### 模式3：跟老板说（决策视角）\n\n```text\n沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]\n```\n\n## 高危表达对比\n\n| 场景 | 不要说 | 可以说 |\n|------|--------|--------|\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\n\n## 沟通场景模板\n\n### 场景1：Bug评审会\n\n```text\n参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调\n```\n\n### 场景2：发布评审会\n\n```text\n参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案\n```\n\n### 场景3：质量报告\n\n```text\n报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施\n```\n\n## 应用场景\n\n**发现一个支付Bug，需要同步给不同角色**\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\n\n**Bug评审会上开发说\"这个没问题\"**\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\n\n## 自检清单\n\n沟通完成后检查：\n- [ ] 是否针对受众定制了信息？\n- [ ] 是否包含了对方需要的决策信息？\n- [ ] 是否避免了高危表达？\n- [ ] 是否达成了沟通目标？\n\n\n## 检查清单\n\n- [ ] 受众角色是否识别？\n- [ ] 沟通策略是否定制？\n- [ ] 关键信息是否突出？\n- [ ] 推动方案是否可行？\n- [ ] 反馈机制是否建立？\n\nFile v1.6.3:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.6.3\",\n \"publishedAt\": 1786548479667\n}\n\nFile v1.6.3:skill-card.md\n\n## Description:\n\nProvides QA teams with stakeholder-specific communication strategies and report templates for developers, product managers, and leadership when discussing bug fixes, requirement changes, and quality risks.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA practitioners and test leads use this skill to tailor bug, release risk, and quality-status messages for developers, product managers, and leadership so each audience receives the details needed for action or decision-making.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Stakeholder communication may include customer, payment, identity, incident, or production details.\n\nMitigation: Redact or mask sensitive data before using the skill, as recommended by the security guidance.\n\nRisk: Audience-specific summaries can overstate quality risks or omit technical context if source QA evidence is incomplete.\n\nMitigation: Review generated communication plans and reports against the underlying test report, bug evidence, and release-risk data before sending them to stakeholders.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Markdown with structured communication templates]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include communication plan IDs with COMM-XXXX traceability.]\n\n## Skill Version(s):\n\n1.6.3 (source: SKILL.md frontmatter and server release metadata)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.6.0: 3 files, 4581 bytes\n\nFiles: skill-card.md (2298b), SKILL.md (6333b), _meta.json (147b)\n\nFile v1.6.0:SKILL.md\n\n---\r\nname: qa-stakeholder-communication\r\nversion: 1.6.0\r\ndescription: >-\r\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\r\n\r\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、\"干系人沟通\"、需要与不同角色沟通、推动问题解决需要有效沟通时\r\nallowed-tools: Read Grep Glob\r\nrelated_skills:\r\n upstream:\r\n - qa-bug-reporting # 输入：Bug报告\r\n - qa-release-risk-governance # 输入：发布风险评估\r\n - qa-quality-metrics # 输入：质量度量数据\r\n downstream: [] # 输出用于沟通\r\ninput_format:\r\n required:\r\n - name: 测试报告\r\n type: object\r\n description: 来自qa-test-reporting的测试报告\r\n - name: 受众分析\r\n type: string\r\n description: 报告接收方的角色和信息需求\r\n optional:\r\n - name: 沟通渠道\r\n type: string\r\n description: 可用的沟通渠道和频率\r\noutput_format:\r\n traceability:\r\n - 每份沟通策略带唯一ID（COMM-XXXX）\r\n structure:\r\n - communication_plan: 沟通计划\r\n - tailored_report: 定制化报告\r\n - key_metrics: 关键指标呈现\r\n - risk_highlight: 风险提示\r\ncategories: ['Development','Team']\r\ndepth_requirement_quantification:\r\n reference_value: \"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\"\r\n minimum: \"至少覆盖开发、PM、领导3类角色的沟通策略\"\r\nerror_recovery_guidance:\r\n on_failure: \"沟通策略未能推动问题解决时回退到问题定位补充\"\r\n retry_behavior: \"补充定位后重新设计沟通策略\"\r\n---\r\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\r\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 干系人沟通\r\n\r\n## 核心原则\r\n\r\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\r\n\r\n## 三类沟通模式\r\n\r\n### 模式1：跟开发说（技术视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 精确的复现步骤：每一步操作\r\n├─ 日志/截图：错误信息、异常堆栈\r\n├─ 根因推测：可能的原因\r\n├─ 环境信息：浏览器、系统、配置\r\n└─ 影响范围：哪些功能受影响\r\n\r\n沟通格式：\r\n[Bug标题] [严重程度]\r\n复现步骤：\r\n1. ...\r\n2. ...\r\n3. ...\r\n错误日志：[日志内容]\r\n截图：[截图描述]\r\n推测原因：[原因分析]\r\n影响范围：[影响描述]\r\n```\r\n\r\n### 模式2：跟PM说（业务视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 用户影响：哪些用户受影响\r\n├─ 严重程度：业务影响多大\r\n├─ 修复优先级：建议优先级\r\n├─ 对其他功能的阻塞\r\n└─ 预计修复时间\r\n\r\n沟通格式：\r\n[Bug标题]\r\n影响：[用户范围]\r\n严重程度：[业务影响]\r\n优先级：[P0-P3]\r\n阻塞：[是否阻塞其他功能]\r\n预计修复：[时间估算]\r\n```\r\n\r\n### 模式3：跟老板说（决策视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 业务影响：对业务的影响\r\n├─ 发布风险：是否影响发布\r\n├─ 建议决策：建议怎么做\r\n├─ 要什么资源：需要什么支持\r\n└─ 时间节点：什么时候能解决\r\n\r\n沟通格式：\r\n[问题描述]\r\n业务影响：[影响描述]\r\n发布风险：[风险评估]\r\n建议决策：[建议方案]\r\n资源需求：[需要什么]\r\n时间节点：[时间计划]\r\n```\r\n\r\n## 高危表达对比\r\n\r\n| 场景 | 不要说 | 可以说 |\r\n|------|--------|--------|\r\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\r\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\r\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\r\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\r\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\r\n\r\n## 沟通场景模板\r\n\r\n### 场景1：Bug评审会\r\n\r\n```text\r\n参会角色：开发、测试、PM\r\n沟通内容：\r\n├─ 测试：Bug描述、复现步骤、影响范围\r\n├─ 开发：根因分析、修复方案、修复时间\r\n└─ PM：优先级评估、资源协调\r\n```\r\n\r\n### 场景2：发布评审会\r\n\r\n```text\r\n参会角色：开发、测试、PM、运维\r\n沟通内容：\r\n├─ 测试：测试结果、质量评估、风险提示\r\n├─ 开发：变更内容、技术风险\r\n├─ PM：业务影响、发布决策\r\n└─ 运维：部署方案、回滚方案\r\n```\r\n\r\n### 场景3：质量报告\r\n\r\n```text\r\n报告对象：老板、PM\r\n报告内容：\r\n├─ 质量指标：缺陷密度、漏测率\r\n├─ 质量趋势：改善/稳定/恶化\r\n├─ 风险提示：高风险区域\r\n└─ 改进建议：建议措施\r\n```\r\n\r\n## 应用场景\r\n\r\n**发现一个支付Bug，需要同步给不同角色**\r\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\r\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\r\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\r\n\r\n**Bug评审会上开发说\"这个没问题\"**\r\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\r\n\r\n## 自检清单\r\n\r\n沟通完成后检查：\r\n- [ ] 是否针对受众定制了信息？\r\n- [ ] 是否包含了对方需要的决策信息？\r\n- [ ] 是否避免了高危表达？\r\n- [ ] 是否达成了沟通目标？\r\n\r\n\r\n## 检查清单\r\n\r\n- [ ] 受众角色是否识别？\r\n- [ ] 沟通策略是否定制？\r\n- [ ] 关键信息是否突出？\r\n- [ ] 推动方案是否可行？\r\n- [ ] 反馈机制是否建立？\n\nFile v1.6.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.6.0\",\n \"publishedAt\": 1783358259881\n}\n\nFile v1.6.0:skill-card.md\n\n## Description:
\nThis skill helps QA teams tailor bug-fix, requirement-change, and quality-risk communication for developers, product managers, and leadership.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA practitioners and team stakeholders use this skill to convert QA findings into audience-specific communication plans, tailored reports, metric summaries, and risk highlights. It supports bug triage, requirement-change discussions, release reviews, and quality reporting across development, product, and management audiences.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Users may paste real customer, payment, identity, order, or production incident data into QA communication examples.
\nMitigation: Redact or mask sensitive data before using the skill, and avoid including production credentials, customer identifiers, or financial records.
\nRisk: Broad Chinese trigger phrases may make the skill appear for non-QA communication requests.
\nMitigation: Confirm that the request is about QA stakeholder communication and identify the intended audience before applying the templates.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)
\n- [Publisher profile](https://clawhub.ai/user/kokxi)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance]
\n**Output Format:** [Markdown communication plans, tailored reports, key metric summaries, and risk highlights with COMM-XXXX traceability IDs]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [No code or shell commands; outputs should avoid real customer, payment, identity, order, or production incident data unless redacted.]
\n\n## Skill Version(s):
\n1.6.0 (source: SKILL.md frontmatter and server release evidence)
\n\n## Ethical Considerations:
\nUsers 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.
\n\nArchive v1.5.0: 3 files, 3988 bytes\n\nFiles: skill-card.md (2139b), SKILL.md (5462b), _meta.json (147b)\n\nFile v1.5.0:SKILL.md\n\n---\r\nname: qa-stakeholder-communication\r\nversion: 1.5.0\r\ndescription: >-\r\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。\r\n\r\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、需要与不同角色沟通、推动问题解决需要有效沟通时\r\nallowed-tools: Read Grep Glob\r\nrelated_skills:\r\n upstream:\r\n - qa-bug-reporting # 输入：Bug报告\r\n - qa-release-risk-governance # 输入：发布风险评估\r\n - qa-quality-metrics # 输入：质量度量数据\r\n downstream: [] # 输出用于沟通\r\ninput_format:\r\n required:\r\n - name: 测试报告\r\n type: object\r\n description: 来自qa-test-reporting的测试报告\r\n - name: 受众分析\r\n type: string\r\n description: 报告接收方的角色和信息需求\r\n optional:\r\n - name: 沟通渠道\r\n type: string\r\n description: 可用的沟通渠道和频率\r\noutput_format:\r\n structure:\r\n - communication_plan: 沟通计划\r\n - tailored_report: 定制化报告\r\n - key_metrics: 关键指标呈现\r\n - risk_highlight: 风险提示\r\n---\r\n\r\n# 干系人沟通\r\n\r\n## 核心原则\r\n\r\n你是一位沟通专家，擅长针对不同角色定制沟通内容。\r\n**核心原则**：同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\r\n本技能覆盖开发/PM/老板三类沟通模式及常见沟通场景。\r\n\r\n## 三类沟通模式\r\n\r\n### 模式1：跟开发说（技术视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 精确的复现步骤：每一步操作\r\n├─ 日志/截图：错误信息、异常堆栈\r\n├─ 根因推测：可能的原因\r\n├─ 环境信息：浏览器、系统、配置\r\n└─ 影响范围：哪些功能受影响\r\n\r\n沟通格式：\r\n[Bug标题] [严重程度]\r\n复现步骤：\r\n1. ...\r\n2. ...\r\n3. ...\r\n错误日志：[日志内容]\r\n截图：[截图描述]\r\n推测原因：[原因分析]\r\n影响范围：[影响描述]\r\n```\r\n\r\n### 模式2：跟PM说（业务视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 用户影响：哪些用户受影响\r\n├─ 严重程度：业务影响多大\r\n├─ 修复优先级：建议优先级\r\n├─ 对其他功能的阻塞\r\n└─ 预计修复时间\r\n\r\n沟通格式：\r\n[Bug标题]\r\n影响：[用户范围]\r\n严重程度：[业务影响]\r\n优先级：[P0-P3]\r\n阻塞：[是否阻塞其他功能]\r\n预计修复：[时间估算]\r\n```\r\n\r\n### 模式3：跟老板说（决策视角）\r\n\r\n```text\r\n沟通重点：\r\n├─ 业务影响：对业务的影响\r\n├─ 发布风险：是否影响发布\r\n├─ 建议决策：建议怎么做\r\n├─ 要什么资源：需要什么支持\r\n└─ 时间节点：什么时候能解决\r\n\r\n沟通格式：\r\n[问题描述]\r\n业务影响：[影响描述]\r\n发布风险：[风险评估]\r\n建议决策：[建议方案]\r\n资源需求：[需要什么]\r\n时间节点：[时间计划]\r\n```\r\n\r\n## 高危表达对比\r\n\r\n| 场景 | 不要说 | 可以说 |\r\n|------|--------|--------|\r\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\r\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\r\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\r\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\r\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\r\n\r\n## 沟通场景模板\r\n\r\n### 场景1：Bug评审会\r\n\r\n```text\r\n参会角色：开发、测试、PM\r\n沟通内容：\r\n├─ 测试：Bug描述、复现步骤、影响范围\r\n├─ 开发：根因分析、修复方案、修复时间\r\n└─ PM：优先级评估、资源协调\r\n```\r\n\r\n### 场景2：发布评审会\r\n\r\n```text\r\n参会角色：开发、测试、PM、运维\r\n沟通内容：\r\n├─ 测试：测试结果、质量评估、风险提示\r\n├─ 开发：变更内容、技术风险\r\n├─ PM：业务影响、发布决策\r\n└─ 运维：部署方案、回滚方案\r\n```\r\n\r\n### 场景3：质量报告\r\n\r\n```text\r\n报告对象：老板、PM\r\n报告内容：\r\n├─ 质量指标：缺陷密度、漏测率\r\n├─ 质量趋势：改善/稳定/恶化\r\n├─ 风险提示：高风险区域\r\n└─ 改进建议：建议措施\r\n```\r\n\r\n## 应用场景\r\n\r\n**发现一个支付Bug，需要同步给不同角色**\r\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\r\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\r\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\r\n\r\n**Bug评审会上开发说\"这个没问题\"**\r\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\r\n\r\n## 自检清单\r\n\r\n沟通完成后检查：\r\n- [ ] 是否针对受众定制了信息？\r\n- [ ] 是否包含了对方需要的决策信息？\r\n- [ ] 是否避免了高危表达？\r\n- [ ] 是否达成了沟通目标？\n\nFile v1.5.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.5.0\",\n \"publishedAt\": 1782737017696\n}\n\nFile v1.5.0:skill-card.md\n\n## Description:
\nProvides Chinese-language templates and communication strategies for QA stakeholders to report bugs, release risks, and quality concerns to developers, product managers, and leadership.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA testers and quality engineers use this skill to tailor bug reports, release-risk updates, and quality summaries for developers, product managers, and managers. It helps convert test findings into role-specific communication plans, reports, key metrics, and risk highlights.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate on broad communication prompts outside a clear QA or stakeholder-reporting context.
\nMitigation: Use it when the request is clearly about QA bugs, release risks, quality issues, or stakeholder reporting.
\nRisk: Generated stakeholder wording may overstate impact or urgency if the underlying test report or audience analysis is incomplete.
\nMitigation: Review the communication plan and report against the source QA evidence before sending it to developers, product managers, or leadership.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Guidance]
\n**Output Format:** [Markdown with structured communication plans, tailored reports, key metrics, and risk highlights]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Chinese-language, audience-specific QA stakeholder communication guidance]
\n\n## Skill Version(s):
\n1.5.0 (source: frontmatter and server release evidence)
\n\n## Ethical Considerations:
\nUsers 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.
\n\nArchive v1.4.1: 3 files, 3695 bytes\n\nFiles: skill-card.md (1910b), SKILL.md (4706b), _meta.json (147b)\n\nFile v1.4.1:SKILL.md\n\n---\r\nname: qa-stakeholder-communication\r\ndescription: >-\r\n 干系人沟通，针对开发/产品/管理层不同角色定制测试沟通内容和汇报方式。当需要与不同角色沟通测试进展或推动问题时激活。\r\n\r\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、需要与不同角色沟通、推动问题解决需要有效沟通时\r\nallowed-tools: Read Grep Glob\r\nrelated_skills:\r\n upstream:\r\n - qa-bug-reporting # 输入：Bug报告\r\n - qa-release-risk-governance # 输入：发布风险评估\r\n - qa-quality-metrics # 输入：质量度量数据\r\n downstream: 无（输出用于沟通）\r\ninput_format: Bug报告/发布评估/质量数据\r\noutput_format: 定制化沟通内容（开发版/PM版/老板版）\r\n---\r\n\r\n# 干系人沟通\r\n\r\n## Overview\r\n\r\n你是一位沟通专家，擅长针对不同角色定制沟通内容。\r\n**核心原则**：同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\r\n本技能覆盖开发/PM/老板三类沟通模式及常见沟通场景。\r\n\r\n## 三类沟通模式\r\n\r\n### 模式1：跟开发说（技术视角）\r\n\r\n```\r\n沟通重点：\r\n├─ 精确的复现步骤：每一步操作\r\n├─ 日志/截图：错误信息、异常堆栈\r\n├─ 根因推测：可能的原因\r\n├─ 环境信息：浏览器、系统、配置\r\n└─ 影响范围：哪些功能受影响\r\n\r\n沟通格式：\r\n[Bug标题] [严重程度]\r\n复现步骤：\r\n1. ...\r\n2. ...\r\n3. ...\r\n错误日志：[日志内容]\r\n截图：[截图描述]\r\n推测原因：[原因分析]\r\n影响范围：[影响描述]\r\n```\r\n\r\n### 模式2：跟PM说（业务视角）\r\n\r\n```\r\n沟通重点：\r\n├─ 用户影响：哪些用户受影响\r\n├─ 严重程度：业务影响多大\r\n├─ 修复优先级：建议优先级\r\n├─ 对其他功能的阻塞\r\n└─ 预计修复时间\r\n\r\n沟通格式：\r\n[Bug标题]\r\n影响：[用户范围]\r\n严重程度：[业务影响]\r\n优先级：[P0-P3]\r\n阻塞：[是否阻塞其他功能]\r\n预计修复：[时间估算]\r\n```\r\n\r\n### 模式3：跟老板说（决策视角）\r\n\r\n```\r\n沟通重点：\r\n├─ 业务影响：对业务的影响\r\n├─ 发布风险：是否影响发布\r\n├─ 建议决策：建议怎么做\r\n├─ 要什么资源：需要什么支持\r\n└─ 时间节点：什么时候能解决\r\n\r\n沟通格式：\r\n[问题描述]\r\n业务影响：[影响描述]\r\n发布风险：[风险评估]\r\n建议决策：[建议方案]\r\n资源需求：[需要什么]\r\n时间节点：[时间计划]\r\n```\r\n\r\n## 高危表达对比\r\n\r\n| 场景 | 不要说 | 可以说 |\r\n|------|--------|--------|\r\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\r\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\r\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\r\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\r\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\r\n\r\n## 沟通场景模板\r\n\r\n### 场景1：Bug评审会\r\n\r\n```\r\n参会角色：开发、测试、PM\r\n沟通内容：\r\n├─ 测试：Bug描述、复现步骤、影响范围\r\n├─ 开发：根因分析、修复方案、修复时间\r\n└─ PM：优先级评估、资源协调\r\n```\r\n\r\n### 场景2：发布评审会\r\n\r\n```\r\n参会角色：开发、测试、PM、运维\r\n沟通内容：\r\n├─ 测试：测试结果、质量评估、风险提示\r\n├─ 开发：变更内容、技术风险\r\n├─ PM：业务影响、发布决策\r\n└─ 运维：部署方案、回滚方案\r\n```\r\n\r\n### 场景3：质量报告\r\n\r\n```\r\n报告对象：老板、PM\r\n报告内容：\r\n├─ 质量指标：缺陷密度、漏测率\r\n├─ 质量趋势：改善/稳定/恶化\r\n├─ 风险提示：高风险区域\r\n└─ 改进建议：建议措施\r\n```\r\n\r\n## Examples\r\n\r\n**发现一个支付Bug，需要同步给不同角色**\r\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\r\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\r\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\r\n\r\n**Bug评审会上开发说\"这个没问题\"**\r\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\r\n\r\n## Guidelines\r\n\r\n沟通完成后检查：\r\n- [ ] 是否针对受众定制了信息？\r\n- [ ] 是否包含了对方需要的决策信息？\r\n- [ ] 是否避免了高危表达？\r\n- [ ] 是否达成了沟通目标？\n\nFile v1.4.1:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.4.1\",\n \"publishedAt\": 1782406601959\n}\n\nFile v1.4.1:skill-card.md\n\n## Description:
\n干系人沟通，针对开发/产品/管理层不同角色定制测试沟通内容和汇报方式。当需要与不同角色沟通测试进展或推动问题时激活。
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA practitioners use this skill to tailor stakeholder communication for developers, product managers, and management. It helps transform bug reports, release assessments, and quality metrics into audience-specific communication content.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate on fairly general communication requests.
\nMitigation: Confirm the request is about QA stakeholder communication before applying its templates.
\nRisk: The skill allows read-only file access for context gathering.
\nMitigation: Limit file reads to relevant bug reports, release assessments, and quality metrics intended for the communication task.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Guidance]
\n**Output Format:** [Markdown communication templates and role-specific stakeholder messages]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May use relevant bug reports, release risk assessments, or quality metrics as input.]
\n\n## Skill Version(s):
\n1.4.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers 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.
\n\nArchive v1.4.0: 3 files, 3814 bytes\n\nFiles: skill-card.md (2179b), SKILL.md (4973b), _meta.json (147b)\n\nFile v1.4.0:SKILL.md\n\n---\r\nname: qa-stakeholder-communication\r\ndescription: >-\r\n 干系人沟通，针对开发、产品、管理层等不同角色定制沟通内容和方式。当用户不知道如何沟通、需要跟开发说或跟产品经理说时自动触发。\r\n 也适用于：测试报告需要面向不同受众，或推动问题解决需要有效沟通时。\r\n 关键词：干系人沟通、角色定制、测试汇报、有效沟通、沟通策略、向上汇报、跨部门沟通、冲突解决、信息同步。\nwhen_to_use: 用户说\"怎么沟通\"、\"跟开发说\"、\"跟PM说\"、\"跟领导说\"、\"沟通策略\"、\"向上汇报\"、需要与不同角色沟通、推动问题解决需要有效沟通时\r\nallowed-tools: Read Grep Glob\r\nrelated_skills:\r\n upstream:\r\n - qa-bug-reporting # 输入：Bug报告\r\n - qa-release-risk-governance # 输入：发布风险评估\r\n - qa-quality-metrics # 输入：质量度量数据\r\n downstream: 无（输出用于沟通）\r\ninput_format: Bug报告/发布评估/质量数据\r\noutput_format: 定制化沟通内容（开发版/PM版/老板版）\r\n---\r\n\r\n# 干系人沟通\r\n\r\n## Overview\r\n\r\n你是一位沟通专家，擅长针对不同角色定制沟通内容。\r\n**核心原则**：同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\r\n本技能覆盖开发/PM/老板三类沟通模式及常见沟通场景。\r\n\r\n## 三类沟通模式\r\n\r\n### 模式1：跟开发说（技术视角）\r\n\r\n```\r\n沟通重点：\r\n├─ 精确的复现步骤：每一步操作\r\n├─ 日志/截图：错误信息、异常堆栈\r\n├─ 根因推测：可能的原因\r\n├─ 环境信息：浏览器、系统、配置\r\n└─ 影响范围：哪些功能受影响\r\n\r\n沟通格式：\r\n[Bug标题] [严重程度]\r\n复现步骤：\r\n1. ...\r\n2. ...\r\n3. ...\r\n错误日志：[日志内容]\r\n截图：[截图描述]\r\n推测原因：[原因分析]\r\n影响范围：[影响描述]\r\n```\r\n\r\n### 模式2：跟PM说（业务视角）\r\n\r\n```\r\n沟通重点：\r\n├─ 用户影响：哪些用户受影响\r\n├─ 严重程度：业务影响多大\r\n├─ 修复优先级：建议优先级\r\n├─ 对其他功能的阻塞\r\n└─ 预计修复时间\r\n\r\n沟通格式：\r\n[Bug标题]\r\n影响：[用户范围]\r\n严重程度：[业务影响]\r\n优先级：[P0-P3]\r\n阻塞：[是否阻塞其他功能]\r\n预计修复：[时间估算]\r\n```\r\n\r\n### 模式3：跟老板说（决策视角）\r\n\r\n```\r\n沟通重点：\r\n├─ 业务影响：对业务的影响\r\n├─ 发布风险：是否影响发布\r\n├─ 建议决策：建议怎么做\r\n├─ 要什么资源：需要什么支持\r\n└─ 时间节点：什么时候能解决\r\n\r\n沟通格式：\r\n[问题描述]\r\n业务影响：[影响描述]\r\n发布风险：[风险评估]\r\n建议决策：[建议方案]\r\n资源需求：[需要什么]\r\n时间节点：[时间计划]\r\n```\r\n\r\n## 高危表达对比\r\n\r\n| 场景 | 不要说 | 可以说 |\r\n|------|--------|--------|\r\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\r\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\r\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\r\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\r\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\r\n\r\n## 沟通场景模板\r\n\r\n### 场景1：Bug评审会\r\n\r\n```\r\n参会角色：开发、测试、PM\r\n沟通内容：\r\n├─ 测试：Bug描述、复现步骤、影响范围\r\n├─ 开发：根因分析、修复方案、修复时间\r\n└─ PM：优先级评估、资源协调\r\n```\r\n\r\n### 场景2：发布评审会\r\n\r\n```\r\n参会角色：开发、测试、PM、运维\r\n沟通内容：\r\n├─ 测试：测试结果、质量评估、风险提示\r\n├─ 开发：变更内容、技术风险\r\n├─ PM：业务影响、发布决策\r\n└─ 运维：部署方案、回滚方案\r\n```\r\n\r\n### 场景3：质量报告\r\n\r\n```\r\n报告对象：老板、PM\r\n报告内容：\r\n├─ 质量指标：缺陷密度、漏测率\r\n├─ 质量趋势：改善/稳定/恶化\r\n├─ 风险提示：高风险区域\r\n└─ 改进建议：建议措施\r\n```\r\n\r\n## Examples\r\n\r\n**发现一个支付Bug，需要同步给不同角色**\r\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\r\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\r\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\r\n\r\n**Bug评审会上开发说\"这个没问题\"**\r\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\r\n\r\n## Guidelines\r\n\r\n沟通完成后检查：\r\n- [ ] 是否针对受众定制了信息？\r\n- [ ] 是否包含了对方需要的决策信息？\r\n- [ ] 是否避免了高危表达？\r\n- [ ] 是否达成了沟通目标？\n\nFile v1.4.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.4.0\",\n \"publishedAt\": 1782277944375\n}\n\nFile v1.4.0:skill-card.md\n\n## Description:
\nHelps QA practitioners tailor stakeholder communication for developers, product managers, and leadership when sharing bug reports, release risk, quality metrics, or issue-resolution updates.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA engineers and test leads use this skill to convert bug reports, release assessments, and quality data into audience-specific messages for developers, PMs, and leadership. It supports technical detail sharing, business-impact framing, upward reporting, and conflict-sensitive issue escalation.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill has broad communication triggers and may be applied outside QA stakeholder communication contexts.
\nMitigation: Confirm the request is about QA findings, stakeholder updates, release risk, or issue-resolution communication before using its guidance.
\nRisk: Drafts may include confidential logs, screenshots, or business details supplied by the user.
\nMitigation: Avoid pasting sensitive operational details unless they are intended to be used in the generated communication.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)
\n- [Publisher profile](https://clawhub.ai/user/kokxi)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Guidance]
\n**Output Format:** [Markdown or structured text templates for stakeholder-specific QA communication]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Outputs may include developer-, PM-, and leadership-focused versions of the same QA finding.]
\n\n## Skill Version(s):
\n1.4.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers 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.
","readmeExcerpt":"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","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调"},{"language":"text","snippet":"参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案"},{"language":"text","snippet":"报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施"},{"language":"text","snippet":"沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]"},{"language":"text","snippet":"沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]"},{"language":"text","snippet":"沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: qa-stakeholder-communication\ndescription: >-\n 当需要告诉开发\"这个 Bug 必须修\"、跟产品经理沟通需求变更的影响、或者向管理层汇报质量风险时使用此技能。不同角色关注的事情不同——开发要的是复现步骤和定位信息，产品要的是影响范围和优先级建议，管理层要的是风险判断和决策依据。此技能提供针对开发/产品/管理层的沟通模板和策略。产出根据不同角色定制的沟通话术和汇报材料模板。 触发场景：怎么沟通、跟开发说、跟PM说、跟领导说、沟通策略、向上汇报、干系人沟通、推动问题解决需要有效沟通时。 Use when the user asks about: communicating test findings to engineers, product managers, and management using role-tailored templates and escalation strategy.\nlicense: MIT\nallowed-tools: Read Grep Glob\nmetadata:\n display-name: \"Stakeholder Communication\"\n version: \"1.8.0\"\n when-to-use: \"用户说\\\"怎么沟通\\\"、\\\"跟开发说\\\"、\\\"跟PM说\\\"、\\\"跟领导说\\\"、\\\"沟通策略\\\"、\\\"向上汇报\\\"、\\\"干系人沟通\\\"、需要与不同角色沟通、推动问题解决需要有效沟通时\"\n related-skills: \"{\\\"upstream\\\":[\\\"qa-bug-reporting\\\",\\\"qa-release-risk-governance\\\",\\\"qa-quality-metrics\\\"],\\\"downstream\\\":[]}\"\n references: \"[\\\"references/comms-patterns.md\\\"]\"\n input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"测试报告\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-reporting的测试报告\\\"},{\\\"name\\\":\\\"受众分析\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"报告接收方的角色和信息需求\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"沟通渠道\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"可用的沟通渠道和频率\\\"}]}\"\n output-format: \"{\\\"traceability\\\":[\\\"每份沟通策略带唯一ID（COMM-XXXX）\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"communication_plan\\\":\\\"沟通计划\\\"},{\\\"tailored_report\\\":\\\"定制化报告\\\"},{\\\"key_metrics\\\":\\\"关键指标呈现\\\"},{\\\"risk_highlight\\\":\\\"风险提示\\\"}]}\"\n error-recovery-guidance: \"{\\\"on_failure\\\":\\\"沟通策略未能推动问题解决时回退到问题定位补充\\\",\\\"retry_behavior\\\":\\\"补充定位后重新设计沟通策略\\\"}\"\n categories: \"[\\\"Development\\\",\\\"Team\\\"]\"\n depth-requirement: \"{\\\"reference_value\\\":\\\"根据沟通场景调整策略深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少覆盖开发、PM、领导3类角色的沟通策略\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 干系人沟通\n\n## 核心原则\n\n同样一个Bug，跟不同人说完全不同的表述方式——说对方关心的，而不是你关心的。\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 按受众选沟通话术时 | [`references/comms-patterns.md`](references/comms-patterns.md) |\n\n> `三类沟通模式`的完整内容已下沉至 `references/comms-patterns.md`，避免每次触发都占用上下文。\n\n## 高危表达对比\n\n| 场景 | 不要说 | 可以说 |\n|------|--------|--------|\n| Bug修复延迟 | \"开发没时间\" | \"这个Bug涉及核心逻辑，需要更多时间确保质量\" |\n| 测试延期 | \"测试做不完\" | \"为了保证质量，建议延长2天测试时间\" |\n| 质量问题 | \"质量很差\" \"这个功能有风险\" | \"这个功能需要更多测试时间\" |\n| 资源不足 | \"人不够\" | \"为了按时交付，建议增加1名测试人员\" |\n| 需求变更 | \"需求又变了\" | \"这个变更会影响测试范围，建议重新评估时间\" |\n\n## 沟通场景模板\n\n### 场景1：Bug评审会\n\n```text\n参会角色：开发、测试、PM\n沟通内容：\n├─ 测试：Bug描述、复现步骤、影响范围\n├─ 开发：根因分析、修复方案、修复时间\n└─ PM：优先级评估、资源协调\n```\n\n### 场景2：发布评审会\n\n```text\n参会角色：开发、测试、PM、运维\n沟通内容：\n├─ 测试：测试结果、质量评估、风险提示\n├─ 开发：变更内容、技术风险\n├─ PM：业务影响、发布决策\n└─ 运维：部署方案、回滚方案\n```\n\n### 场景3：质量报告\n\n```text\n报告对象：老板、PM\n报告内容：\n├─ 质量指标：缺陷密度、漏测率\n├─ 质量趋势：改善/稳定/恶化\n├─ 风险提示：高风险区域\n└─ 改进建议：建议措施\n```\n\n## 应用场景\n\n**发现一个支付Bug，需要同步给不同角色**\n→ 跟开发说：技术细节+复现步骤+日志截图（定位问题）\n→ 跟PM说：影响用户数+严重程度+修复时间（评估影响）\n→ 跟老板说：一句话结论+业务影响+风险等级（决策依据）\n\n**Bug评审会上开发说\"这个没问题\"**\n→ 沟通场景应对：用数据和截图说话，避免\"我觉得\"，使用\"数据显示\"\n\n## 自检清单\n\n沟通完成后检查：\n- [ ] 是否针对受众定制了信息？\n- [ ] 是否包含了对方需要的决策信息？\n- [ "},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-stakeholder-communication\",\n \"version\": \"1.8.0\",\n \"publishedAt\": 1790656112831\n}"},{"path":"references/comms-patterns.md","content":"# 三类沟通模式详解\n\n> 本文是 `qa-stakeholder-communication` 的**三类沟通模式详解**。按受众选沟通话术时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 模式1：跟开发说（技术视角）\n\n```text\n沟通重点：\n├─ 精确的复现步骤：每一步操作\n├─ 日志/截图：错误信息、异常堆栈\n├─ 根因推测：可能的原因\n├─ 环境信息：浏览器、系统、配置\n└─ 影响范围：哪些功能受影响\n\n沟通格式：\n[Bug标题] [严重程度]\n复现步骤：\n1. ...\n2. ...\n3. ...\n错误日志：[日志内容]\n截图：[截图描述]\n推测原因：[原因分析]\n影响范围：[影响描述]\n```\n\n### 模式2：跟PM说（业务视角）\n\n```text\n沟通重点：\n├─ 用户影响：哪些用户受影响\n├─ 严重程度：业务影响多大\n├─ 修复优先级：建议优先级\n├─ 对其他功能的阻塞\n└─ 预计修复时间\n\n沟通格式：\n[Bug标题]\n影响：[用户范围]\n严重程度：[业务影响]\n优先级：[P0-P3]\n阻塞：[是否阻塞其他功能]\n预计修复：[时间估算]\n```\n\n### 模式3：跟老板说（决策视角）\n\n```text\n沟通重点：\n├─ 业务影响：对业务的影响\n├─ 发布风险：是否影响发布\n├─ 建议决策：建议怎么做\n├─ 要什么资源：需要什么支持\n└─ 时间节点：什么时候能解决\n\n沟通格式：\n[问题描述]\n业务影响：[影响描述]\n发布风险：[风险评估]\n建议决策：[建议方案]\n资源需求：[需要什么]\n时间节点：[时间计划]\n```"},{"path":"skill-card.md","content":"## Description:\n\nHelps QA teams communicate test findings and release risks to engineers, product managers, and leaders with audience-specific templates.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA practitioners use this skill to tailor bug reports, quality updates, and release-risk discussions for developers, product managers, and decision-makers.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: QA examples may expose customer, payment, identity, or production details if copied into prompts.\n\nMitigation: Mask sensitive data and use synthetic or sanitized examples instead of real production evidence.\n\nRisk: The optional installation suggestion does not pin a source version.\n\nMitigation: Verify the publisher, source, and version before running the suggested installation command.\n\n## Reference(s):\n\n- [Stakeholder communication patterns](references/comms-patterns.md)\n- [ClawHub skill listing](https://clawhub.ai/kokxi/skills/qa-stakeholder-communication)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Audience-tailored communication plans and report templates]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Communication strategy IDs use COMM-XXXX; coverage statements state their basis and identify uncovered areas.]\n\n## Skill Version(s):\n\n1.8.0 (source: frontmatter and release evidence)\n\n## Ethical Considerations:\n\nUsers 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."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"当需要告诉开发\"这个 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","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":952,"uniquenessScore":53,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T07:35:12.729Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T07:35:12.729Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:51:31.410Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}