Menu
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.
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.
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 | status |
| description | 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. |
Show the current state of the wicked-bus.
npx wicked-bus status 2>/dev/null
If this fails, the bus isn't initialized. Suggest running wicked-bus/init.
The status command returns JSON. Display it in a readable format:
## wicked-bus Status
**Database**: {db_path}
**Events**: {total_events} total, {active_events} active (not expired)
**Providers**: {provider_count} registered
**Subscribers**: {subscriber_count} active
### Subscriber Lag
| Plugin | Filter | Cursor | Latest | Lag |
|--------|--------|--------|--------|-----|
| {plugin} | {filter} | {last_event_id} | {max_event_id} | {lag} |
If the user wants deeper diagnostics, query SQLite directly:
Event distribution by type:
sqlite3 ~/.something-wicked/wicked-bus/bus.db \
"SELECT event_type, COUNT(*) as count FROM events GROUP BY event_type ORDER BY count DESC LIMIT 20;"
Event distribution by domain:
sqlite3 ~/.something-wicked/wicked-bus/bus.db \
"SELECT domain, COUNT(*) as count FROM events GROUP BY domain ORDER BY count DESC;"
Database size:
ls -lh ~/.something-wicked/wicked-bus/bus.db
WAL size (if checkpointing is lagging):
ls -lh ~/.something-wicked/wicked-bus/bus.db-wal 2>/dev/null
Events per hour (last 24h):
sqlite3 ~/.something-wicked/wicked-bus/bus.db \
"SELECT strftime('%Y-%m-%d %H:00', emitted_at/1000, 'unixepoch') as hour, COUNT(*) as count FROM events WHERE emitted_at > (strftime('%s','now')-86400)*1000 GROUP BY hour ORDER BY hour;"
Oldest and newest events:
sqlite3 ~/.something-wicked/wicked-bus/bus.db \
"SELECT 'oldest' as which, event_id, event_type, datetime(emitted_at/1000, 'unixepoch') as time FROM events ORDER BY event_id ASC LIMIT 1 UNION ALL SELECT 'newest', event_id, event_type, datetime(emitted_at/1000, 'unixepoch') FROM events ORDER BY event_id DESC LIMIT 1;"
Deregistered subscriptions:
npx wicked-bus list --include-deregistered --json
Configuration:
cat ~/.something-wicked/wicked-bus/config.json
If WICKED_BUS_DATA_DIR is set, use that path instead of the default.
Flag these issues if detected: