Most teams find out someone was burning out after it already happened. A Slack message that went unanswered for too long, a drop-off in output, a conversation that finally surfaced what had been building for weeks. Your assistant makes the signal visible earlier. It pulls Oura readiness data daily, reads it in the context of what the team has been carrying, and posts a morning energy report with trends and actionable notes — not just numbers.
Getting started
Each team member DMs their Oura personal access token to the assistant in Slack. It saves the token securely and confirms it is working. No forms, no admin portal — just a DM. Once the team is connected, the daily reports start automatically.
Hey — DM me your Oura personal access token and I'll connect you to the team energy report. Your data stays private. The report only shows your readiness score and trend direction, nothing else. I'll confirm once it's working.The daily report prompt
This runs every morning at 8:30 AM and posts to the team's Slack channel.
Pull today's Oura readiness score for each connected team member.
For each person:
- Readiness score (0-100)
- 7-day trend (improving, stable, declining)
- HRV and sleep score if readiness is below 60
Layer in work context:
- Is today a heavy meeting day?
- Is there a deadline or launch this week?
- Has this person posted fewer than usual in Slack the last 3 days?
Post the report to #oura-insights in this format:
- Team average and trend
- Anyone with a score below 60: flag with context and suggest a check-in
- Anyone with a 7-day declining trend below 40: escalate to manager with a private message
Keep the tone factual and supportive. No alarmism.How it works
The assistant calls the Oura API for each connected team member using their stored tokens. It reads readiness, HRV, sleep score, and contributors. It then cross-references with calendar data (heavy meeting days, upcoming launches) and recent Slack activity (message frequency, response latency) to add work context to each score.
The 7-day trend is what makes the system useful. A single bad score can be noise — a cold, a late night, travel. A declining trend over a week, compounded by a big deadline and reduced Slack activity, is a signal. When one team member's readiness trended into single digits during a crunch sprint, the assistant surfaced it before the manager had noticed anything was off. The check-in happened. The burnout did not.
Privacy by design
The public channel report shows readiness score and trend direction — nothing more specific. Detailed metrics (HRV, sleep stages, contributors) only surface in private messages, and only when a score is flagged. Each team member controls their own token and can disconnect at any time by DMing the assistant. The goal is visibility, not surveillance.
The outcome
The team's energy becomes a first-class signal alongside sprint velocity and ticket throughput. Managers stop finding out about burnout in retrospectives and start catching it three days before it would have derailed someone. The data is already there — your wearable collects it every night. Your assistant just makes it visible before it's too late.