Parallel Monitor
PassAudited by ClawScan on May 7, 2026.
Overview
This skill appears to do what it says, but users should notice that it uses an authenticated Parallel CLI to create persistent web monitors and can optionally send events to webhooks.
Install this only if you intend to let the agent manage Parallel monitors through your authenticated Parallel CLI. Check the account being used, choose the slowest useful cadence, use trusted webhook URLs, and keep the monitor_id so you can update or delete monitors later.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the CLI is already logged in, the agent can use that account to create, update, list, delete, and simulate Parallel monitors when following this skill.
The skill relies on an authenticated Parallel CLI session to manage monitors in the user's Parallel account, although the registry metadata declares no primary credential or required binary.
Requires `parallel-cli` (installed and authenticated).
Confirm the Parallel CLI is authenticated to the intended account and workspace before using the skill, and consider declaring the CLI/auth requirement in metadata.
A monitor may keep running and producing events until the user updates or deletes it.
The skill creates monitors that continue running on a schedule after initial setup. This persistence is the stated purpose and is disclosed, but it is important for users to notice.
Recurring research that should re-run automatically without re-prompting
Only create monitors the user explicitly wants, record the monitor_id, and use the documented delete command when monitoring is no longer needed.
Monitor event data could be delivered to whatever webhook endpoint is configured.
The skill supports sending monitor events to an external webhook URL. This is optional and purpose-aligned, but monitor outputs and objectives may leave the Parallel environment.
`--webhook <url>` | Webhook URL for event delivery
Use only trusted webhook URLs, avoid embedding secrets in URLs when possible, and make sure the user understands what data will be sent.
The behavior and security of the actual CLI depend on the user's installed parallel-cli package, which is outside this skill artifact.
The skill depends on an external CLI that is not installed or pinned by this artifact. The instruction tells the agent to stop rather than install arbitrary code, so this is a disclosure/provenance note rather than a concern.
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.
Install or update parallel-cli only from official Parallel documentation and verify it before authenticating.