New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Unified Notifications Ops

by affaan-m in affaan-m/ECC

Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces.

MITAuto-check passedData & Analytics

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/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
277k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
685 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces.

  • Works in 5 steps: Inventory the current surface → Decide what deserves interruption → Collapse duplicates before adding channels → …
  • The real problem is alert routing
  • SKILL.md covers When to Use, Preferred Surface, Non-Negotiable Rules and Event Pipeline, 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. 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.

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

It sits in Data & Analytics, covering Data cleaning and Email management. 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.

When your agent uses it

  • The real problem is alert routing
  • Tasks that involve Data cleaning
  • Tasks that involve Email management

Example prompts

  • “/unified-notifications-ops”

Workflow steps

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

  1. Inventory the current surface
  2. Decide what deserves interruption
  3. Collapse duplicates before adding channels
  4. Design the ECC-native workflow
  5. Return an action-biased design

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. 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 1.4k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 685 words of instructions outside code blocks.

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

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 2d515e4, republished under its MIT licence (© affaan-m). 685 words, ~1,408 tokens.

Download SKILL.mdSave it as .claude/skills/unified-notifications-ops/SKILL.md (or your agent's skills folder).
name
unified-notifications-ops
description
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.
metadata.origin
ECC

Unified Notifications Ops

Use this skill when the real problem is not a missing ping. The real problem is a fragmented notification system.

The job is to turn scattered events into one operator surface with:

  • clear severity
  • clear ownership
  • clear routing
  • clear follow-up action

When to Use

  • the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email
  • CI failures, review requests, issue updates, and operator events are arriving in disconnected places
  • the current setup creates noise instead of action
  • the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane
  • the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy

Preferred Surface

Start from what already exists:

  • GitHub issues, PRs, reviews, comments, and CI
  • Linear issue/project movement
  • local hook events and session lifecycle signals
  • desktop notification primitives
  • connected email/chat surfaces when they actually exist

Prefer ECC-native orchestration over telling the user to adopt a separate notification product.

Non-Negotiable Rules

  • never expose tokens, secrets, webhook secrets, or internal identifiers
  • separate:
    • event source
    • severity
    • routing channel
    • operator action
  • default to digest-first when interruption cost is unclear
  • do not fan out every event to every channel
  • if the real fix is better issue triage, hook policy, or project flow, say so explicitly

Event Pipeline

Treat the lane as:

  1. Capture the event
  2. Classify urgency and owner
  3. Route to the correct channel
  4. Collapse duplicates and low-signal churn
  5. Attach the next operator action

The goal is fewer, better notifications.

Default Severity Model

ClassExamplesDefault handling
Criticalbroken default-branch CI, security issue, blocked release, failed deployinterrupt now
Highreview requested, failing PR, owner-blocking handoffsame-day alert
Mediumissue state changes, notable comments, backlog movementdigest or queue
Lowrepeat successes, routine churn, redundant lifecycle markerssuppress or fold

If the workspace has no severity model, build one before proposing automation.

Workflow

1. Inventory the current surface

List:

  • event sources
  • current channels
  • existing hooks/scripts that emit alerts
  • duplicate paths for the same event
  • silent failure cases where important things are not being surfaced

Call out what ECC already owns.

2. Decide what deserves interruption

For each event family, answer:

  • who needs to know?
  • how fast do they need to know?
  • should this interrupt, batch, or just log?

Use these defaults:

  • interrupt for release, CI, security, and owner-blocking events
  • digest for medium-signal updates
  • log-only for telemetry and low-signal lifecycle markers
Show full SKILL.md (282 more words)Show less
3. Collapse duplicates before adding channels

Look for:

  • the same PR event appearing in GitHub, Linear, and local logs
  • repeated hook notifications for the same failure
  • comments or status churn that should be summarized instead of forwarded raw
  • channels that duplicate each other without adding a better action path

Prefer:

  • one canonical summary
  • one owner
  • one primary channel
  • one fallback path
4. Design the ECC-native workflow

For each real notification need, define:

  • source
  • gate
  • shape: immediate alert, digest, queue, or dashboard-only
  • channel
  • action

If ECC already has the primitive, prefer:

  • a skill for operator triage
  • a hook for automatic emission/enforcement
  • an agent for delegated classification
  • an MCP/connector only when a real bridge is missing
5. Return an action-biased design

End with:

  • what to keep
  • what to suppress
  • what to merge
  • what ECC should wrap next

Output Format

text
CURRENT SURFACE
- sources
- channels
- duplicates
- gaps

EVENT MODEL
- critical
- high
- medium
- low

ROUTING PLAN
- source -> channel
- why
- operator owner

CONSOLIDATION
- suppress
- merge
- canonical summaries

NEXT ECC MOVE
- skill / hook / agent / MCP
- exact workflow to build next

Recommendation Rules

  • prefer one strong lane over many weak ones
  • prefer digests for medium and low-signal updates
  • prefer hooks when the signal should emit automatically
  • prefer operator skills when the work is triage, routing, and review-first decision-making
  • prefer project-flow-ops when the root cause is backlog / PR coordination rather than alerts
  • prefer workspace-surface-audit when the user first needs a source inventory
  • if desktop notifications are enough, do not invent an unnecessary external bridge

Good Use Cases

  • "We have GitHub, Linear, and local hook alerts, but no single operator flow"
  • "Our CI failures are noisy and people ignore them"
  • "I want one notification policy across Claude, OpenCode, and Codex surfaces"
  • "Figure out what should interrupt versus land in a digest"
  • "Collapse overlapping notification PR ideas into one canonical ECC lane"
  • workspace-surface-audit
  • project-flow-ops
  • github-ops
  • knowledge-ops
  • customer-billing-ops when the notification pain is billing/customer operations rather than engineering

© 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 skills/unified-notifications-ops of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

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/ECC277k1 repos~1.4kAutomated safety check: PassMIT
Dingo VerifyMigoXLab/dingo757—~741Automated safety check: NotesApache-2.0
Connect Apps with ComposioComposioHQ/awesome-claude-skills77k3 repos~557Automated safety check: PassNone
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0
Composio Cloud Toolsquarqlabs/argus279—~543Automated safety check: PassApache-2.0
ClawdiClawdi-AI/clawdi103—~4.9kAutomated safety check: NotesMIT

Similar skills

  • Dingo Verify

    MigoXLab/dingo

    A skill your agent uses when the user wants to fact-check an article or verify factual claims in a document.

    757 GitHub stars~741 tokensUpdated 2 days ago
    Data & AnalyticsAuto-check: notes

  • Connect Apps with Composio

    ComposioHQ/awesome-claude-skills

    Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.

    77k GitHub starsUsed in 3 repos~557 tokens
    Productivity & AutomationAuto-check passed

  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 17 days ago
    Productivity & AutomationAuto-check passed

  • Composio Cloud Tools

    quarqlabs/argus

    Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.

    279 GitHub stars~543 tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed

  • Clawdi

    Clawdi-AI/clawdi

    API keys, tokens, memory, sessions, Projects, integrations. An agent skill from Clawdi-AI/clawdi.

    103 GitHub stars~4.9k tokensUpdated today
    Productivity & AutomationAuto-check: notes

  • Connectors

    autonomous-ai/Physical-AI-Operating-System

    Discover and use linked third-party services (Gmail, Google Calendar, Google Drive, Notion, Figma, Asana, Linear, GitHub, Ahrefs, Facebook Fan Page and others).

    407 GitHub stars~10k tokensUpdated yesterday
    Productivity & AutomationAuto-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

  • VideoDB Video Search and Editing

    affaan-m/ECC

    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

  • Master Agreement Generator

    affaan-m/ECC

    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

  • Frontend Design Direction

    affaan-m/ECC

    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

Categories

Questions about Unified Notifications Ops

What does Unified Notifications Ops do?

Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Unified Notifications Ops is an agent skill from affaan-m/ECC. Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces.

When should I use Unified Notifications Ops?

Unified Notifications Ops fits situations like: the real problem is alert routing; tasks that involve Data cleaning; tasks that involve Email management.

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 (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 (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 1.4k tokens (SKILL.md is roughly 5.6k 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: Dingo Verify (MigoXLab/dingo, 757 stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Openloomi Connectors (melandlabs/openloomi, 1k stars) and Composio Cloud Tools (quarqlabs/argus, 279 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,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 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.