swarm-monitor

Discovers changelog channels and watches for unread messages using the ve CLI tool.

3|1|Updated Jan 8, 2026

Search Tags:#changelog #monitoring #channels #swarm #ve-cli #watch-multi

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill swarm-monitor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swarm-monitor
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/swarm-monitor
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill swarm-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing swarm-level changelog visibility across many channels is tedious and error-prone, so this skill provides a unified view of activity to reduce manual checks and blind spots.

Core Features & Use Cases

Discover and list all relevant changelog channels across a swarm.
Show per-channel cursors, head positions, and unread counts for quick situational awareness.
Initiate an event-driven multi-channel watch that notifies on new messages and auto-advances cursors.

Quick Start

Run the swarm monitor to discover channels and start watching for new changelog messages.

Frequently Asked Questions about swarm-monitor

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

FAQPage Schema

How do I monitor changelog activity across multiple swarm channels?▼

To monitor changelog activity across multiple swarm channels, use a unified command to discover channels and launch an event-driven watch that surfaces unread messages and auto-advances cursors.

Can I see unread message counts for individual changelog channels?▼

Yes, you can view per-channel unread counts, head positions, and cursors to gain quick situational awareness of swarm changelog activity without manual checks.

Do I need the ve CLI tool to watch multi-channel swarm changelogs?▼

Yes, watching multi-channel swarm changelogs requires the ve CLI tool and access to the bound swarm configuration to discover channels and initiate the watch.

What is the best way to reduce blind spots when tracking changelogs for several services?▼

The best way to reduce blind spots when tracking changelogs for several services is to use a unified monitoring view that aggregates activity and notifies you of new messages across all channels.

Does the swarm monitor automatically advance cursors when new changelog messages arrive?▼

Yes, the swarm monitor initiates an event-driven watch that notifies on new changelog messages and automatically advances cursors to reduce manual tracking overhead.

Why does managing swarm-level changelog visibility across many channels become error-prone?▼

Swarm-level changelog visibility becomes error-prone due to the tedious nature of manual checks across many channels, which creates blind spots and missed updates that a unified view solves.