Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent local workout logging skill, with practical cautions around its external npm CLI and no-confirmation local delete/edit features.
Install only if you are comfortable using the global npm package it depends on and storing workout records in ~/.workout-claw. Treat delete/edit requests carefully, especially because delete is non-interactive and may not be reversible. Broad trigger phrases may need clarification before the agent acts.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
For OpenClaw integration:
mkdir -p ~/.openclaw/workspace/skills/workout-claw
cp SKILL.md ~/.openclaw/workspace/skills/workout-claw/SKILL.md
systemctl --user restart openclaw-gateway.service
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
mkdir -p ~/.openclaw/workspace/skills/workout-claw
cp SKILL.md ~/.openclaw/workspace/skills/workout-claw/SKILL.md
systemctl --user restart openclaw-gateway.service
The README advertises workout-claw delete <session-id> but does not warn that this removes workout data or indicate whether deletion is reversible. For a markdown file, destructive behavior affecting user data should be accompanied by an explicit warning so users and invoking agents understand the risk.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
By default the session's muscle group is inferred from the exercises you logged (most sets wins). If you follow a fixed split, create ~/.workout-claw/config.json:
{ "split": { "mon": "back", "wed": "legs", "fri": "chest" } }
Shadow Command Trigger: 'log workout' conflicts with built-in command 'log'
Shadow Command Trigger: 'delete workout' conflicts with built-in command 'delete'
Shadow Command Trigger: 'edit workout' conflicts with built-in command 'edit'
The listed triggers include generic phrases like "today's workout", "last workout", and "show last session", which can plausibly occur in ordinary conversation and may collide with other fitness, calendar, or note-taking contexts. The manifest does not provide exclusion conditions or tighter scope constraints to distinguish when this skill should or should not activate.
Triggers such as "back volume", "chest volume", "how much volume", and "weekly volume" are broad fragments that could refer to audio, storage, anatomy, or other domains, not necessarily workout training volume. Without contextual qualifiers or negative examples, these phrases risk unintended invocation.
The skill exposes a destructive delete operation with no confirmation prompt and explicitly instructs agents to use it non-interactively. In an agent setting, a mistaken trigger, stale session ID, or ambiguous user request could permanently remove workout data without an opportunity for the user to approve or recover the action.
workout-claw delete
Session IDs come from the `id` field in any `log` / `summary` / `last` output. No confirmation prompt — the CLI is non-interactive by design.
### Edit a session
The README states that workout-claw edit <session-id> opens session JSON in $EDITOR, which allows direct modification of persisted workout records. Although not inherently unsafe, the markdown description lacks any warning that users can alter or corrupt stored data if they edit the JSON incorrectly.