trainer-buddy-pro

• Outcome: Review
• Latest audit: May 29, 2026, 9:30 PM
• Version:
  1.0.0

Overview

The core trainer is coherent, but it stores sensitive fitness and injury data while bundled dashboard/cloud materials conflict with local-only privacy claims.

Review before installing if you care about privacy of workout, body, or injury data. Keep the core skill local, avoid enabling dashboard cloud sync unless you understand exactly what data will be uploaded, and ask the agent before it saves injury or limitation notes to your profile.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (7)

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The uninstall section instructs users to run a destructive `rm -rf` command without any explicit warning, path validation, or confirmation step. Even though the target path is relatively narrow, destructive shell commands in setup documentation can lead to accidental data loss if copied blindly, modified, or executed from an unexpected context.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The usage trigger is extremely broad, including 'anything related to fitness programming,' which could cause the skill to activate during ordinary conversation and process sensitive health or workout data unexpectedly. Over-broad activation increases the chance of unintended data access, profile mutation, or generation of workout advice in contexts where the user did not explicitly invoke the skill.

Missing User Warnings

Medium

• Confidence: 87% confidence
• Finding: The spec explicitly describes syncing workout and profile data to Supabase in a cloud mode, but it does not mention consent, privacy disclosures, or safeguards around transmission and storage of potentially sensitive health-related data. In a developer-facing build spec, this omission can lead implementers to ship external data transfer by default without user awareness, creating privacy and compliance risk.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The manifest clearly defines collection and storage of sensitive health-related data, including injuries, body metrics, and fitness profiles, but provides no user-facing disclosure about privacy practices, retention, sharing, or consent. In a fitness-tracking context, this omission increases privacy and compliance risk because users may not understand that sensitive wellness data is being stored and synchronized.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The skill states that it has updated the user's profile with a health-related note about back/form issues without warning the user that this information will be stored or obtaining clear consent. Because the note concerns physical condition and training limitations, this creates a privacy and transparency issue and can lead to unauthorized retention of sensitive wellness information.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The skill gives specific exercise selection, volume, and weight targets without any safety caveat, screening for injuries or limitations, or advice to stop if pain occurs. In a fitness context, prescriptive guidance can lead users to overexert, aggravate prior injuries, or use unsafe loads, especially when the agent infers progression from prior sessions.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The script automatically deletes older backup directories once more than 10 exist, with no confirmation, dry-run mode, or retention policy override. Although the deletion is scoped to the skill's backup directory and appears intended as routine housekeeping, it can still cause unintended data loss if users rely on older backups for recovery or auditing.

VirusTotal

65/65 vendors flagged this skill as clean.