parallel-monitor
Continuously track the web for changes on a recurring cadence. Use when the user asks to 'monitor', 'track changes to', 'watch', or 'alert me when' something on the web changes — e.g., 'Track price changes for iPhone 16', 'Alert me when Tesla files a new 8-K', 'Monitor competitor pricing pages weekly'. Also use to list, inspect, update, or stop existing monitors, including requests to delete them.
Install
git clone https://github.com/parallel-web/parallel-cursor-plugin /tmp/parallel-cursor-plugin && ln -s /tmp/parallel-cursor-plugin/skills/parallel-monitor ~/.claude/skills/parallel-monitorFrom README
Web Monitor Action: $ARGUMENTS Requires parallel-cli ≥ 0.4.0 for the GA Monitor commands. If a Monitor command or option is missing, tell the user to update through their method (see ), then retry. What this skill does Monitors are long-running, server-side jobs that re-check the web on a cadence and emit events when something changes. Unlike search/research/findall (one-shot lookups), monitors persist until cancelled and can optionally deliver detected events through a webhook. Creation does not establish an ongoing agent notification service: explain how to read server-side events or use the configured webhook, without promising chat or email alerts. The default type is eventstream, with frequency 1d and server processor lite. A snapshot monitor requires an existing Task run ID. Create or modify only the resource requested by the user; do not create a monitor just to demonstrate the skill.
More from this repo
parallel-data-enrichment
Bulk data enrichment.
parallel-deep-research
ONLY use when user explicitly says 'deep research', 'exhaustive', 'comprehensive report', or 'thorough investigation'.
parallel-findall
Discover entities (companies, people, products, etc.) matching a natural-language description.