Calorie Counter
v1.0.0Track daily calorie and protein intake, set goals, and log weight. Use when user mentions food they ate, wants to know remaining calories, or needs to track weight. Stores data in SQLite with automatic daily totals.
⭐ 1· 2k·3 current·3 all-time
by@cnqso
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (calorie & weight tracking) match the included Python script and README/SKILL.md. The skill requires only Python and uses a local SQLite DB in the skill workspace; nothing requested or included is unrelated to its stated purpose.
Instruction Scope
SKILL.md explicitly instructs the agent to run the included script from workspace/calorie-counter and to read/write the local SQLite DB. All referenced files, commands, and data (add, summary, goal, weight, delete, history) are directly relevant. The only non-functional autonomy is that the agent is asked to estimate protein when not provided — this is a behavioral/accuracy choice, not a security concern.
Install Mechanism
No install spec is provided (instruction-only with a bundled script). No external downloads, package installs, or archive extraction are present. The code is local and uses only the Python standard library and SQLite.
Credentials
The skill requests no environment variables, credentials, or config paths. The metadata notes Python>=3.7 which is reasonable. There are no unrelated or excessive permissions requested.
Persistence & Privilege
always:false and no install hooks or modifications to other skills are present. The skill persists data only to its own local SQLite file under the workspace (calorie_data.db). Agent autonomous invocation is allowed by default but is not disproportionate here.
Assessment
This skill appears to be a simple local calorie/protein tracker that stores data in workspace/calorie-counter/calorie_data.db. Before installing, consider: 1) Privacy — the DB is stored unencrypted in your workspace and could be included in backups or accessed by other processes/users with access to that path. 2) Permissions — verify the workspace location is appropriate and restrict file permissions if needed. 3) Autonomy — the agent may auto-run the script when you mention food; if you want manual control, disable autonomous invocation or limit when the skill can run. 4) Code review — although the script appears benign (no networking, no exec of arbitrary shell commands, parameterized SQL), you may still inspect scripts/calorie_tracker.py yourself. If you need encrypted storage, remote sync, or integration with other services, expect to add explicit, audited code and credentials for those services.Like a lobster shell, security has layers — review code before you run it.
latestvk97axt0ac5j0g24eqv16812fen80kw1q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🍎 Clawdis