Skip to content
TrustedSkillsbeta
Back to all skills

Status Page Monitoring

Listed
proxiblue·vlatest·devops

ProxiBlue's status-page-monitoring proactively alerts DevOps teams to incidents impacting service availability and performance.

Repository

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 proxiblue/claude-skills --skill status-page-monitoring -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

proxiblue

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: paypal-status.com, stats.uptimerobot.com.

    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.

    Hosts contacted

    stats.uptimerobot.comundeclaredpaypal-status.comundeclared

    What it found (3 of 6)

    • status-page-monitoring/SKILL.md:38contacts stats.uptimerobot.com
      curl -s "https://stats.uptimerobot.com/api/getMonitorList/Zk2EbUnM73" | jq -r '.psp.monitors[] | "\(.name): \(.statusClass)"' | sort
    • status-page-monitoring/SKILL.md:49contacts stats.uptimerobot.com
      curl -s "https://stats.uptimerobot.com/api/getMonitorList/Zk2EbUnM73" | jq -r '
    • status-page-monitoring/SKILL.md:58contacts stats.uptimerobot.com
      curl -s "https://stats.uptimerobot.com/api/getMonitorList/Zk2EbUnM73" | jq -r '.psp.monitors[] | select(.statusClass == "danger") | .name'

  • 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 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 proxiblue/claude-skills at 062e22b83c.

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

Commit
062e22b83c
Manifest
status-page-monitoring/SKILL.md
Scanned
1 file, 411 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 monitors status pages of various online services and reports on their current operational state. It can check for incidents, maintenance announcements, or general availability information directly from these status pages. The agent can then summarize this data to provide a quick overview of service health.

When to use it

  • Proactive Incident Response: Get notified when critical services you depend on experience outages before users report them.
  • Service Dependency Checks: Regularly verify the availability of third-party APIs or platforms your applications rely on.
  • Customer Support Triage: Quickly inform customers about known issues and estimated resolution times by checking official status pages.
  • Internal Reporting: Generate automated reports summarizing the health of key services for internal teams.

Key capabilities

  • Supports a variety of status page formats.
  • Provides summaries of current incidents.
  • Checks for maintenance announcements.
  • Reports on overall service availability.

Example prompts

  • "Check the status page for Atlassian."
  • "What's the current incident report for AWS?"
  • "Summarize any maintenance scheduled for Google Workspace."

Tips & gotchas

  • The skill requires a URL to the target status page. Ensure this URL is accurate and accessible.
  • Status page formats vary; some pages might be parsed more reliably than others.