Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
wger OpenClaw Fitness Skill
v1.0.0Manage gym routines, log workouts, track nutrition, update goals, and generate fitness reports via the wger API integrated with OpenClaw automation.
⭐ 0· 17·0 current·0 all-time
byjaspreet@0xjaspreet
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description match the included scripts and curl examples (wger API usage). However the registry metadata does not declare the WGER_TOKEN env var that the SKILL.md and both scripts require, and some workflows in SKILL.md reference scripts/assets (generate_report.py, set_goal.py, assets/progress_template.html, references/nutrition.md) that are not present in the file manifest — this inconsistency undermines trust in the declared purpose.
Instruction Scope
SKILL.md instructs the agent to run curl commands and to run/read bundled Python scripts (create_log.py, view_logs.py). Those commands are appropriate for a wger client, but the instructions also reference missing files and additional scripts/subagents not provided. The SKILL.md tells the agent to use 'exec curl' (shell execution) and to parse/POST data; that is expected for an API client but gives the agent authority to run shell commands and use the WGER_TOKEN. No instructions request unrelated system files, but the presence of exec usage means operators should verify there are no hidden commands in omitted referenced scripts.
Install Mechanism
Instruction-only skill with no install spec — nothing is downloaded or written during installation. This is the lower-risk installation model.
Credentials
Both scripts require the WGER_TOKEN env var at runtime, yet the registry lists no required env vars or primary credential. The skill also uses the Python 'requests' library but does not declare dependencies. Asking for the user's wger API token is proportionate to the stated purpose, but the missing declarations and undeclared dependency are coherence/maintenance issues and risk runtime failure or secret mishandling if the agent logs shell output.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges. It suggests cron/subagent integration for automation (normal for this class of skill).
What to consider before installing
This skill appears to be an API client for wger, but there are several inconsistencies you should address before installing or providing any credentials:
- Do not supply your WGER_TOKEN until you're comfortable: both Python scripts and the SKILL.md require WGER_TOKEN, but the registry metadata did not declare it. That mismatch could be an oversight, but confirm the skill owner intentionally requires the token.
- Verify missing/mentioned files: SKILL.md references generate_report.py, set_goal.py, references/nutrition.md, and an assets HTML template that are not in the package. Ask the publisher for the complete source or an updated manifest; missing files could mean incomplete/broken behavior or omitted functionality.
- Confirm dependencies/environment: The bundled scripts use the 'requests' Python library but the skill declares no dependencies. Ensure your runtime has the required Python packages before running, or run the scripts in an isolated environment.
- Review what will be executed: SKILL.md instructs running curl and Python scripts. Inspect every script you execute locally (create_log.py, view_logs.py) and any additional scripts the author provides to ensure they only call the wger API and do not transmit data to other endpoints.
- Protect the token: Treat WGER_TOKEN as a secret. Prefer scoping the token to least privilege, use a throwaway/test account for initial testing, and avoid pasting it into logs or public channels. Consider self-hosting wger if you need stronger privacy (selfhost.md includes an example Docker compose with weak defaults — change passwords and avoid exposing ports publicly).
If the publisher cannot explain or fix the missing declarations and files, consider the skill suspicious and avoid providing real credentials or enabling automated invocation until the issues are resolved.Like a lobster shell, security has layers — review code before you run it.
latestvk977be4377zdpddjg7ddpdefn584w4gw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
