calorie-tracker

name	Calorie Tracker
slug	calories
version	1.0.3
changelog	Full coverage pass: deeper guides, situation-named files, and per-user configuration
description	Tracks calories, macros, and weight trends from meal photos, text logs, and nutrition labels. Use when the user logs a meal or a drink, keeps a food diary, asks how many calories something has, wants a calorie or protein target for a cut, bulk, deficit, or maintenance, asks for their TDEE or maintenance calories, counts macros or carbs, reads a food label, asks whether to eat back exercise calories or workout burn, or asks why the scale is stuck, why they are not losing weight, or why it jumped overnight. Covers TDEE calibration from the user's own logs, restaurant, alcohol, and cheat-day estimates, plateaus and water weight, smart-scale body-fat readings, GLP-1 and medical guardrails, and eating disorder safety. Not for meal planning or recipes.
homepage	https://clawic.com/skills/calories
metadata	{"clawdbot":{"displayName":"Calorie Tracker","emoji":"🍎","configPaths":["~/Clawic/data/calories/","~/calories/","~/clawic/calories/"]},"openclaw":{"requires":{"config":"[Truncated]"}}}

User preferences, memory, and the food library live in ~/Clawic/data/calories/ (see setup.md on first use, memory-template.md for the file formats). If you have data at an old location (~/calories/ or ~/clawic/calories/), move it to ~/Clawic/data/calories/, and say in one line that you moved it and from where.

Configuration

User-dependent variables. Defaults apply until the user states a preference; store them in ~/Clawic/data/calories/config.yaml.

Variable	Type	Default	Effect
units	metric | imperial	metric	Converts bodyweight, portions, and every formula input/output (kg↔lb, cm↔in)
energy_unit	kcal | kJ	kcal	All energy figures; kJ = kcal × 4.184 (labels.md for kJ-labeled countries)
summary_cadence	per_meal | daily | weekly | none	per_meal	When running totals are reported back to the user
clarify_style	ask_once | assume	ask_once	Ask the single clarifying question, or estimate silently and state the assumption that moves the number most

Preference areas to record as the user reveals them:

• logging medium — photo-first, text-first, or label-first; affects which path in estimation.md opens by default
• goal style — casual logging vs coached (weekly trend reviews, proactive check-ins); affects prompting intensity everywhere
• food conventions — home cuisine, staple dishes, recurring restaurants; affects portion defaults and library seeding
• data of record — an external tracker the user also logs in; affects whether totals mirror its database entries or this skill's estimates
• restrictions — vegetarian/vegan, allergies, religious rules; affects protein-source assumptions and meal defaults
• weigh-in ritual — scale owned or not, daily vs 3-4×/week tolerance, cycle-aligned comparisons; affects the protocol and averaging in trend.md

When To Use

• User logs a meal by photo, text, or label and wants a calorie/macro estimate
• User wants a calorie or protein target for a cut, bulk, or maintenance, or asks to count macros