Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
| name | update |
| description | 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. |
Check for and install updates to wicked-bus and its skills.
Commands work on macOS, Linux, and Windows. Use agent-native tools (Read, Write, Grep, Glob) over shell commands when possible.
Check both global and local installations:
npm list -g wicked-bus --json 2>/dev/null | python3 -c "
import json, sys
try:
d = json.load(sys.stdin)
deps = d.get('dependencies', {})
v = deps.get('wicked-bus', {}).get('version', 'not installed')
print(v)
except Exception:
print('not installed')
" 2>/dev/null || python -c "
import json, sys
try:
d = json.load(sys.stdin)
deps = d.get('dependencies', {})
v = deps.get('wicked-bus', {}).get('version', 'not installed')
print(v)
except Exception:
print('not installed')
"
Also check local (project-level) install:
npm list wicked-bus --json 2>/dev/null
npm view wicked-bus version 2>/dev/null
If installed version matches latest: "wicked-bus is up to date (v{version})."
If an update is available: "wicked-bus v{new} is available (you have v{current}). Update now?"
For global install:
npm install -g wicked-bus@latest 2>&1
For local (project) install:
npm install wicked-bus@latest 2>&1
If EACCES / permission denied:
sudo npm install -g wicked-bus@latestAfter updating the package, run the installer to copy updated skills:
npx wicked-bus-install
Or with a specific CLI target:
npx wicked-bus-install --cli=claude
Re-run the Step 1 version check. Confirm the version matches latest.
If it still shows the old version:
which wicked-bus (macOS/Linux) or where wicked-bus (Windows)npm cache clean --forcewicked-bus updated: v{old} → v{new}
Skills refreshed in {N} CLIs: {list}
If the user just wants to check, stop after Step 3 and report current vs. available version.