How we make

mxa-monitor

Sets up operational monitoring so problems surface on their own after a project ships: errors, real-user performance, uptime and logging.

  • Wires error tracking, real-user performance, uptime and logging once, at ship time.
  • Turns a real signal into a tracked work item for a person to pick up, rather than acting on it alone.
  • Answers whether the site is broken, which is a different question from how it is used.

What it uses

Default

Sentry

Also uses

web-vitals or Vercel Speed Insights

Sentry for errors, the other for real-user performance.

Install it

Already on studio Claude accounts, in the Made by Agents plugin. Anyone else:

claude plugin marketplace add madebymany/madebyagentsclaude plugin install made-by-agents@madebymany

For Cursor, Codex and other agents, just this skill:

npx skills add madebymany/madebyagents --skill mxa-monitor
Read the skill itself