👨‍🍳 Cooking Coach

Mode: cooking-coach · Category: Lifestyle

Recipe ideas, meal planning based on what's in your pantry, dietary substitutions

Quick run

From the repo root, after pnpm -r build:

node apps/cli/dist/index.js -a cooking-coach -q "your question here"

Requirements

LLM provider

Recommended: anthropic, gemini, any general model

Set the corresponding API key in ~/.openvesper/.env:

ANTHROPIC_API_KEY (or other)

Plugins used

This agent has access to all plugins (cross-plugin tool registry), but typically reaches for:

notes

Skills it can pull in

recipe-adapt-for-diet

Example sessions

node apps/cli/dist/index.js -a cooking-coach -q "I have chicken, broccoli, rice. 3 dinner ideas?"

node apps/cli/dist/index.js -a cooking-coach -q "Substitutions for eggs in baking?"

Scheduled mode (optional)

This agent ships with a heartbeat checklist in.agents/cooking-coach/HEARTBEAT.md. The default schedule is0 17 * * * but the heartbeat is disabled by default.

To enable scheduled execution:

# Edit .agents/cooking-coach/HEARTBEAT.md
# Change "enabled: false" to "enabled: true"

# Then add it to your cron job state
node apps/cli/dist/index.js cron add hb-cooking-coach   --schedule "0 17 * * *"   --agent cooking-coach   --prompt "Run your heartbeat checklist for {{date}}"   --deliver-to "telegram:@me"

Files

The agent's source files live under .agents/cooking-coach/:

SOUL.md — persona and principles
IDENTITY.md — metadata (name, icon, model preferences)
USER.md — what the agent knows about you
TOOLS.md — tool policy
HEARTBEAT.md — scheduled checklist (opt-in)
MEMORY.md — long-term memory store

You can edit any of these files to customize the agent. Changes take effect on the next run — no rebuild needed.

Privacy

This agent runs entirely on your machine. Your prompts go only to your configured LLM provider. Nothing is sent to OpenVesper servers (we don't have any). SeeSecurity policy for details.