Fetcher eventbus
Skill Ahoo-Wang/skills/plugins/ahoo-fetcher-skills/skills/fetcher-eventbus
A central aggregation repository for Agent Skills from Ahoo-Wang's open source projects.
npx -y skills add Ahoo-Wang/skills --skill fetcher-eventbusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when implementing typed event buses, serial or parallel event execution, BroadcastChannel or storage-based cross-tab messaging, handler priority, once handlers, name generation, or event synchronization across browser contexts.
SKILL.md
1.8 KB, as published. Nobody here has run it
fetcher-eventbus
Use This Skill When
- The task mentions event bus, event handlers, broadcasts, or cross-tab communication.
- The task needs serial versus parallel event execution semantics.
- The task involves
BroadcastChannel, storage fallback messaging, or cross-tab sync. - The task needs handler ordering, duplicate-name prevention, or once-only handlers.
Workflow
- Choose
SerialTypedEventBuswhen ordering and sequential side effects matter. - Choose
ParallelTypedEventBuswhen handlers are independent and latency matters. - Choose
BroadcastTypedEventBusor a cross-tab messenger for browser-tab synchronization. - Give handlers stable names and explicit order values when behavior must be predictable.
- Load
references/api.mdfor interface details, messenger fallback behavior, and examples.
Key Practices
- Use one event type per focused bus unless a multi-type router materially reduces duplication.
- Treat handler names as identifiers, not labels; duplicate names are rejected.
- Call cleanup functions or
destroy()for long-lived UI and test code.
References
references/api.md: Detailed package API, examples, and edge-case guidance. Load it only when the task needs TypedEventBus contracts, event handler fields, serial/parallel/broadcast examples, messenger APIs, and fallback chains.
Related Skills
- $fetcher-storage: Use when eventing is tied to persistent key-value state.
- $fetcher-react-hooks: Use when React components subscribe to event buses.
- $fetcher-cosec-auth: Use when auth token or device storage changes must broadcast.