What problem does it solve?
On-call engineers need a prioritized summary of new and escalating Sentry issues each morning, but manually querying Sentry, classifying issues, and writing a triage report is repetitive. This Skill sets up a server-side scheduled Claude Managed Agent that pulls the last 24 hours of Sentry issues with sentry-cli and writes a prioritized triage report, with the Sentry token held in a vault so the model never sees the secret.
Core Features & Use Cases
- Scheduled server-side triage: A cron deployment (weekday 9 AM Eastern) starts sandboxed sessions on Anthropic infrastructure with no host process running on your machine.
- Vault-based credential handling: The Sentry auth token is stored as an environment_variable vault credential; an egress proxy substitutes the real token only for allowlisted Sentry hosts, so the sandbox and model only ever see a placeholder.
- Full lifecycle scripts: setup_agent.py provisions the vault, credential, agent, and environment; deploy.py creates the cron deployment; run_now.py smoke-tests manually and downloads the report; update_agent.py pushes prompt or model changes and re-pins the deployment; runs.py shows run history; teardown.py archives everything.
- Use Case: An SRE team wants a morning report classifying issues as NEW, REGRESSION, ESCALATING, or ONGOING, ranked by user impact. After setup, the deployment produces TRIAGE_REPORT.md automatically every weekday.
Quick Start
Ask Claude to walk you through setting up the scheduled Sentry triage agent, starting with creating a Sentry auth token and running the setup script.