What does this skill do, and when should you use it?
This skill, one of five in the peon-ping repository, focuses on logging exercise reps. Users can say 'did 25 pushups' or 'log 30 squats', and the skill invokes the peon.sh script to update daily counts and play a trainer voice line. It also supports checking status to see today's progress. As part of the larger peon-ping suite, it relies on the repository's installation, which places files in ~/.claude/hooks/peon-ping/ and requires the trainer feature to be enabled.
The skill reads the user-provided number and exercise type (pushups or squats), then runs bash ~/.claude/hooks/peon-ping/peon.sh trainer log <count> <exercise>. This command updates the count and plays a trainer voice line. When the user asks for progress, it also runs peon.sh trainer status to show today's progress. If the trainer is not enabled, it prompts the user to run /peon-ping-toggle or peon trainer on first.
- A developer wants to log pushups between coding sessions to stay healthy
- A user with Claude Code wants to log squats without leaving the conversation
- A user wants to check daily progress to see if they've met their goal
- A user needs a fun voice reminder to keep motivation, enhanced by trainer voice feedback
How do you install this skill?
- Skill depends on external scripts that may not have undergone security review.
- Permission scope and user confirmation mechanisms should be clarified.
- Shell / CLI
- Local filesystem
Bashpeon-ping installed
First install the entire peon-ping repository: on macOS/Linux, use Homebrew (brew install PeonPing/tap/peon-ping) or run curl -fsSL https://raw.githubusercontent.com/PeonPing/peon-ping/main/install.sh | bash; on Windows, use the installer script (Invoke-WebRequest -Uri ... -OutFile install.ps1 then run it). The installer copies the skill to the skills directory under ~/.claude/hooks/peon-ping/. Ensure the trainer is enabled (peon trainer on).
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/PeonPing/peon-ping.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/peon-ping-log" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- log 30 squats
In Claude Code, type /peon-ping-log 25 pushups or 'log 30 squats' to record. The skill calls the trainer log command, displaying the updated count and voice feedback. Later, ask 'what's my progress?' to trigger a status check.
What are this skill's strengths and limitations?
- Integrated into coding workflow without switching apps
- Provides voice feedback for fun
- Supports customizable daily goals via `peon trainer goal`
- Open source under MIT license
- Only supports pushups and squats, not other exercises
- Requires installing the whole repository (though local install option exists)
- Voice feedback depends on peon-ping's audio playback, which may need extra config on older Windows versions
- Lacks automated tests or documentation for maintenance states
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Peon Trainer Log this page | 54 · Use with care | ★ 5.1k | 5d ago | MIT |
| peon-ping Config Manager | 64 · Recommended | ★ 5.1k | 5d ago | MIT |
| CCM — Claude Code Manager | 55 · Use with care | ★ 29 | 2mo ago | MIT |
| Jetson BSP Info Check ✓ NVIDIA · Official | 59 · Recommended | ★ 3.5k | 3d ago | Apache-2.0 |
| Project Plugin Settings Pattern ✓ Anthropic · Official | 49 · Use with care | ★ 38k | 3d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill invokes local scripts, no network exfiltration, data flow transparent. However, permissions are not clearly specified, user confirmation mechanism is absent, affecting trust score.
Instructions are clear but depend on external scripts, no error handling provided, static assessment cannot fully verify.
Use case is clear but boundary conditions (e.g., invalid input) are not described, environment fit information is limited.
Basic documentation exists but version info, changelog missing, maintenance responsibility not clearly defined.
Skill can complete task but output format not specified, value evidence limited.
No reproducible test evidence provided, relies on single fact source.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →