Workout Tracker

v1.3.7

个人健身跟踪器 — 通过文字记录健身训练数据,自动解析动作、组数、次数和重量,实时写入本地 MySQL 数据库。支持制定专属训练计划、查询历史记录、追踪进步曲线,以及球类和有氧运动记录。

1· 98·1 current·1 all-time
byzenggang@query1988
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, required binaries (python3, mysql), required env vars (MYSQL_*), and included scripts (init_database.py, verify_setup.py) all align with a local MySQL-based fitness tracker. Required items are expected for the stated purpose.
Instruction Scope
SKILL.md instructs installing a Python MySQL connector, configuring local env vars/.env, creating a minimal-privilege DB user, running the init and verify scripts. The runtime instructions and scripts only read local config (.workout-tracker.env) and access the local MySQL socket; they do not call external endpoints or request unrelated system data.
Install Mechanism
No automated install download or remote-executable install spec is present (instruction-only); scripts are plain Python files included in the package. The only third-party dependency is mysql-connector-python installed via pip as instructed — proportionate to the task.
Credentials
Requested environment variables are limited to MYSQL_SOCKET, MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE and match the service the skill uses. The scripts only reference those vars (and defaults) and do not ask for unrelated secrets or credentials.
Persistence & Privilege
Skill is not forced-always, does not request system-wide privileges, and does not modify other skills' configs. It can be invoked autonomously (platform default) — appropriate for a local helper that writes to a database, but consider user policy if you want to avoid autonomous DB writes.
Assessment
This skill appears internally consistent with a local MySQL workout tracker, but take these precautions before installing: 1) Review the included scripts (init_database.py, verify_setup.py) yourself — they are small and only use the declared MYSQL_* vars, but confirm no surprises. 2) Create and use a dedicated local MySQL user with minimal privileges (INSERT/SELECT/UPDATE/DELETE) and do NOT use production or admin DB credentials. 3) Keep the .workout-tracker.env file permission-restricted (chmod 600) and do not commit it to version control; verify how the scripts parse values (they read raw values and will include quotes if present). 4) Run the init/verify steps in an isolated/dev environment or container first to confirm behavior. 5) If you do not want the agent to write to your local DB without prompts, consider disabling or limiting autonomous invocation in your agent policy. 6) Because the package source is unknown, prefer to run it locally from a vetted copy or audit the repository before granting access to any sensitive systems.

Like a lobster shell, security has layers — review code before you run it.

fitnessvk971qnknya4hsa3s79z6zhhrh983yh3mgymvk971qnknya4hsa3s79z6zhhrh983yh3mhealthvk971qnknya4hsa3s79z6zhhrh983yh3mlatestvk979sqwt27bjcjzhsfegn1mndh8444qgpersonal-trainervk971qnknya4hsa3s79z6zhhrh983yh3mstrengthvk971qnknya4hsa3s79z6zhhrh983yh3mworkoutvk971qnknya4hsa3s79z6zhhrh983yh3m

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🏋️ Clawdis
Binspython3, mysql
EnvMYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE, MYSQL_SOCKET
Primary envMYSQL_PASSWORD

Comments