Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Food photo analysis and meal logging for ClawCoach. Send a photo of your meal and get instant macro breakdown via Claude Vision.
Food photo analysis and meal logging for ClawCoach. Send a photo of your meal and get instant macro breakdown via Claude Vision.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill handles food photo analysis via Claude Vision, text-based meal logging, and the confirmation flow.
User sends a photo — assume it is food unless context clearly suggests otherwise User types a food description ("I had 2 eggs and toast for breakfast") User says "log [food]" or "I ate [food]" User wants to edit or delete a previous meal
All meals are stored in ~/.clawcoach/food-log.json with this structure: { "meals": [ { "id": "2026-02-22-lunch-001", "date": "2026-02-22", "type": "lunch", "status": "confirmed", "items": [ { "name": "grilled chicken breast", "portion": "6 oz", "calories": 280, "protein_g": 52, "fat_g": 6, "carbs_g": 0 } ], "total_calories": 520, "total_protein_g": 62, "total_fat_g": 14, "total_carbs_g": 48, "source": "photo", "timestamp": "2026-02-22T12:35:00Z" } ] }
When the user sends a photo: Analyze the image using your vision capabilities. Identify every distinct food item visible. For each item estimate: Name (be specific: "grilled chicken breast" not just "chicken") Portion in common units (oz, cups, pieces, slices) Calories and macros (protein, fat, carbs in grams) Use your nutritional knowledge. For common foods, these are well-established values. Be conservative with portions if uncertain. Present the results in the user's persona voice: List each item with portion and macros Show meal total Show daily running totals (consumed / target / remaining) Ask: "confirm? (yes / edit / redo)" Handle response: "yes" / "confirm" — Write the meal to ~/.clawcoach/food-log.json with status "confirmed" Correction (e.g., "the rice was brown rice" or "it was more like 8oz") — recalculate and present updated totals "redo" — ask for a new photo or text description After confirmation, always show updated daily totals.
When the user describes food in text: Parse the food items and estimate portions from the description Calculate macros for each item using your nutritional knowledge Follow the same confirmation flow as photo analysis
Categorize meals by time: Before 10:00 = breakfast 10:00 - 14:00 = lunch 14:00 - 17:00 = snack After 17:00 = dinner The user can override: "log this as a snack"
"Delete my lunch" — find today's lunch entry, remove it from food-log.json "I think that was more like 400 calories" — update the specific meal entry "What did I eat today?" — list all confirmed meals for today with totals
After any meal is confirmed, calculate and show: Read profile from ~/.clawcoach/profile.json for targets Sum all confirmed meals for today from food-log.json Display: Consumed: X cal | Xg protein | Xg fat | Xg carbs Target: X cal | Xg protein | Xg fat | Xg carbs Remaining: X cal | Xg protein | Xg fat | Xg carbs
Blurry or unclear photo: "I can't quite make out the food. Try a better lit photo, or just tell me what you had." Non-food photo: "That doesn't look like food! Send a photo of your meal, or type what you ate." Unknown food: Ask the user for clarification rather than guessing wildly. Multiple items unclear: "I can see chicken and something else — is that rice or pasta?" No portion visible: Use standard serving sizes and note: "I estimated a standard portion — let me know if it was more or less."
Use these as a baseline. Scale by estimated portion size. FoodCalProteinFatCarbsChicken breast (grilled)165313.60Salmon (baked)20820130White rice (cooked)1302.70.328Brown rice (cooked)1232.71.026Pasta (cooked)13151.125Broccoli (steamed)352.40.47Egg (whole, large ~50g)15513111.1Avocado1602159Sweet potato (baked)9020.121Greek yogurt (plain)59100.73.6Banana (~120g)891.10.323Oats (cooked)682.41.412Bread (white, per slice ~30g)26593.249Cheese (cheddar)40325331.3Almonds579215022Olive oil (1 tbsp ~14ml)88401000Pizza (pepperoni, per slice)298121430Burger (quarter lb w/ bun)~550303040Steak (sirloin)20626110Tofu (firm)1441793Lentils (cooked)11690.420Milk (whole, 250ml)613.23.34.8Protein shake (~1 scoop)~120251.53 For foods not on this list, use your general nutritional knowledge. Be transparent when estimating.
Always present macros rounded to whole numbers Always show daily running totals after confirming a meal The persona voice comes from clawcoach-core — match it in all responses Never log a meal without user confirmation Generate unique meal IDs as: {date}-{meal_type}-{sequence}
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.