Fitness Support
v1.0.0Personal fitness coach specializing in home workouts with 2 dumbbells for muscle building. Provides workout design, progressive overload tracking, form coach...
⭐ 0· 382·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (home dumbbell hypertrophy coach) match the provided instructions and files. The skill requires no binaries, env vars, or external installs and the guidance focuses on workouts, tracking, form, and recovery — all consistent with the purpose.
Instruction Scope
SKILL.md and AGENT.md instructions are appropriately scoped to workout design, tracking, and form guidance. The skill explicitly says it will 'maintain a memory file' and a MEMORY.md is shipped containing a sample client profile (including a personal name and location). Storing user fitness and lifestyle data is expected, but the presence of prefilled personal data ("Kavinda") is noteworthy and should be reviewed/edited before use.
Install Mechanism
No install spec, no downloaded code, and no code files to execute. Being instruction-only means the skill does not write or execute additional binaries on install.
Credentials
The skill requests no environment variables, credentials, or config paths. This is proportionate to a fitness-coach skill.
Persistence & Privilege
The skill is not marked always:true and uses the platform default allowing autonomous invocation. It also explicitly uses a memory file to persist user profile, workout history, and PRs: this is functional for a coaching skill but means personal or health-related data will be stored — review retention and contents before enabling long-term use.
Assessment
This skill appears coherent and low-risk, but take these steps before installing/using it: 1) Open MEMORY.md and AGENT.md and remove or replace any sample personal data (e.g., the name 'Kavinda') with anonymized or intentionally provided values. 2) Decide whether you are comfortable with the skill persisting workout/history/nutrition information and adjust or clear memory if you do not want long-term storage. 3) Because the skill owner is unknown and it's instruction-only, prefer using it with non-sensitive test inputs first (no private medical data). 4) If you do not want autonomous runs that may read/write memory, restrict invocation or disable the skill when not actively using it. 5) If you plan to share health details, consider whether local storage or export controls are available and appropriate.Like a lobster shell, security has layers — review code before you run it.
latestvk97dfet4s514d5krgwhe3f21e18231df
License
MIT-0
Free to use, modify, and redistribute. No attribution required.