Sites in the Woods

Teach your agent the job.

An agent skill is a short SKILL.md an agent loads when a request matches it: which calls to make, in what order, what each one changes, and when to stop and ask. These are ours, one per job.

sites-in-the-woods-status
Check whether a website that Sites in the Woods monitors in public is up, and see its recent outages, uptime and response times, from its public status page, data file and outage feed. Use when someone asks if one of these public sites is down, had an outage, or how reliable or fast it has been. Read-only, with no account or key. Not for a team's own private sites (use sites-in-the-woods-health with the team's key), and not for whether some other site or service is down (google.com, AWS, a site of your own): only sites on Sites in the Woods' public list.
sites-in-the-woods-connect
Set up an agent's access to a team's Sites in the Woods website monitoring: get an API key from the team's admin, keep it in an environment variable, add the hosted MCP server to Claude Code, Cursor or VS Code, and check the connection. Use when working with a team's Sites in the Woods monitoring for the first time, or when another Sites in the Woods skill can't reach its tools or gets a 401. Not for public status pages, which need no key (use sites-in-the-woods-status), and not for setting up other monitoring or alerting services (Pingdom, UptimeRobot, Datadog) or other MCP servers.
sites-in-the-woods-health
Find out what's wrong with a team's websites and why, using the team's Sites in the Woods API key or MCP server: what's down now, open incidents with their likely causes, uptime, and domains or TLS certificates about to expire; and, with a Member or Admin key, ask for a check again or dismiss an incident as noise. Use when a team that monitors its sites with Sites in the Woods asks whether their sites are OK, what broke and why, or when a domain or certificate it watches expires. Not for a domain or certificate question without a Sites in the Woods account (a registrar, a one-off SSL check), maintenance windows or pausing a site (use sites-in-the-woods-maintenance), or public sites without a key (use sites-in-the-woods-status).
sites-in-the-woods-maintenance
Hold a team's Sites in the Woods alerts during a deploy or planned work with a maintenance window, end it, or pause and resume a site's checks, using the team's API key or MCP server. Use when someone says they're deploying or doing maintenance and wants alerts held, wants alerts back on, or wants a site's monitoring paused or resumed. Not for reading what's wrong (use sites-in-the-woods-health).

Install one

Save a skill's file as <name>/SKILL.md in your agent's skills folder: ~/.claude/skills/ for Claude Code, or the one Codex, Cursor or your agent reads. Agents that read an index find all four at /.well-known/agent-skills/index.json, each with a digest of its file.

What they ask of an agent

The skills point at the live API docs and the MCP server rather than copying them, so they stay true as the API grows. To monitor sites of your own from your own machine, see the open-source agent-ready-uptime.

Last updated .