Skip to content
TrustedSkillsbeta
Back to all skills

Status

Checked
parallel-web·vlatest·other·MIT

Checks the online status of multiple websites simultaneously, reporting any outages or errors quickly.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add parallel-web/parallel-agent-skills --skill status -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

parallel-web

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned parallel-web/parallel-agent-skills at 8fc1fc426e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 18 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to monitor and report the operational status of web services or specific endpoints. It provides real-time visibility into whether a target URL is responding correctly, helping agents verify connectivity before attempting complex tasks like data extraction or form submission.

When to use it

  • Verify that a third-party API or website is online before initiating a scraping workflow.
  • Check the health of internal microservices during automated deployment pipelines.
  • Confirm email server availability before sending bulk notifications.
  • Diagnose intermittent connectivity issues by polling specific status pages repeatedly.

Key capabilities

  • Checks HTTP response codes for specified URLs to determine success or failure.
  • Reports detailed status information including latency and error messages.
  • Supports continuous monitoring intervals for persistent uptime tracking.

Example prompts

  • "Check if the payment gateway at https://api.example.com/pay is currently responding with a 200 OK status."
  • "Monitor the status of our internal dashboard endpoint every minute and alert me if it goes down."
  • "Before starting the data migration, verify that the target database server URL is accessible and online."

Tips & gotchas

Ensure the target URLs are publicly accessible or properly configured to allow external health checks from your agent's execution environment. For high-frequency monitoring, be mindful of rate limits imposed by the target servers to avoid triggering security blocks.