Download for MacApple silicon, macOS 14+
Skill

uptime-monitors

@betterstackhq Updated 2026-10-23

Reference for Better Stack Uptime monitors and escalation policies — monitor types, valid configuration values, how escalation policies work, and the limits of what the monitor tools can do. Load before using create_monitor, create_heartbeat, monitors, monitor, escalation_policies or escalation_policy.

Install

With your agent

Install OMGSkills skill "betterstackhq/claude-plugin:skills/uptime-monitors" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/BetterStackHQ/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/uptime-monitors ~/.claude/skills/uptime-monitors

From README

Uptime monitors & escalation policies What the Uptime tools can do, the non-obvious rules, and where the limits are. A monitor is one Uptime check against a URL or host; when a check fails it opens an incident and alerts whoever the monitor's escalation policy routes it to. Tools at a glance monitors, monitor — read monitors. monitoravailability, monitorresponsetimes — a monitor's availability and response times, per region. createmonitor — create a monitor. createheartbeat — create a heartbeat (below). escalationpolicies, escalationpolicy — read escalation policies (who gets paged). Show the user what you are about to create and get a yes before calling a create tool: a new monitor starts checking, and alerting, right away. There is no update, pause/resume or delete tool. You can create and read monitors, but not edit one in place (change its URL, frequency, alerting, etc.), pause, resume or remove it. You can read escalation policies but not create/edit them.