Agent skill

Unified Notifications Ops

by affaan-m in affaan-m/ECC

将通知作为统一的 ECC 原生工作流进行操作,涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。

MITAuto-check passed

Install Unified Notifications Ops

skills CLI
$ npx skills add affaan-m/ECC --skill unified-notifications-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC unified-notifications-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/zh-CN/skills/unified-notifications-ops .claude/skills/unified-notifications-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
unified-notifications-ops
GitHub stars
276k
Token cost
~603 tokens
SKILL.md length
181 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

将通知作为统一的 ECC 原生工作流进行操作,涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。

  • Works in 5 steps: 盘点当前界面 → 决定哪些值得中断 → 在添加通道前合并重复项 → …
  • SKILL.md covers 何时使用, 首选界面, 不可妥协的规则 and 事件管道, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Unified Notifications Ops is an agent skill from affaan-m/ECC. 将通知作为统一的 ECC 原生工作流进行操作,涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。

Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

Example prompts

  • “/unified-notifications-ops”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. 盘点当前界面
  2. 决定哪些值得中断
  3. 在添加通道前合并重复项
  4. 设计 ECC 原生工作流
  5. 返回以行动为导向的设计

What it can do on your machine

Read from SKILL.md and the folder at commit 4eb71d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Unified Notifications Ops loads about 603 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 181 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~603

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 4eb71d9, republished under its MIT licence (© affaan-m). 181 words, ~603 tokens.

