Unified Notifications Ops
Operate notifications as one workflow across GitHub, Linear, desktop alerts, and hooks: routing, deduplication, and escalation that cut noise.
- What
- Operate notifications as one workflow across GitHub, Linear, desktop alerts, and hooks: routing, deduplication, and escalation that cut noise.
- Cost
- Free
- Needs
- Use "Unified Notifications Ops" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an operations skill for the real notification problem, which is never a missing ping but a fragmented system. It turns scattered events into one operator surface with clear severity, clear ownership, clear routing, and a clear follow-up action, across GitHub, Linear, desktop alerts, hooks, and connected chat or email surfaces. Start from what already exists (issues, PRs, CI, Linear movement, hook events) and prefer native orchestration over adopting yet another notification product. Non-negotiable rules: never expose tokens, secrets, or webhook secrets; separate event source, severity, routing channel, and operator action; default to digest-first when interruption cost is unclear. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; needs your actual tools connected to be useful; digest-first means some urgent things wait for the digest, tune severity carefully. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Unified Notifications Ops" with your Muse. Prerequisites: your real tools connected (GitHub, Linear, desktop alerts, or hooks). Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/unified-notifications-ops/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Design a unified notification lane for my setup: GitHub + [your tools]. Severity, ownership, routing, follow-up action." 3. Ask: "Where am I getting noise instead of action today?" and let it consolidate overlapping branches. Tip: default to digest-first; only truly paging-worthy events should interrupt. Safety: a skill is plain-text instructions; it runs nothing by itself. Never expose tokens, secrets, or webhook secrets in a chat.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.