⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
oura
Oura Ring health data — sleep, readiness, activity, and stress
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
OuraClaw
Oura Ring plugin and skill for OpenClaw. Brings your sleep, readiness, activity, and stress data into your agent conversations.
Features
- Agent tool (
oura_data) — lets the agent fetch Oura Ring data on your behalf - Skill — teaches the agent how to interpret scores, format summaries, and answer health questions
- Scheduled summaries — optional morning and evening health recaps delivered to your preferred channel
- Background token refresh — keeps your Oura connection alive without manual intervention
Prerequisites
Installation
# From npm
npm install -g @rickybloomfield/ouraclaw
openclaw plugins install @rickybloomfield/ouraclaw
# Or from source
git clone https://github.com/rickybloomfield/OuraClaw.git
cd OuraClaw && npm install && npm run build
openclaw plugins install -l .
Setup
Run the interactive setup wizard:
openclaw ouraclaw setup
The wizard will walk you through:
-
Create an Oura application
- Go to https://developer.ouraring.com
- Navigate to "My Applications" and create a new app
- Set the redirect URI to
http://localhost:9876/callback
-
Enter credentials — paste your Client ID and Client Secret
-
Authorize — a browser window opens to complete the OAuth flow
-
Choose delivery channel — pick iMessage, Slack, Discord, Telegram, or use the default active channel
-
Set schedule — configure morning and evening summary times and timezone, or skip scheduled messages
Usage
Once set up, just ask your agent about your health data:
- "How did I sleep last night?"
- "What's my readiness score?"
- "How active was I today?"
- "Show me my sleep trends for the past week"
- "Give me a full health summary"
CLI Commands
openclaw ouraclaw setup # Run the setup wizard
openclaw ouraclaw status # Show connection status and config
openclaw ouraclaw test # Fetch today's data to verify the connection
Scheduled Summaries
If enabled during setup, OuraClaw creates two cron jobs:
- Morning (default 7:00 AM) — sleep score, readiness, stress, and a personalized note
- Evening (default 9:00 PM) — activity summary, readiness, stress, sleep recap, and a wind-down note
Manage them with:
openclaw cron list # See all cron jobs
openclaw cron run ouraclaw-morning --force # Manually trigger morning summary
Re-running openclaw ouraclaw setup replaces existing cron jobs without duplication.
Development
npm install
npm run build # Compile TypeScript
npm run dev # Watch mode
License
MIT
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/oura/SKILL.md7.8 KBupstream ↗
--- name: oura description: Oura Ring health data — sleep, readiness, activity, and stress gatedOn: plugins.entries.ouraclaw.config.accessToken --- # Oura Ring Health Data You have access to the user's Oura Ring data through the `oura_data` tool. Use it to answer health questions and deliver scheduled summaries. ## Endpoint Reference ### Core (used in daily summaries) | Endpoint | Returns | Key Fields | |----------|---------|------------| | `daily_sleep` | Sleep score & contributors | `score`, `contributors.deep_sleep`, `.efficiency`, `.rem_sleep`, `.restfulness`, `.total_sleep` | | `daily_readiness` | Readiness score & contributors | `score`, `contributors.hrv_balance`, `.resting_heart_rate`, `.recovery_index`, `.sleep_balance` | | `daily_activity` | Activity score & metrics | `score`, `steps`, `active_calories`, `total_calories`, `high_activity_time`, `medium_activity_time` | | `sleep` | Detailed sleep periods | `duration`, `total_sleep_duration`, `deep_sleep_duration`, `rem_sleep_duration`, `light_sleep_duration`, `efficiency`, `average_heart_rate`, `lowest_heart_rate`, `average_hrv`, `bedtime_start`, `bedtime_end` | | `daily_stress` | Stress summary | `stress_high`, `recovery_high`, `day_summary` | ### Additional (available for ad-hoc queries) | Endpoint | Returns | Key Fields | |----------|---------|------------| | `heartrate` | Continuous heart rate samples | `bpm`, `source`, `timestamp` | | `daily_spo2` | Blood oxygen levels | `spo2_percentage`, `breathing_disturbance_index` | | `workout` | Workout sessions | `activity`, `calories`, `duration`, `distance`, `intensity`, `start_datetime`, `end_datetime` | | `session` | Mindfulness/breathing sessions | `type`, `mood`, `duration`, `heart_rate`, `hrv` | | `enhanced_tag` | User-created tags | `tag_type_code`, `comment`, `timestamp` | | `daily_cardiovascular_age` | Cardiovascular age estimate | `vascular_age` | | `daily_resilience` | Resilience score & contributors | `level`, `contributors.sleep_recovery`, `.daytime_recovery`, `.stress` | | `vO2_max` | VO2 max estimate | `vo2_max`, `timestamp` | | `rest_mode_period` | Rest mode periods | `start_day`, `end_day`, `episodes` | | `sleep_time` | Recommended sleep times | `recommendation`, `status`, `ideal_bedtime_start`, `ideal_bedtime_end` | | `ring_configuration` | Ring hardware info | `color`, `design`, `firmware_version`, `hardware_type`, `set_up_at`, `size` | | `personal_info` | User profile | `age`, `weight`, `height`, `biological_sex`, `email` | | `tag` | Tags (deprecated, use `enhanced_tag`) | `tag_type_code`, `timestamp` | ## Usage Instructions - **Date defaults**: If no dates specified, the tool defaults to today's data. Use `start_date` and `end_date` in `YYYY-MM-DD` format for specific ranges. - **Multi-endpoint queries**: For comprehensive answers, call multiple endpoints. E.g., "How did I sleep?" should fetch both `daily_sleep` (score) and `sleep` (details). - **Duration conversion**: Sleep/activity durations are in **seconds**. Convert to hours and minutes: `27360s` → `7h 36m`. - **Null values**: Some fields may be `null` if Oura hasn't computed them yet. Note this gracefully rather than showing "null". ## Score Interpretation | Range | Label | |-------|-------| | 85+ | Excellent | | 70–84 | Good | | 60–69 | Fair | | Below 60 | Needs attention | ## Formatting Guidelines - Use concise bullet points, not long paragraphs - Lead with scores and labels (e.g., "Sleep: 82 (Good)") - Include 2–3 key contributor details per category - Convert all durations from seconds to Xh Ym format - Add brief, personalized context when relevant (e.g., "HRV is trending lower than usual") - Keep summaries scannable — the user may be reading on a phone - **Adapt formatting to the delivery channel** — see Channel Formatting Guide below ## Channel Formatting Guide Different messaging channels support different formatting syntax. Use the correct format for the delivery channel. When the channel is unknown or "default", use plain text formatting (safe everywhere). ### Plain text — iMessage (bluebubbles), Signal No text-based formatting syntax is supported. Characters like `*`, `_`, and `~` appear literally. - Use emoji and whitespace for visual structure - Use UPPERCASE sparingly for emphasis if needed (e.g., "SLEEP: 82") - URLs are auto-linked — just include them as plain text - Use `|` or `·` as inline separators - Use `—` (em dash) for inline breaks ### WhatsApp - **Bold**: `*text*` - **Italic**: `_text_` - **Strikethrough**: `~text~` - **Inline code**: `` `text` `` - **Lists**: `- item` at the start of a line - URLs are auto-linked — do NOT use markdown link syntax `[text](url)` ### Telegram Supports Markdown-style formatting: - **Bold**: `*text*` - **Italic**: `_text_` - **Underline**: `__text__` - **Strikethrough**: `~text~` - **Links**: `[display text](url)` - Escape special characters (`.`, `-`, `(`, `)`, `!`, etc.) with `\` when they appear outside formatting ### Slack Uses Slack's mrkdwn syntax (not standard Markdown): - **Bold**: `*text*` - **Italic**: `_text_` - **Strikethrough**: `~text~` - **Links**: `<url|display text>` - **Lists**: `- item` or `• item` - Do NOT use standard Markdown bold (`**text**`) or link syntax (`[text](url)`) ### Discord Uses standard Markdown: - **Bold**: `**text**` - **Italic**: `*text*` - **Underline**: `__text__` - **Strikethrough**: `~~text~~` - **Links**: `[display text](url)` - **Lists**: `- item` - **Headers**: `#`, `##`, `###` (at start of line) ### WebChat / Default Use standard Markdown formatting. ## Scheduled Summary Delivery When producing a scheduled summary (morning or evening), follow these rules: - **Read the template carefully** and follow every format rule, including all specified data points, line counts, and examples. - **Send the complete formatted summary as a single message** to the channel and target specified in the request. Do not summarize, abbreviate, or rephrase the summary. - **Apply channel-appropriate formatting** using the Channel Formatting Guide above based on the channel specified in the request. ## Morning Summary Template When delivering a morning summary, fetch `daily_sleep`, `sleep` (detailed periods), `daily_readiness`, `daily_activity`, and `daily_stress` for today. Also fetch yesterday's `daily_activity` as a fallback. Send only the formatted summary — no preamble, intro message, or extra commentary before or after it. Apply the correct formatting syntax for the delivery channel (see Channel Formatting Guide). Format rules: - Start with "Good morning!" and today's date - **Sleep**: score with label, total sleep time (convert seconds to Xh Ym), key contributors that are notably high or low. From the detailed `sleep` endpoint, include lowest resting heart rate, average overnight heart rate, and average HRV. Show deep, REM, and light durations in minutes. - **Readiness**: score with label, body temperature deviation, HRV balance, recovery index. Call out anything that's dragging the score down. - **Activity**: use today's `daily_activity` if available (score, steps, active calories). If score is null or data is missing, use yesterday's activity instead and note that it's yesterday's data. - **Stress**: mention if data is available (normal, high, etc.). If no stress data, skip it. - End with: "Dive deeper in the Oura app: https://cloud.ouraring.com/app/v1/home — enjoy your day!" (include trailing text after the URL so it renders inline, not as a separate link preview). - Keep it concise — 8–10 lines max. Use emoji sparingly. Warm but not cheesy. - Bold the category labels and scores on channels that support bold (e.g., `*Sleep: 82 (Good)*` on WhatsApp/Telegram/Slack, `**Sleep: 82 (Good)**` on Discord). On plain text channels (iMessage, Signal), do not use any formatting markers. Example tone (plain text / iMessage): ``` Good morning! Here's your recap for Monday, Jan 27. 😴 Sleep: 82 (Good) — 7h 12m total Deep 58m | REM 1h 24m | Light 4h 50m Lowest HREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/rickybloomfield-ouraclaw-skills-oura.md