Download SKILL.mdSave it as .claude/skills/unified-notifications-ops/SKILL.md (or your agent's skills folder).
name
unified-notifications-ops
description
将通知作为统一的 ECC 原生工作流进行操作,涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。
origin
ECC

统一通知运维

当真正的问题不是缺少通知,而是通知系统碎片化时,使用此技能。

任务是将分散的事件整合到一个操作员界面上,包含:

  • 明确的严重等级
  • 明确的责任人
  • 明确的路由
  • 明确的后续行动

何时使用

  • 用户希望在 GitHub、Linear、本地钩子、桌面提醒、聊天或邮件之间建立统一的通知通道
  • CI 失败、审查请求、问题更新和操作员事件分散在不同的地方
  • 当前设置制造了噪音而非行动
  • 用户希望将重叠的通知分支或积压提案整合到一个 ECC 原生通道中
  • 工作区已有钩子、MCP 或连接工具,但缺乏连贯的通知策略

首选界面

从已有资源出发:

  • GitHub 问题、PR、审查、评论和 CI
  • Linear 问题/项目状态变更
  • 本地钩子事件和会话生命周期信号
  • 桌面通知原语
  • 已连接的邮件/聊天界面(如果实际存在)

优先使用 ECC 原生编排,而非建议用户采用独立的通知产品。

不可妥协的规则

  • 绝不暴露令牌、密钥、Webhook 密钥或内部标识符
  • 区分:
    • 事件来源
    • 严重等级
    • 路由通道
    • 操作员行动
  • 当中断成本不明确时,默认采用摘要优先策略
  • 不要将每个事件广播到所有通道
  • 如果真正的解决方案是更好的问题分类、钩子策略或项目流程,请明确说明

事件管道

将通道视为:

  1. 捕获 事件
  2. 分类 紧急程度和责任人
  3. 路由 到正确的通道
  4. 合并 重复和低信号噪音
  5. 附加 下一个操作员行动

目标是更少但更好的通知。

默认严重等级模型

等级示例默认处理方式
严重默认分支 CI 损坏、安全问题、发布受阻、部署失败立即中断
高请求审查、PR 失败、阻塞责任人的交接当日提醒
中问题状态变更、重要评论、积压变动摘要或队列
低重复成功、常规噪音、冗余生命周期标记抑制或折叠

如果工作区没有严重等级模型,请先构建一个,再提出自动化方案。

工作流程

1. 盘点当前界面

列出:

  • 事件来源
  • 当前通道
  • 现有的发出提醒的钩子/脚本
  • 同一事件的重复路径
  • 重要事项未被呈现的静默失败案例

指出 ECC 已拥有的部分。

2. 决定哪些值得中断

针对每个事件族,回答:

  • 谁需要知道?
  • 他们需要多快知道?
  • 应该中断、批量处理还是仅记录?

使用以下默认值:

  • 发布、CI、安全和阻塞责任人的事件需要中断
  • 中等信号更新使用摘要
  • 遥测和低信号生命周期标记仅记录
3. 在添加通道前合并重复项

检查:

  • 同一 PR 事件出现在 GitHub、Linear 和本地日志中
  • 同一失败的重复钩子通知
  • 应总结而非直接转发的评论或状态变更
  • 相互重复且未提供更好行动路径的通道

优先选择:

  • 一个规范摘要
  • 一个责任人
  • 一个主要通道
  • 一个备用路径
4. 设计 ECC 原生工作流

针对每个真实通知需求,定义:

  • 来源
  • 门控
  • 形态:即时提醒、摘要、队列或仅仪表盘
  • 通道
  • 行动

如果 ECC 已有原语,优先使用:

  • 操作员分类技能
  • 自动触发/执行的钩子
  • 委托分类的代理
  • 仅在真正缺少桥接时才使用 MCP/连接器
5. 返回以行动为导向的设计

最终输出:

  • 保留什么
  • 抑制什么
  • 合并什么
  • ECC 下一步应封装什么

输出格式

text
当前表面
- 来源
- 渠道
- 重复项
- 缺口

事件模型
- 严重
- 高
- 中
- 低

路由计划
- 来源 -> 渠道
- 原因
- 操作员/负责人

整合
- 抑制
- 合并
- 规范摘要

下一步ECC行动
- 技能/钩子/代理/MCP
- 下一步要构建的具体工作流

推荐规则

  • 优先选择一条强通道而非多条弱通道
  • 中等和低信号更新优先使用摘要
  • 信号应自动触发时优先使用钩子
  • 工作涉及分类、路由和审查优先决策时优先使用操作员技能
  • 当根本原因是积压/PR 协调而非提醒时,优先使用 project-flow-ops
  • 当用户首先需要来源盘点时,优先使用 workspace-surface-audit
  • 如果桌面通知已足够,不要发明不必要的外部桥接

良好用例

  • "我们有 GitHub、Linear 和本地钩子提醒,但没有统一的操作员流程"
  • "我们的 CI 失败噪音很大,人们都忽略了"
  • "我想要一个跨 Claude、OpenCode 和 Codex 界面的统一通知策略"
  • "判断哪些应该中断,哪些应该进入摘要"
  • "将重叠的通知 PR 想法合并为一个规范的 ECC 通道"

相关技能

  • workspace-surface-audit
  • project-flow-ops
  • github-ops
  • knowledge-ops
  • customer-billing-ops 当通知痛点涉及计费/客户运营而非工程时

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in docs/zh-CN/skills/unified-notifications-ops of affaan-m/ECC.

Open the folder on GitHubat commit 4eb71d9

Compare with similar skills

Unified Notifications Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Unified Notifications Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Unified Notifications Ops this skillaffaan-m/ECC276k—~603Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes

More from affaan-m/ECC

All 682 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    277k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed
  • Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    277k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    277k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    277k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    277k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Set an ECC-specific frontend design direction for production UI work.

    277k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Works with

Questions about Unified Notifications Ops

What does Unified Notifications Ops do?

将通知作为统一的 ECC 原生工作流进行操作,涵盖 GitHub、Linear、桌面提醒、钩子以及连接的通信界面。当真正的问题是告警路由、去重、升级或收件箱崩溃时使用。. Unified Notifications Ops is an agent skill from affaan-m/ECC.

How do I install Unified Notifications Ops in Claude Code?

Run `npx skills add affaan-m/ECC --skill unified-notifications-ops -a claude-code`. Or copy the skill folder (docs/zh-CN/skills/unified-notifications-ops in affaan-m/ECC) into .claude/skills/unified-notifications-ops in your project. Claude Code loads it when a task matches its description.

How do I install Unified Notifications Ops in Codex?

Run `npx skills add affaan-m/ECC --skill unified-notifications-ops -a codex`. Or copy the skill folder (docs/zh-CN/skills/unified-notifications-ops in affaan-m/ECC) into .agents/skills/unified-notifications-ops in your project. Codex loads it when a task matches its description.

Can I use Unified Notifications Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill unified-notifications-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unified-notifications-ops, .gemini/skills/unified-notifications-ops, .github/skills/unified-notifications-ops and .opencode/skills/unified-notifications-ops in your project.

What does Unified Notifications Ops need to run?

SKILL.md names no scripts, command-line tools or credentials: Unified Notifications Ops is instructions for the agent only.

Does Unified Notifications Ops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Unified Notifications Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Unified Notifications Ops use?

Unified Notifications Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Unified Notifications Ops use?

About 603 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Unified Notifications Ops?

Skills that share tags, products or a category with Unified Notifications Ops: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Unified Notifications Ops?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,111 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 10, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.