monitoringlisted

# Monitoring Monitoring is an on-demand request, not a mandatory step. The agent helps the user check their app's health or set up basic monitoring. Keep it simple. ## If the user asks to check production health Do not set up anything. Just check what is available: 1. Read `.agents/skills/deploy-project/SKILL.md` to find the deployment URL. 2. If a URL exists: fetch it and check for a successful response. Report status, response time, and any obvious errors. 3. If no URL: ask the user for the URL. 4. If the app is down or returning errors, report what you see. Do not fix anything unless asked. ## If the user wants to set up monitoring Ask: **What do you want to monitor?** - Uptime (is the site alive?) - Errors (are there failures in logs?) - Performance (is it slow?) Then ask: **Do you already use a monitoring service?** (Sentry, UptimeRobot, BetterStack, etc.) - If yes: help them configure it for this project. Use the service's CLI or dashboard — never handle API keys directly. - If no: suggest the simplest free option based on what they want: | Need | Free option | What it does | |---|---|---| | Uptime | [UptimeRobot](https://uptimerobot.com) | Checks your URL every 5 minutes, sends email if down | | Uptime | [BetterStack](https://betterstack.com) | Uptime + status page, free tier | | Errors | [Sentry](https://sentry.io) | Error tracking, free tier for small projects | | Simple | A cron job + curl | `curl -f https://yourapp.com/health \|\| echo "DOWN"` — no extern