food-analyzer · v1.1.0 · 2026-05-14 · sha256 cf37de63b09e199c
food-analyzer v1.1.0A
Immutable. This exact content never changes and is served at /api/v1/blob/cf37de63b09e199c.
--- name: food-analyzer description: > Analyze food photos, nutrition labels, and ingredient lists. Trigger on food images, nutrition label scans, macro questions, glycemic questions, medication interaction checks, and similar food-analysis requests. version: 1.1.0 --- # Food Analyzer Analyze images of food, plated meals, nutrition labels, or ingredient lists and return a structured nutritional breakdown with fitness, glycemic, processing, and interaction context. ## Trigger When - The user starts with `fa` or `food` - The user uploads an image of food, a meal, a label, or an ingredient list - The user asks to analyze food, scan a label, estimate calories or macros, check blood sugar impact, or check medication compatibility - The user wants two foods or meals compared - The user wants repeated meal patterns reviewed across multiple analyses ## Input Modes Detect which mode applies from the visible input: | Mode | What Claude Sees | Behavior | | --- | --- | --- | | Meal or Plate | Actual food, plated dish, restaurant item | Estimate calories and macros from visual portion heuristics | | Nutrition Label | FDA-style Nutrition Facts panel | Extract exact values from the label | | Ingredient List | Text ingredients | Flag allergens, additives, and processing red flags | | Mixed | Label and product both visible | Prefer label data over visual estimates | | Comparison | Two foods, two labels, or two meals visible or described | Compare tradeoffs side by side before giving a recommendation | | History Review | Multiple prior meals or repeated food summaries provided | Find patterns across repeated analyses rather than analyzing one item only | If no image is attached and the request depends on visual inspection, ask for a photo before proceeding. ## Output Sections Include the sections that apply to the identified food: - Quick Summary - Nutrition Estimate - Fitness Alignment - Ingredient Flags - NOVA Ultra-Processed Food Score - Blood Sugar Impact - Meal Timing Assessment - Medication and Supplement Interactions - Notes - Healthier Alternatives when the food scores poorly ## Goal Aware Modes Infer the best mode unless the user explicitly gives one: - `fat loss` - `endurance fueling` - `muscle gain` - `blood sugar control` Use the selected goal to change the emphasis: - `fat loss`: satiety, calories, protein density, hidden calorie load, and appetite control - `endurance fueling`: digestibility, carb availability, sodium, hydration fit, and workout timing - `muscle gain`: protein quality, total calories, carb support, recovery fit, and meal composition - `blood sugar control`: glycemic load, fiber, meal pairing, ultra-processed signals, and timing caution ## Core Rules - Use visible label data when available - Estimate visually only when label data is not available - State confidence clearly - Separate obvious observations from low confidence guesses when the image or label is incomplete - Use the FDA 2,000 kcal reference diet for percent daily values unless the user provides custom targets - Keep medication and supplement warnings factual and end that section with a pharmacist and physician disclaimer - Omit swap suggestions when the food scores well overall ## Output Expectations The analysis should be structured, readable, and practical. It should cover: - calories, protein, carbs, fat, fiber, sugar, and sodium - percent daily values where applicable - additive and allergen flags when ingredients are visible - NOVA classification and the factors that drove it - glycemic index or load estimates when relevant - timing fit for pre-workout, post-workout, before bed, with medication, or general use - clinically significant medication or supplement interactions - quantified healthier swaps when needed Start with a short quick summary that is easy to scan before the deeper analysis. Use a structure like: ```text Quick Summary - Overall fit: [short line] - Best use case: [short line] - Biggest concern: [short line] - Confidence: [high, medium, low] ``` ## Confidence Levels - High: label clearly readable and values extracted directly - Medium: recognizable dish and portion size reasonably visible - Low: partial view, obscured label, layered dish, or unusual item When confidence is not high: - label direct observations as `Observed` - label uncertain inferences as `Lower confidence estimate` - do not present guesses as facts ## Reference Standards Use these as defaults unless the user provides custom targets: - Calories: 2,000 kcal - Total Fat: 78g - Saturated Fat: 20g - Cholesterol: 300mg - Sodium: 2,300mg - Total Carbohydrate: 275g - Dietary Fiber: 28g - Total Sugars: 50g - Protein: 50g - Vitamin D: 20mcg - Calcium: 1,300mg - Iron: 18mg - Potassium: 4,700mg ## NOVA Guidance Classify foods by processing level: - NOVA 1: unprocessed or minimally processed - NOVA 2: processed culinary ingredients - NOVA 3: processed foods - NOVA 4: ultra-processed foods When ingredients are visible, scan for marker additives such as emulsifiers, artificial sweeteners, artificial colors, preservatives, industrial thickeners, flavor compounds, and modified starches. If uncertain between two NOVA groups, prefer the higher group and note the uncertainty. ## Ingredient Risk Grouping When ingredients are visible, group concerns under clearer buckets: - additives and preservatives - sweeteners - seed oils and refined fats - ultra-processed signals - allergen or sensitivity flags Use the grouping to make the ingredient section easier to scan instead of listing everything as one flat set of warnings. ## Glycemic Guidance Use: - Low GI: under 55 - Medium GI: 56 to 69 - High GI: 70 and above Estimate glycemic load as `(GI x net carbs per serving) / 100` and consider modifiers such as fiber, fat, protein, vinegar, cooking method, particle size, ripeness, and food form. ## Comparison Mode When the user provides two foods or meals: - compare them side by side - identify the practical tradeoffs instead of pretending one is universally best - call out which one fits better for the inferred goal mode - end with a short recommendation based on the stated or inferred goal ## Meal Timing Guidance Adjust meal timing guidance based on likely use: - `pre workout`: lighter digestion, lower GI burden when needed, accessible carbs, and tolerance - `post workout`: protein support, carb refeed potential, sodium and hydration fit when relevant - `bedtime`: digestion load, satiety, blood sugar steadiness, and sleep disruption risk - `general daily use`: overall quality, portion fit, and repeatability If timing is not stated, infer the most relevant use case and say so briefly. ## Meal History Review When the user provides repeated meals or multiple prior analyses: - look for patterns in protein intake, carb quality, processed food load, sugar load, sodium, and timing fit - identify recurring wins and recurring issues - keep the review evidence based and practical - end with 2 to 3 focused adjustments rather than a giant rewrite of the whole diet ## User Preference Memory When the user gives stable preferences or recurring issues, carry them forward within the conversation: - favorite foods - foods they tolerate well - foods that repeatedly cause problems - sensitivities - recurring supplement interactions Use those preferences to refine later recommendations, but say when a conclusion still has low confidence. ## Validation Checklist - [ ] Label data takes precedence over estimates when visible - [ ] Quick summary appears before deeper sections - [ ] Confidence labels separate direct observations from weaker guesses - [ ] Goal mode changes the analysis emphasis appropriately - [ ] Percent daily values use the correct reference unless custom targets were provided - [ ] Comparison mode highlights tradeoffs instead of forcing one winner - [ ] Meal timing guidance matches the likely use case - [ ] Ingredient flags are grouped cleanly - [ ] Meal history review finds patterns across repeated analyses - [ ] NOVA classification includes rationale - [ ] Blood sugar impact is explained, not just labeled - [ ] Medication and supplement warnings stay factual and include a disclaimer - [ ] Healthier swaps appear only when the food scores poorly ## Help And Examples If the user is not sure how to use this skill, asks what it needs, or asks for examples: - Explain in plain language what this skill can do. - Tell the user the minimum input needed for a useful first pass. - Show the example prompts below. - Offer the fastest next prompt the user can send. Minimum useful input: - A food photo, label, meal description, or two items to compare. Example prompts: - `Use food-analyzer to compare these two lunches for protein, calories, and satiety.` - `Analyze this meal and tell me whether it fits a lean mass gain day.` - `Show me an example prompt for using this skill with a food photo or nutrition label.`