v1.0.8

Garmin Connect Health

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 7:29 AM.

Analysis

This skill coherently fetches Garmin health data as described, but it requires Garmin credentials, caches tokens, and stores sensitive health data locally.

GuidanceInstall this only if you are comfortable giving it access to your Garmin Connect account and storing Garmin health snapshots on your machine. Prefer Keychain or environment-variable authentication, avoid command-line passwords, protect the local data/token directories, and consider pinning the `garminconnect` dependency.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

skill.json

"dependencies": {
  "python": ">=3.10",
  "pip": [
    "garminconnect"
  ]
}

The external Python dependency is not version-pinned. It is central to the skill's purpose, but users are trusting the currently installed package version.

User impactA future or compromised dependency version could affect how Garmin credentials and health data are handled.

RecommendationInstall dependencies from a trusted environment and consider pinning or reviewing a known-good `garminconnect` version before use.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusNote

SKILL.md

export GARMIN_EMAIL="you@example.com"
export GARMIN_PASSWORD="yourpassword" ... `~/.garminconnect/` -- OAuth token cache

The skill uses the user's Garmin account credentials and cached OAuth tokens to authenticate to Garmin Connect. This is expected for the stated integration and is disclosed, but it grants access to account health data.

User impactAfter setup, the skill can access Garmin Connect data associated with your account, and anyone who obtains the password or token cache could potentially access that data.

RecommendationUse macOS Keychain or protected environment variables, avoid passing passwords on the command line, and remove or revoke cached tokens if you stop using the skill.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning

SeverityMediumConfidenceHighStatusNote

SKILL.md

`~/.garmin_health/YYYY-MM-DD.json` -- Daily snapshots
`~/.garmin_health/latest.json` -- Most recent fetch
`~/.garminconnect/` -- OAuth token cache

The skill persists sensitive health snapshots and session material locally so future runs and agent queries can reuse them.

User impactYour sleep, heart rate, HRV, stress, activity, and other health metrics may remain on disk and may be available to future agent interactions or local users with file access.

RecommendationKeep the data and token directories private, consider using custom protected paths via `GARMIN_DATA_DIR` and `GARMIN_TOKENSTORE`, and delete stored snapshots or tokens when no longer needed.