Gym

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Security Scan

This is an instruction-only fitness logging/coaching skill that only reads/writes files under ~/gym and requests no external credentials or installs—its behavior is coherent with its stated purpose.

Purpose & Capability

Name/description (log workouts, plan routines, track progress, coach) align with the content of the provided files. The skill requires no external services, binaries, or credentials, which is consistent with a local workout-tracking and coaching tool.

Instruction Scope

SKILL.md and the included documents instruct the agent to create and persist user preferences and data in files beneath ~/gym (memory.md, workouts.md, prs.md, measurements.md). This is within the scope of a local fitness tracker, but users should be aware that personal workout and measurement data will be written to their home directory. The instructions do not attempt to read other system config, secrets, or contact external endpoints.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk model for install behavior — nothing is downloaded or executed beyond the platform's normal agent actions.

Credentials

The skill requires no environment variables, credentials, or special config paths. No secrets or unrelated credentials are requested, which is proportionate to its purpose.

Persistence & Privilege

always:false (default). The skill persists its own data under ~/gym as described, and does not request system-wide changes or alter other skills. The skill may be invoked by the agent (platform default), which is normal and not in itself a concern.

Assessment

This skill appears to be what it says: a local workout planner and logger. Before installing, note that it will create and update files in ~/gym (memory.md, workouts.md, prs.md, measurements.md) containing your workout logs, measurements, and preferences. If you are uncomfortable with local storage of personal fitness data, do not install or plan to delete/secure those files after use. There are no network endpoints, credentials, or installers requested by the skill. If you want cloud sync or third-party integrations, verify how and where that would be added (those are not present here).

Quick Reference

Topic	File
Routines, exercises, templates	workouts.md
Progress tracking, volume, PRs	progress.md
Injury adaptation, modifications	adaptation.md
Gym nutrition, macros, timing	nutrition.md

User Profile

User preferences persist in ~/gym/memory.md. Create on first use:

## Level
<!-- beginner | intermediate | advanced -->

## Goals
<!-- strength | hypertrophy | fat-loss | general-fitness | powerlifting -->

## Schedule
<!-- Days available. Format: "days | frequency" -->
<!-- Examples: Mon/Wed/Fri, 3x/week, daily -->

## Session Duration
<!-- 45min | 60min | 90min -->

## Restrictions
<!-- Injuries, equipment limits, mobility issues -->
<!-- Examples: Lower back injury (no deadlifts), Home gym (no cable machine) -->

Fill on first conversation. Update as goals evolve.

Data Storage

Store workout logs and measurements in ~/gym/:

• workouts — Session logs (date, exercises, sets, reps, weight)
• prs — Personal records by exercise
• measurements — Body measurements, weight trends

Core Rules

• Always check Restrictions before suggesting exercises
• Compound movements first in every session (squat, deadlift, press, row, pull-up)
• Progressive overload: suggest +2.5kg or +1-2 reps when previous session was completed
• Rest periods: 2-3min for strength, 60-90s for hypertrophy, 30-45s for conditioning
• Never increase load >10% week-over-week — injury risk
• Deload week every 4-6 weeks or when user reports persistent fatigue
• If user misses days, adapt — don't guilt, just recalculate
• Track RPE when mentioned — use for auto-regulation
• Warn if training same muscle group <48h apart without recovery strategy