oura-ring-skill_skill

Overview

This skill fetches Oura Ring Readiness, Sleep, and 7-day readiness trends from the Oura Cloud API V2 and generates a concise Morning Readiness Brief. It provides a small, public reference implementation and CLI to pull raw JSON or a formatted morning summary. The goal is quick, actionable insights to guide daily recovery and performance decisions.

How this skill works

The skill calls Oura V2 endpoints under /v2/usercollection to retrieve the latest readiness and sleep records plus a seven-day trends window. It supports OAuth2 bearer tokens, accepts an environment file for configuration, and can run in mock mode for testing without a live token. Outputs include raw JSON for programmatic use and a formatted morning brief with tactical recommendations.

When to use it

• When you want a daily, automated readiness summary to guide training or workload.
• When integrating Oura readiness or sleep metrics into personal dashboards or automation.
• During development to prototype API access patterns and trend calculations.
• When you need a lightweight CLI to inspect readiness, sleep, or 7-day trends quickly.
• For offline testing using mock mode before connecting a live Oura account.

Best practices

• Store the OAuth2 access token and any refresh token in a local .env file and never commit it to source control.
• Use the provided mock mode for dry runs and CI validation to avoid rate limits or token expiry issues.
• Refresh access tokens as needed; implement token refresh using the returned refresh_token from Oura.
• Run the morning brief shortly after your normal wake time to capture the latest overnight data.
• Paginate trend requests when requesting long windows to avoid API timeouts or truncated responses.

Example use cases

• Generate a morning readiness brief for individualized training or meeting load decisions.
• Pipe raw readiness and sleep JSON into a personal dashboard or time-series database.
• Schedule a daily cron job to archive seven-day readiness trends for longitudinal analysis.
• Prototype integrations that combine Oura readiness with calendar or task systems.
• Validate Oura API connectivity and response shapes in development using mock mode.