sites-in-the-woods-health
Installation
SKILL.md
What's wrong with our sites, and why
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.
Reading
- Start with
status(MCP) orGET /api/status: every site and every open incident, right now. - Why something broke:
incidents/GET /api/incidentsgives each incident's likely cause and evidence. Report the cause in your own words, with the evidence. - One site's week:
sites_by_slug/GET /api/sites/{slug}. - Uptime:
sites/GET /api/sites(1, 7 and 30 days). - Expiry:
domains/GET /api/domains(domain registrations and TLS certificates, with days left). - Follow each answer's
next_steps: they name the next call (and its MCP tool).
Changing things
With a Member or Admin key, on a team with 10 sites or more: