Garmin Connect Sync (国际→国内)

• Outcome: Review
• Latest audit: May 29, 2026, 3:25 AM
• Version:
  2.0.0

Overview

This Garmin sync skill appears purpose-aligned, but it handles sensitive account and fitness data without enough clear privacy and activation boundaries.

Install only if you are comfortable giving the agent access to Garmin credentials or tokens and personal fitness history. Before first use, confirm exactly which accounts are accessed, where FIT files or tokens are stored, how to delete cached data, and require explicit confirmation before any download, upload, or cross-account sync.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The trigger set is broad and generic for common topics like Garmin, syncing, and watches, which can cause the skill to activate in unrelated conversations. In this skill's context, unintended invocation is more dangerous because activation may expose account-linked operations involving fitness data transfer and credential-backed actions.

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The skill lacks a prominent privacy and security warning despite processing usernames, passwords, OAuth tokens, activity history, and locally cached FIT files. Because it transfers personal fitness records between accounts and stores artifacts on disk, users may underestimate the sensitivity of the operation and the risk of credential or health-data exposure.

VirusTotal

64/64 vendors flagged this skill as clean.