sites-in-the-woods-maintenance

Installation
SKILL.md

Hold alerts, or pause checks

First, check the connection

If you have the Sites in the Woods MCP tools, call status. Otherwise call GET /api/status with the key from $SITES_IN_THE_WOODS_API_KEY. If the tools are missing, the variable isn't set, or the answer is a 401, stop and follow the sites-in-the-woods-connect skill: don't guess a key and don't ask for one in chat.

Choose the lighter tool

  • A maintenance window (a Member or Admin key) holds the site's alerts; every check still runs and is recorded. It ends by itself after minutes (default 30, at most 24 hours), or when you end it. For a deploy, use this.
  • Pausing (an Admin key) stops every check of the site until it's resumed. Its history is kept, but nothing is checked or alerted in between, so an outage then goes unseen. Only when the person asks for monitoring to stop.

Both need a team with 10 sites or more.

Calls

  • Start a window: POST /api/sites/{slug}/maintenance/start with { "minutes": 45, "reason": "deploy" } (the reason is the team's own words and never public). Starting again replaces the open window.
  • End it: POST /api/sites/{slug}/maintenance/end. Alerts held during it are then sent, once, if the problem is still there.
  • Pause or resume: POST /api/sites/{slug}/pause, POST /api/sites/{slug}/resume.
  • See a site's windows: GET /api/sites/{slug}/maintenance.
Installs
1
First Seen
3 days ago