parallel-monitor

Name: parallel-monitor
Author: parallel-web

9.4kinstalls6forks

How to install parallel-monitor?

parallel-web/parallel-agent-skills/parallel-monitor

$npx -y skills add parallel-web/parallel-agent-skills --skill parallel-monitor

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Web Monitor
2
3	Action: $ARGUMENTS
4
5	> 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 installation method (see <https://docs.parallel.ai/integrations/cli>), then retry.
6
7	## What this skill does
8
9	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.
10
11	## Decide the action
12
13	Parse the user's request and pick one:
14
15	\| Intent \| Action \|
16	\|---\|---\|
17	\| "Track / watch / monitor / alert me when X" \| create \|
18	\| "What am I monitoring?" / "List monitors" \| list \|
19	\| "What changed?" / "Show me events for monitor X" \| events \|
20	\| "Show monitor X" / "Get details for X" \| get \|
21	\| "Change cadence / webhook for X" \| update \|
22	\| "Check monitor X now" / "Run it now" \| trigger \|
23	\| "Show me the full payload for event group X" \| events with `--event-group-id` \|
24	\| "Stop / delete monitor X" \| cancel (always confirm before cancelling) \|
25
26	## Create a monitor
27
28	```bash
29	parallel-cli monitor create "<query>" --frequency 1d --json
30	```
31
32	Frequency accepts `<n><unit>` with `h`, `d`, or `w` (for example `1h`, `1d`, or `1w`). The aliases `hourly`, `daily`, `weekly`, and `every_two_weeks` are also accepted. Match cadence to how often the source actually changes — hourly for prices/news, weekly for filings/staffing.
33
34	Optional flags:
35
36	- `--webhook https://example.com/hook` — deliver detected events to a URL
37	- `--metadata '{"team":"competitive-intel"}'` — attach JSON metadata for your own bookkeeping
38	- `--output-schema '<json>'` — structure the event payload (advanced)
39
40	Parse the JSON to extract the `monitor_id`. Tell the user:
41
42	- The monitor has been created with its ID
43	- The frequency (so they know how often the monitor checks)
44	- That recent events are available server-side — they can run `parallel-cli monitor events $MONITOR_ID` later to see what changed
45
46	## List monitors
47
48	```bash
49	parallel-cli monitor list -n 10 --json
50	```
51
52	Default to `-n 10` for concise output. `list` returns active monitors only by default; add `--status active --status cancelled` when the user asks to include cancelled monitors. Raise the limit only for a larger set. Present as a table: ID, query or Task Run (truncated), frequency, created.
53
54	> Note: `monitor list` is sorted newest-first. If a user is verifying creation, prefer `monitor get $MONITOR_ID` (using the ID returned by create) over scanning the list.
55
56	## View events for a monitor
57
58	```bash
59	parallel-cli monitor events "$MONITOR_ID" --json
60	```
61
62	Events are returned newest-first. If the response contains `next_cursor`, pass it with `--cursor` to retrieve another page.
63
64	For deeper detail on a specific event group:
65
66	```bash
67	parallel-cli monitor events "$MONITOR_ID" --event-group-id "$EVENT_GROUP_ID" --json
68	```
69
70	Summarize for the user: count of events, then a bulleted list of what changed with dates or timestamps. Cite source URLs from the event payload.
71
72	## Get / update / trigger / cancel
73
74	```bash
75	parallel-cli monitor get "$MONITOR_ID" --json
76	parallel-cli monitor update "$MONITOR_ID" --frequency 1w --json
77	parallel-cli monitor trigger "$MONITOR_ID" --json
78	parallel-cli monitor cancel "$MONITOR_ID" --json
79	```
80
81	The current CLI does not expose query updates; create a new monitor to change the query.
82
83	`trigger` enqueues a real off-schedule run without changing the regular schedule. It is not a synthetic webhook test, and it emits an event only if the run detects a material change.
84
85	Always confirm before cancelling — cancellation is permanent.
86
87	## Setup
88
89	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.

People who liked this also viewed

6 picks

Type

parallel-monitor

9.4kinstalls6forks

View on GitHub

How to install parallel-monitor?

parallel-web/parallel-agent-skills/parallel-monitor

$npx -y skills add parallel-web/parallel-agent-skills --skill parallel-monitor

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Web Monitor
2
3	Action: $ARGUMENTS
4
5	> 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 installation method (see <https://docs.parallel.ai/integrations/cli>), then retry.
6
7	## What this skill does
8
9	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.
10
11	## Decide the action
12
13	Parse the user's request and pick one:
14
15	\| Intent \| Action \|
16	\|---\|---\|
17	\| "Track / watch / monitor / alert me when X" \| create \|
18	\| "What am I monitoring?" / "List monitors" \| list \|
19	\| "What changed?" / "Show me events for monitor X" \| events \|
20	\| "Show monitor X" / "Get details for X" \| get \|
21	\| "Change cadence / webhook for X" \| update \|
22	\| "Check monitor X now" / "Run it now" \| trigger \|
23	\| "Show me the full payload for event group X" \| events with `--event-group-id` \|
24	\| "Stop / delete monitor X" \| cancel (always confirm before cancelling) \|
25
26	## Create a monitor
27
28	```bash
29	parallel-cli monitor create "<query>" --frequency 1d --json
30	```
31
32	Frequency accepts `<n><unit>` with `h`, `d`, or `w` (for example `1h`, `1d`, or `1w`). The aliases `hourly`, `daily`, `weekly`, and `every_two_weeks` are also accepted. Match cadence to how often the source actually changes — hourly for prices/news, weekly for filings/staffing.
33
34	Optional flags:
35
36	- `--webhook https://example.com/hook` — deliver detected events to a URL
37	- `--metadata '{"team":"competitive-intel"}'` — attach JSON metadata for your own bookkeeping
38	- `--output-schema '<json>'` — structure the event payload (advanced)
39
40	Parse the JSON to extract the `monitor_id`. Tell the user:
41
42	- The monitor has been created with its ID
43	- The frequency (so they know how often the monitor checks)
44	- That recent events are available server-side — they can run `parallel-cli monitor events $MONITOR_ID` later to see what changed
45
46	## List monitors
47
48	```bash
49	parallel-cli monitor list -n 10 --json
50	```
51
52	Default to `-n 10` for concise output. `list` returns active monitors only by default; add `--status active --status cancelled` when the user asks to include cancelled monitors. Raise the limit only for a larger set. Present as a table: ID, query or Task Run (truncated), frequency, created.
53
54	> Note: `monitor list` is sorted newest-first. If a user is verifying creation, prefer `monitor get $MONITOR_ID` (using the ID returned by create) over scanning the list.
55
56	## View events for a monitor
57
58	```bash
59	parallel-cli monitor events "$MONITOR_ID" --json
60	```
61
62	Events are returned newest-first. If the response contains `next_cursor`, pass it with `--cursor` to retrieve another page.
63
64	For deeper detail on a specific event group:
65
66	```bash
67	parallel-cli monitor events "$MONITOR_ID" --event-group-id "$EVENT_GROUP_ID" --json
68	```
69
70	Summarize for the user: count of events, then a bulleted list of what changed with dates or timestamps. Cite source URLs from the event payload.
71
72	## Get / update / trigger / cancel
73
74	```bash
75	parallel-cli monitor get "$MONITOR_ID" --json
76	parallel-cli monitor update "$MONITOR_ID" --frequency 1w --json
77	parallel-cli monitor trigger "$MONITOR_ID" --json
78	parallel-cli monitor cancel "$MONITOR_ID" --json
79	```
80
81	The current CLI does not expose query updates; create a new monitor to change the query.
82
83	`trigger` enqueues a real off-schedule run without changing the regular schedule. It is not a synthetic webhook test, and it emits an event only if the run detects a material change.
84
85	Always confirm before cancelling — cancellation is permanent.
86
87	## Setup
88
89	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.

People who liked this also viewed

6 picks

Type