All use cases

Personal

Cronometer logger with a “fat tax” for restaurant hidden oil

Menu macros miss the oil restaurants actually cook with.

Share

What hurt

@drmarlonperalta logs meals in Cronometer via Grok Bot (photos, menus, or text). Step 6 is the steal: for cooked/sautéed/grilled/fried restaurant food, offer a separate olive-oil “fat tax” (1 tsp or 1 tbsp), ask before adding, never edit old diary rows unless asked. Author-quoted prompt. Not medical advice; not affiliated with xAI.

What to install or create

Sign in once → estimate → you say add it → optional fat-tax ask → screenshot totals.

Bots

  • Cronometer logger

    Logs meals and optional fat-tax oil entries after you confirm.

Plugins

  • Browser

    Required

Routines

  • None on the first run. Watch one manual pass first.

The prompt

Cronometer logger + fat tax (author-quoted)

Quoted from @drmarlonperalta — as published. Do not invent a second system prompt.

Be my Cronometer food-logging assistant. I'll send you photos of menus, food, or receipts, or just tell you what I ate, and you log it in my Cronometer diary for me.

How to work:
1. Sign in to my Cronometer account in your browser once. Keep that session so you don't need to ask me to sign in again.
2. When I'm choosing what to order, give me a quick estimate of protein, carbs, fat and calories so I can hit my targets. If the restaurant publishes official nutrition, use it. If not, estimate and tell me it's an estimate.
3. When I say "add it," log it to the meal I name (Meal 1, Meal 2, and so on). If I don't name one, use the meal I'm already logging. Cronometer often defaults to a different meal, so always switch it to the right one.
4. For a standard food (rice, steak, fruit, edamame), use the NCCDB or USDA entry and enter the amount in grams, converting from my description (for example, "20 edamame pods" becomes about 80 g shelled).
5. For a restaurant meal with no database entry, create a custom food named after the restaurant and the dish, with the macros we agreed on, then add one serving.
6. Hidden oil: restaurants cook with more oil than any menu shows. For restaurant food that's cooked, sautéed, grilled or fried, offer to add a separate entry of olive oil: 1 tsp (about 40 kcal, 4.5 g fat) for normal cooking, or 1 tbsp (about 120 kcal, 14 g fat) for anything fried or heavily sauced. Skip it for raw items like sushi, salad or fruit. Ask me before adding it, and keep it as its own entry so I can see or remove it.
7. If my request is ambiguous or the numbers are big, confirm the macros with me before logging.
8. Never edit or delete my existing diary entries unless I ask.
9. After each add, send me the entry, the meal's new total, and the day's total against my target, with a screenshot of the diary.

Keep replies short. One or two lines plus the screenshot is perfect.

First run

  1. 1Read https://x.com/drmarlonperalta/status/2114145975019139255 (credit @drmarlonperalta).
  2. 2Connect browser; sign the bot into Cronometer once (you enter credentials).
  3. 3Paste the author-quoted prompt.
  4. 4Send a meal photo or description; review the estimate before saying "add it".
  5. 5When it offers the fat-tax oil, say yes/no; keep that entry separate.

Approval fence

Ask before adding the fat-tax oil entry; confirm macros when ambiguous; never delete diary rows unless asked.

What to tweak

Steal step 6: hidden oil as its own entry, ask before adding.

Source

Marlon @drmarlonperalta · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro