Menu
Initialize wicked-bus or connect to an existing instance. Use when setting up the bus for the first time, checking if it's running, or configuring a project to use it. Auto-triggered when any wicked-bus skill detects no config.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Emit events to the wicked-bus. Use when publishing events from a plugin, logging activity to the bus, or integrating a new system with the event bridge. Covers both programmatic (Node.js) and CLI usage.
Guide for naming wicked-bus events — helps choose event_type, domain, and subdomain when emitting events. Use when creating new events, integrating a plugin with the bus, or reviewing event naming for consistency.
Query and debug the wicked-bus. Use when checking bus health, inspecting events, debugging delivery issues, tracing event flow, or investigating why a subscriber isn't receiving events. Covers status, replay, and direct SQLite queries.
Show wicked-bus health, statistics, and diagnostics. Event counts, subscriber lag, provider list, database size, and configuration. Use when: "bus status", "is the bus healthy", "how many events", "show bus stats", or when diagnosing delivery issues.
Subscribe to wicked-bus events. Use when consuming events from the bus, setting up event listeners, polling for new events, or integrating as a subscriber. Covers registration, polling, acknowledgment, and filter patterns.
Check for and install wicked-bus updates. Compares installed version against npm registry, updates skills across all detected CLIs. Use when: "update wicked-bus", "check for bus updates", "wicked-bus update", or periodically to stay current.
| name | init |
| description | Initialize wicked-bus or connect to an existing instance. Use when setting up the bus for the first time, checking if it's running, or configuring a project to use it. Auto-triggered when any wicked-bus skill detects no config. |
Set up wicked-bus for the current project. Detects an existing running instance before creating a new one.
Before creating anything, check if wicked-bus is already initialized:
# Check if the data directory exists
ls ~/.something-wicked/wicked-bus/bus.db 2>/dev/null
If the data dir and DB exist, wicked-bus is already running. Skip to Step 4.
Also check if another agent or process already initialized it this session:
# Check if the CLI is available
npx wicked-bus status 2>/dev/null
If status returns valid JSON, the bus is live. Report to the user and skip init.
# Check if the package is available
node -e "require.resolve('wicked-bus')" 2>/dev/null || \
node -e "import('wicked-bus').then(() => console.log('found'))" 2>/dev/null
If not installed:
wicked-bus is not installed. Install it:
npm install wicked-bus
Run the init command:
npx wicked-bus init
This creates:
~/.something-wicked/wicked-bus/ data directorybus.db SQLite database with WAL modeconfig.json with defaultsVerify success by checking the JSON output for "initialized": true.
If the user wants this project to emit events, register as a provider:
Ask: "What domain name should this project use?" (default: directory name)
npx wicked-bus register \
--role provider \
--plugin {domain} \
--filter 'wicked.*'
Report:
wicked-bus is ready.
Data dir: ~/.something-wicked/wicked-bus/
DB: bus.db (WAL mode)
Status: {event count} events, {subscriber count} subscribers
If the bus was already running, say so:
wicked-bus is already initialized and running.
{status output}