# Fitness Skill

> Personal fitness planning, live workout tracking with session support, auto-stale-session cleanup, Feishu-integrated reminders, and exportable training reports. Use when a user asks to create a workout plan, log exercises (real-time or after), track fitness progress, or manage gym/tennis schedules.

- Skill: `dvcrn/fitness-skill` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add dvcrn/fitness-skill`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/fitness-skill/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/dvcrn/fitness-skill

---


# Fitness Skill

Manage fitness plans, log workouts (real-time or one-shot), view history with token-efficient queries, and export full reports. Includes smart session lifecycle management with auto-close and proactive Claw check-ins.

## Quick Start

```bash
# Create a fitness plan
fitness-plan create --goals "muscle_gain,cardio" --sport_pref "gym,tennis" --frequency 4

# One-shot log (after workout)
fitness-log "gym: bench press 60kg x 8 x 3, squat 80kg x 5 x 4, 1.5 hours"

# Live session (during workout — log each exercise as you go)
fitness-log start gym
fitness-log "bench press 60kg x 8 x 3"
fitness-log "squat 80kg x 5 x 4"
fitness-log "felt great"
fitness-log end "good session overall"

# View status
fitness-status --week
fitness-status --month
fitness-status --export
```

## Commands

### fitness-plan

| Command | Description |
|---------|-------------|
| `fitness-plan init` | Interactive multi-turn Q&A to generate a plan |
| `fitness-plan create --goals ... --frequency N` | Non-interactive plan creation |
| `fitness-plan show` | Display the current plan (Markdown) |
| `fitness-plan update --frequency 4 --level advanced` | Modify an existing plan |
| `fitness-plan sync` | Push plan to Feishu doc |

### fitness-log

Two modes: **one-shot** (after workout) and **live session** (during workout).

| Command | Description |
|---------|-------------|
| `fitness-log "<text>"` | One-shot: parse and log a single workout entry |
| `fitness-log start [type]` | Start a live session (e.g. `start gym`) |
| `fitness-log "<exercise text>"` | Append exercise to active session |
| `fitness-log end ["notes"]` | End session, auto-calculate duration, commit to log |
| `fitness-log status` | Show active session info (includes idle/stale warnings) |

**Live session workflow:** The user sends messages during training. Each message is appended to the same session entry. When the user says "end", all exercises are merged into one log entry with auto-calculated duration (from start to end time).

### fitness-status

| Command | Description |
|---------|-------------|
| `fitness-status` | Last 7 entries (compact, token-efficient) |
| `fitness-status --week` | Weekly summary with stats |
| `fitness-status --month` | Monthly summary (last 30 days) |
| `fitness-status --days N` | Custom period summary |
| `fitness-status --all` | All entries (capped at 50, with truncation notice) |
| `fitness-status --export [N]` | Export last N days (default 30) as Markdown file |

## Session Lifecycle & Auto-Close

Sessions that are not explicitly ended are handled automatically:

| Condition | Behavior |
|-----------|----------|
| **Idle ≥ 30 min** | Claw proactively asks the user if training is done (via AGENTS.md rule). At most once per conversation to avoid nagging. |
| **Idle > 4 hours or next day** | Session is marked **stale** and auto-closed on the next fitness-related action. Duration is calculated up to the last message (not current time). |
| **Heartbeat detects stale session** | HEARTBEAT.md rule runs `fitness-log end` to force-close, and Claw notifies user on next interaction. |
| **New `start` while stale exists** | Old stale session is auto-closed first, then new one begins. |

This ensures no workout data is ever lost, even if the user forgets to say "end".

## Token Efficiency

- Default queries return compact summaries (7 entries or period stats) to minimize token usage.
- `--all` is capped at 50 entries with a truncation notice.
- For full history, use `--export` to generate a Markdown file that can be sent to the user directly, avoiding large inline output.

## Data Storage

- Plan: `~/.openclaw/workspace/fitness-skill/plan.json`
- Log: `~/.openclaw/workspace/fitness-skill/log.json`
- Active session: `~/.openclaw/workspace/fitness-skill/active_session.json` (auto-deleted on end)
- Exports: `~/.openclaw/workspace/fitness-skill/exports/`

## Feishu Integration

- Set `FEISHU_FITNESS_DOC_ID` to enable plan/log sync to a Feishu doc.
- `sync_plan_to_feishu()` — push plan Markdown
- `sync_log_to_feishu(days=30)` — push log report Markdown
- Daily reminders via `scheduler.add_cron_job()` at the user's configured time.