wps-events

Define Wave PubSub events with broker routing and scoped persistence.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/lihonghuacgk/waveterm --skill wps-events-lihonghuacgk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wps-events
Source: https://github.com/lihonghuacgk/waveterm/tree/main/.kilocode/skills/wps-events
Command: npx skills add https://github.com/lihonghuacgk/waveterm --skill wps-events-lihonghuacgk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wave PubSub (WPS) enables asynchronous communication between Wave Terminal components, allowing publishers and subscribers to exchange events in a decoupled, reliable way.

Core Features & Use Cases

  • Event broker: central routing of published events to interested subscribers based on event type and scope.
  • Event structure and typing: defined WaveEvent data formats with optional scopes and persistence for history.
  • Publishing and subscribing: simple APIs to publish events from publishers and subscribe to updates from subscribers across modules.
  • Use Case: coordinate UI widgets, editors, and services to react to system events like block updates, status changes, and cross-component messaging.

Quick Start

Define a new event type in your publisher, subscribe in your consumer, and publish events through the broker to enable live inter-component communication.

Frequently Asked Questions about wps-events

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

FAQPage Schema
How do I coordinate asynchronous messaging between Wave Terminal components?

Wave PubSub events coordinate asynchronous messaging between Wave Terminal components by using a broker-based publish/subscribe pattern, allowing publishers and subscribers to exchange events in a decoupled way.

What is a broker-based publish/subscribe pattern for event routing?

A broker-based publish/subscribe pattern routes published events to interested subscribers based on event type and scope, enabling central routing of asynchronous messaging across different modules.

How do I define and publish events across modules using Wave PubSub?

To define and publish events, define a new event type in your publisher component, subscribe in your consumer component, and publish events through the broker to enable live inter-component communication.

Can I persist event history when subscribing to Wave PubSub events?

Yes, Wave PubSub events support optional persistence for history, allowing subscribers to access past event data alongside defined WaveEvent data formats with optional scopes.

Does Wave PubSub support event scoping for cross-component messaging?

Wave PubSub supports event scoping to manage cross-component messaging, ensuring published events are routed to subscribers based on their specific event type and defined scope.

When do I need a pubsub event broker for UI widgets and editors?

You need a pubsub event broker when coordinating UI widgets, editors, and services to react to system events like block updates, status changes, and cross-component messaging in a decoupled architecture.