Oura Cli

Retrieve health and biometric data from your Oura Ring via CLI commands for sleep, activity, readiness, heart rate, and more using specified dates.

What to consider before installing or running this skill: - The bundled code is a normal Oura CLI: it uses OAuth and will store your Client ID/Secret and tokens in ~/.config/oura-cli/config.json. If you run it, expect local persistent storage of credentials and tokens. - The registry metadata omitted required env vars and an install/build step. Before running any binary, either build the included source locally (go build ./cmd/oura) or inspect the code yourself. Do not run an unreviewed prebuilt binary. - The auth flow starts a temporary HTTP server on localhost:8080 to receive the OAuth callback; that can interfere with existing services using that port. If you do authentication, prefer creating a dedicated Oura app with minimal scopes and revoke the app afterwards if you don't trust it. - If you only want agent-driven answers (without giving real credentials), avoid providing your production Oura client secret. Consider testing with a throwaway account or running the CLI in an isolated environment (container or VM). - The mismatches (no declared env vars, no install steps) are likely sloppy metadata rather than malicious intent, but they reduce transparency. If you plan to use this skill, inspect the source files provided and confirm you are comfortable with the local config behavior and OAuth scopes before proceeding.

Type: OpenClaw Skill Name: oura-cli Version: 1.0.0 The skill is classified as suspicious due to a vulnerability in how OAuth tokens are stored. The `internal/config/config.go` file uses `os.Create` to save `config.json`, which by default creates files with world-readable permissions (e.g., 0644 on most systems after umask). This allows other local users on the same system to read the `AccessToken` and `RefreshToken`, potentially leading to unauthorized access to the user's Oura data. While the core functionality is benign and the prompt injection instructions in `SKILL.md` are for legitimate tool usage, this information disclosure vulnerability is a significant security flaw.