Best fit
- 将通知作为统一的 ECC 原生工作流进行操作，涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。
affaan-m/ECC
unified-notifications-ops
将通知作为统一的 ECC 原生工作流进行操作，涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。
62Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/unified-notifications-ops"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn unified-notifications-ops's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: 当真正的问题不是缺少通知，而是通知系统碎片化时，使用此技能。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/unified-notifications-ops"Bring this context
- A concrete task that matches the documented purpose of unified-notifications-ops.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned unified-notifications-ops instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read unified-notifications-ops through these 5 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
何时使用
用户希望在 GitHub、Linear、本地钩子、桌面提醒、聊天或邮件之间建立统一的通知通道 CI 失败、审查请求、问题更新和操作员事件分散在不同的地方 当前设置制造了噪音而非行动 用户希望将重叠的通知分支或积压提案整合到一个 ECC 原生通道中 工作区已有钩子、MCP 或连接工具，但缺乏连贯的通知策略
用户希望在 GitHub、Linear、本地钩子、桌面提醒、聊天或邮件之间建立统一的通知通道CI 失败、审查请求、问题更新和操作员事件分散在不同的地方当前设置制造了噪音而非行动
首选界面
GitHub 问题、PR、审查、评论和 CI Linear 问题/项目状态变更 本地钩子事件和会话生命周期信号 桌面通知原语 已连接的邮件/聊天界面（如果实际存在）
GitHub 问题、PR、审查、评论和 CILinear 问题/项目状态变更本地钩子事件和会话生命周期信号
不可妥协的规则
绝不暴露令牌、密钥、Webhook 密钥或内部标识符 区分： 事件来源 严重等级 路由通道 操作员行动 当中断成本不明确时，默认采用摘要优先策略 不要将每个事件广播到所有通道 如果真正的解决方案是更好的问题分类、钩子策略或项目流程，请明确说明
绝不暴露令牌、密钥、Webhook 密钥或内部标识符区分：事件来源
事件管道
1. 捕获 事件 2. 分类 紧急程度和责任人 3. 路由 到正确的通道 4. 合并 重复和低信号噪音 5. 附加 下一个操作员行动
捕获 事件分类 紧急程度和责任人路由 到正确的通道
默认严重等级模型
如果工作区没有严重等级模型，请先构建一个，再提出自动化方案。
如果工作区没有严重等级模型，请先构建一个，再提出自动化方案。
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use unified-notifications-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned unified-notifications-ops source to [task]. Pay particular attention to these source sections: “何时使用”, “首选界面”, “不可妥协的规则”, “事件管道”, “默认严重等级模型”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current unified-notifications-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “何时使用” has been checked.
The source section “首选界面” has been checked.
The source section “不可妥协的规则” has been checked.
The source section “事件管道” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
unified-notifications-ops
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailunified-notifications-ops
GitHub、Linear、デスクトップアラート、フック、接続された通信インターフェースを網羅する、統合されたECCネイティブワークフローとして通知を運用する。真の問題がアラートルーティング、重複排除、エスカレーション、またはインボックス崩壊である場合に使用する。
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does unified-notifications-ops do?
当真正的问题不是缺少通知，而是通知系统碎片化时，使用此技能。
How do I start using unified-notifications-ops?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/unified-notifications-ops". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
62/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation19/30
Specificity11/25
Maintenance20/20
Trust signals12/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
unified-notifications-ops by affaan-m
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
unified-notifications-ops by affaan-m
GitHub、Linear、デスクトップアラート、フック、接続された通信インターフェースを網羅する、統合されたECCネイティブワークフローとして通知を運用する。真の問題がアラートルーティング、重複排除、エスカレーション、またはインボックス崩壊である場合に使用する。
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
统一通知运维
当真正的问题不是缺少通知，而是通知系统碎片化时，使用此技能。
任务是将分散的事件整合到一个操作员界面上，包含：
- 明确的严重等级
- 明确的责任人
- 明确的路由
- 明确的后续行动
何时使用
- 用户希望在 GitHub、Linear、本地钩子、桌面提醒、聊天或邮件之间建立统一的通知通道
- CI 失败、审查请求、问题更新和操作员事件分散在不同的地方
- 当前设置制造了噪音而非行动
- 用户希望将重叠的通知分支或积压提案整合到一个 ECC 原生通道中
- 工作区已有钩子、MCP 或连接工具，但缺乏连贯的通知策略
首选界面
从已有资源出发：
- GitHub 问题、PR、审查、评论和 CI
- Linear 问题/项目状态变更
- 本地钩子事件和会话生命周期信号
- 桌面通知原语
- 已连接的邮件/聊天界面（如果实际存在）
优先使用 ECC 原生编排，而非建议用户采用独立的通知产品。
不可妥协的规则
- 绝不暴露令牌、密钥、Webhook 密钥或内部标识符
- 区分：
- 事件来源
- 严重等级
- 路由通道
- 操作员行动
- 当中断成本不明确时，默认采用摘要优先策略
- 不要将每个事件广播到所有通道
- 如果真正的解决方案是更好的问题分类、钩子策略或项目流程，请明确说明
事件管道
将通道视为：
- 捕获 事件
- 分类 紧急程度和责任人
- 路由 到正确的通道
- 合并 重复和低信号噪音
- 附加 下一个操作员行动
目标是更少但更好的通知。
默认严重等级模型
| 等级 | 示例 | 默认处理方式 |
|---|---|---|
| 严重 | 默认分支 CI 损坏、安全问题、发布受阻、部署失败 | 立即中断 |
| 高 | 请求审查、PR 失败、阻塞责任人的交接 | 当日提醒 |
| 中 | 问题状态变更、重要评论、积压变动 | 摘要或队列 |
| 低 | 重复成功、常规噪音、冗余生命周期标记 | 抑制或折叠 |
如果工作区没有严重等级模型，请先构建一个，再提出自动化方案。
工作流程
1. 盘点当前界面
列出：
- 事件来源
- 当前通道
- 现有的发出提醒的钩子/脚本
- 同一事件的重复路径
- 重要事项未被呈现的静默失败案例
指出 ECC 已拥有的部分。
2. 决定哪些值得中断
针对每个事件族，回答：
- 谁需要知道？
- 他们需要多快知道？
- 应该中断、批量处理还是仅记录？
使用以下默认值：
- 发布、CI、安全和阻塞责任人的事件需要中断
- 中等信号更新使用摘要
- 遥测和低信号生命周期标记仅记录
3. 在添加通道前合并重复项
检查：
- 同一 PR 事件出现在 GitHub、Linear 和本地日志中
- 同一失败的重复钩子通知
- 应总结而非直接转发的评论或状态变更
- 相互重复且未提供更好行动路径的通道
优先选择：
- 一个规范摘要
- 一个责任人
- 一个主要通道
- 一个备用路径
4. 设计 ECC 原生工作流
针对每个真实通知需求，定义：
- 来源
- 门控
- 形态：即时提醒、摘要、队列或仅仪表盘
- 通道
- 行动
如果 ECC 已有原语，优先使用：
- 操作员分类技能
- 自动触发/执行的钩子
- 委托分类的代理
- 仅在真正缺少桥接时才使用 MCP/连接器
5. 返回以行动为导向的设计
最终输出：
- 保留什么
- 抑制什么
- 合并什么
- ECC 下一步应封装什么
输出格式
当前表面
- 来源
- 渠道
- 重复项
- 缺口
事件模型
- 严重
- 高
- 中
- 低
路由计划
- 来源 -> 渠道
- 原因
- 操作员/负责人
整合
- 抑制
- 合并
- 规范摘要
下一步ECC行动
- 技能/钩子/代理/MCP
- 下一步要构建的具体工作流
推荐规则
- 优先选择一条强通道而非多条弱通道
- 中等和低信号更新优先使用摘要
- 信号应自动触发时优先使用钩子
- 工作涉及分类、路由和审查优先决策时优先使用操作员技能
- 当根本原因是积压/PR 协调而非提醒时，优先使用
project-flow-ops - 当用户首先需要来源盘点时，优先使用
workspace-surface-audit - 如果桌面通知已足够，不要发明不必要的外部桥接
良好用例
- "我们有 GitHub、Linear 和本地钩子提醒，但没有统一的操作员流程"
- "我们的 CI 失败噪音很大，人们都忽略了"
- "我想要一个跨 Claude、OpenCode 和 Codex 界面的统一通知策略"
- "判断哪些应该中断，哪些应该进入摘要"
- "将重叠的通知 PR 想法合并为一个规范的 ECC 通道"
相关技能
workspace-surface-auditproject-flow-opsgithub-opsknowledge-opscustomer-billing-ops当通知痛点涉及计费/客户运营而非工程时
- Source repo
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/unified-notifications-ops/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected