Calorie Tracker
v1.0.1Track calories and macros conversationally. Auto-adapts to your goals and style.
⭐ 2· 980·1 current·1 all-time
byIván@ivangdavila
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 and macro tracking, adaptive to goals) align with the instructions and supporting docs: photo-first estimation, text fallback, goal adaptation, and a personal library. No unexpected credentials, binaries, or cloud-host references are required.
Instruction Scope
The runtime instructions direct the agent to ask for photos/text, estimate calories, and save user-specific data (library, preferences, targets). This is within scope for a tracker, but the skill explicitly says it will 'build library silently' and persist label scans and repeat meals — meaning it will store potentially sensitive user-provided images/text locally. There is no instruction to transmit data off-device, nor to read unrelated system files, but the privacy implications of saving images/labels are worth noting.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is downloaded or written to disk by an installer. Risk from installation mechanism is minimal.
Credentials
The skill requests no environment variables, credentials, or external config paths. The lack of required secrets is proportional to the stated purpose.
Persistence & Privilege
The skill requests permission to create and maintain a local memory file at ~/calories/memory.md and to cache/retain label scans and saved recipes. This is reasonable for functionality, but it does grant persistent local storage of user-provided images and logs — users should be aware that data will be stored on disk and persists across updates ('Preferences now persist across skill updates').
Assessment
This skill appears coherent and does what it says, but before installing consider: (1) it will create and maintain a local file at ~/calories/memory.md and cache images/label scans — review where your platform stores that file and who can access it; (2) photos can contain sensitive metadata (location, faces) and the skill does not mention stripping EXIF or encrypting data; (3) it explicitly avoids tracking for contraindicated populations (pregnancy, eating disorders, diabetes) — do not use it for clinical care; (4) if you are concerned about privacy, test with non-sensitive example entries, periodically review or delete ~/calories/memory.md, and confirm your platform’s image-handling/privacy policies. Overall the skill is internally consistent, not requesting unrelated privileges or external credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk9705cxj3mvnzx1aztw02396cn817mhr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.