Help us improve
Share bugs, ideas, or general feedback.
From parallel
Creates and manages long-running web monitors that track page changes on a recurring cadence (hourly/daily/weekly). Use to monitor pricing, filings, competitor pages, or any web content that changes over time.
npx claudepluginhub parallel-web/parallel-agent-skills --plugin parallelHow this skill is triggered — by the user, by Claude, or both
Slash command
/parallel:parallel-monitor <create|list|events|get|update|simulate|event-group|delete> [args]<create|list|events|get|update|simulate|event-group|delete> [args]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Action: $ARGUMENTS
Detects website content changes and sends notifications via webhook or email, without cron jobs or scrapers. Useful for monitoring pricing, docs, job postings, changelogs, and status pages.
Sets up Yutori Scouts for continuous web monitoring to track news, competitors, product updates, funding rounds, price changes, or recurring web information.
Generates a monitoring plan for tracking web page changes using change-detection tools, RSS feeds, or custom scripts with webhook alerts.
Share bugs, ideas, or general feedback.
Action: $ARGUMENTS
Requires
parallel-cli≥ 0.3.0 (themonitorcommand was added in 0.3.0). Ifparallel-cli monitorerrors withno such commandor similar, tell the user to runparallel-cli update(orpipx upgrade parallel-web-toolsif installed via pipx), then retry.
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 deleted and can optionally fire a webhook on each event.
Parse the user's request and pick one:
| Intent | Action |
|---|---|
| "Track / watch / monitor / alert me when X" | create |
| "What am I monitoring?" / "List monitors" | list |
| "What changed?" / "Show me events for monitor X" | events |
| "Show monitor X" / "Get details for X" | get |
| "Change cadence / query / webhook for X" | update |
| "Test the webhook" / "Fire a test event" | simulate (requires a webhook on the monitor) |
| "Show me the full payload for event group X" | event-group |
| "Stop / delete monitor X" | delete (always confirm before deleting) |
parallel-cli monitor create "<query>" --cadence daily --json
Cadence options: hourly, daily (default), weekly, every_two_weeks. Match cadence to how often the source actually changes — hourly for prices/news, weekly for filings/staffing.
Optional flags:
--webhook https://example.com/hook — POST events to a URL as they happen--metadata '{"team":"competitive-intel"}' — attach JSON metadata for your own bookkeeping--output-schema '<json>' — structure the event payload (advanced)Parse the JSON to extract the monitor_id. Tell the user:
parallel-cli monitor events $MONITOR_ID later to see what changedIf they configured a webhook, suggest testing it:
parallel-cli monitor simulate "$MONITOR_ID"
simulate requires a webhook to be configured on the monitor. Without one it errors with Webhook not configured for this monitor — do not run it on monitors created without --webhook.
parallel-cli monitor list -n 10 --json
Default to -n 10 — accounts with many historical monitors can return megabytes of JSON otherwise. Raise the limit only if the user explicitly asks for "all" or a larger set. Present as a table: ID, query (truncated), cadence, created.
Note:
monitor listis not guaranteed to be sorted newest-first, so a monitor you just created may not appear in the first page of results. If a user is verifying creation, prefermonitor get $MONITOR_ID(using the ID returned by create) over scanning the list.
parallel-cli monitor events "$MONITOR_ID" --lookback 10d --json
Lookback format: Nd (days) or Nw (weeks). Default 10d.
For deeper detail on a specific event group:
parallel-cli monitor event-group "$MONITOR_ID" "$EVENT_GROUP_ID" --json
Summarize for the user: count of events in the period, then a bulleted list of what changed with timestamps. Cite source URLs from the event payload.
parallel-cli monitor get "$MONITOR_ID" --json
parallel-cli monitor update "$MONITOR_ID" --cadence weekly --json
parallel-cli monitor delete "$MONITOR_ID" --json
Always confirm before deleting — deletion is permanent.
Requires parallel-cli (installed and authenticated). If parallel-cli --version fails, or if a later command fails with an authentication error, tell the user to see https://docs.parallel.ai/integrations/cli and stop.