Skill: nutrition-menu-assessment


Nutrition Menu Assessment

Use this skill when the user asks which meal to choose, compares weekly menus, or wants a health/cholesterol-oriented conclusion from menu photos, restaurant pages, or fast-food product URLs.

Default output style

Workflow

  1. Extract the menu accurately
  2. For screenshots/photos: use vision to read days, soups, options, sides, sauces, prices if relevant.
  3. If OCR/vision is uncertain, state the uncertainty and avoid over-specific claims.
  4. Score for cholesterol/cardiovascular impact
  5. Prefer: legumes, vegetables, fish, lean poultry, unsmoked/unsausaged protein, boiled potatoes/rice, non-fried dishes.
  6. Penalize: fried/crumbed foods, fatty pork (knuckle, neck/krkovice), sausages/uzené/slanina, creamy cheese sauces, tartar/majo dressings, fries, dumplings as frequent default, very salty soups.
  7. Choose practical options, not perfect fantasy
  8. If all options are mediocre, choose the least harmful and explain modifications: smaller meat portion, skip tartar/majo, half dressing, no fries/sugary drink, add vegetables, avoid soup if salty/fatty.
  9. For URLs / fast food
  10. Try the official product page/nutrition calculator first.
  11. If official access is blocked or lacks data, use reputable secondary nutrition pages and label the data as approximate.
  12. Convert per-100g values to a plausible portion only if needed, and mark it as an estimate.
  13. For social posts / Facebook menu hunting
  14. If the user asks you to find a menu from a Facebook profile/page, do not claim success from the profile shell alone.
  15. First enumerate whatever public content is actually visible without login. A practical fallback is the mobile/public mirror path (m.facebook.com) via a text mirror such as r.jina.ai/http://m.facebook.com/..., which may expose the profile shell and public image URLs even when the normal site is hard to scrape.
  16. OCR the publicly exposed images to see whether any contain a weekly menu or date.
  17. If you only find food photos, event posters, or partial price lists, say so explicitly and state that the target weekly menu was not confirmed.
  18. When post/photo detail pages require login, stop short of inventing the menu and ask the user for a direct post URL or screenshot.
  19. Conclude with a simple verdict
  20. Use a 1–5 health impact scale if helpful, with scale direction explicit, e.g. 1 = dobré, 5 = špatné.

Useful Czech phrasing

Pitfalls

References