myco:notification-system-operations

Configure, debug, and extend Myco notification systems across domains and modes.

12|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/goondocks-co/myco --skill myco-notification-system-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myco:notification-system-operations
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/notification-system-operations
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-notification-system-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing and debugging complex notification flows across domains is error-prone without clear defaults, mode resolution, and robust testing.

Core Features & Use Cases

  • Domain self-registration and default configuration for new notification domains
  • Deterministic mode resolution across payload, domain, global, and registry levels
  • Enforced banner-only browser notifications and proper summary handling
  • Dismissed-vs-deleted semantics and on-write pruning to bound data
  • Debug protocols and end-to-end smoke tests to verify emissions from restart to UI

Quick Start

Trigger a test emission and verify it surfaces in the drawer and browser notification after applying the domain defaults and mode-resolution rules.

Frequently Asked Questions about myco:notification-system-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix notification mode resolution conflicts across different domains?

Resolve notification mode conflicts using deterministic resolution logic applied across payload, domain, global, and registry levels to ensure predictable emission behavior.

What is the best way to manage dismissed versus deleted notification data?

Browser notification systems display incorrect summaries when banner-only enforcement and proper summary handling rules are not applied to the domain configuration.

How do I debug a notification system when emissions are missing from the UI?

Debug notification system emissions by applying end-to-end smoke tests that verify domain defaults, mode resolution logic, and React Router navigation fixes from restart to UI surfacing.

Why does my browser notification system show summary banners incorrectly?

Configure new notification domains through self-registration and default configuration, ensuring proper emission coverage, banner filter integration, and mode resolution compliance.

How do I configure a new notification domain with default settings?

Configure new notification domains through self-registration and default configuration, ensuring proper emission coverage, banner filter integration, and mode resolution compliance.

Can I use React Router navigation fixes within a notification daemon workflow?

React Router navigation fixes integrate within notification daemon workflows by addressing UI filtering and drawer surfacing issues during end-to-end emission and smoke test verification.