Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Plan meals with weekly menus, shopping lists, batch cooking, budget tracking, dietary preferences, and recipe management.
Plan meals with weekly menus, shopping lists, batch cooking, budget tracking, dietary preferences, and recipe management.
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.
On first use, read setup.md for onboarding guidelines. Start helping naturally without technical jargon โ users can always ask about storage details if curious.
User wants to plan meals, generate shopping lists, track food budget, organize recipes, coordinate household eating, or reduce food waste. Agent handles the full meal lifecycle: planning, shopping, cooking, and reviewing.
Memory lives in ~/meal-planner/. See memory-template.md for structure. ~/meal-planner/ โโโ memory.md # Preferences + dietary info + household โโโ weeks/ # Weekly meal plans โ โโโ YYYY-WXX.md # Week 12 of 2026 = 2026-W12.md โโโ recipes/ # Saved recipes โ โโโ {recipe-name}.md โโโ shopping/ # Shopping lists โ โโโ YYYY-MM-DD.md โโโ inventory/ # What's in pantry/fridge โ โโโ pantry.md โ โโโ fridge.md โโโ templates/ # Reusable meal templates โ โโโ {template-name}.md โโโ archive/ # Past weeks for reference
TopicFileSetup processsetup.mdMemory templatememory-template.mdShopping optimizationshopping-guide.mdBatch cookingmeal-prep.mdBudget trackingbudget-tips.md
Before any meal planning, read ~/meal-planner/memory.md for: Dietary restrictions and allergies (critical for safety) Household composition (adults, kids, guests) Cooking skill level and time constraints Budget targets and preferences Cuisine preferences and dislikes
PhaseActionPlanCreate week file in weeks/ with all mealsShopGenerate shopping list from week planPrepSuggest batch cooking opportunitiesCookReference recipes, adjust portionsReviewNote what worked, update preferences
When user asks to plan meals: Check inventory first (avoid buying duplicates) Balance nutrition across the week Cluster similar ingredients (reduce waste) Plan leftovers strategically (cook once, eat twice) Leave 1-2 flex slots for spontaneity or eating out
For any dietary restrictions or allergies: Flag incompatible recipes BEFORE suggesting Check ingredient lists thoroughly Suggest substitutions when possible Never assume "a little bit is fine" Mark severity: preference vs. intolerance vs. allergy (life-threatening)
When cooking for multiple people: Track individual restrictions per person Note kid-friendly vs. adult portions Plan meals everyone can eat (or easy modifications) Track who likes what (reduce "I don't want that" moments)
StrategyTypical SavingsWhen to ApplySeasonal produce20-40%Always check what's in seasonBatch cooking30% time, 15% costBusy weeksProtein rotation15-25%Alternate expensive/cheap proteinsPantry meals50%+End of budget cycleStore brands10-30%Most staples
Proactively ask about inventory updates: After shopping trips: "Want to update what you bought?" When planning: "Checking pantry โ last update was X days ago" For staples: track approximate quantities (full, half, low, out) ## Pantry โ Updated YYYY-MM-DD ### Grains & Pasta | Item | Status | Notes | |------|--------|-------| | Rice | Full | 5 lb bag | | Pasta | Half | | ### Canned Goods ... ### Spices ...
Planning without checking inventory โ duplicate purchases, waste Overambitious meal plans โ exhaustion, ordering takeout Ignoring prep time โ not just cook time, total time matters Same proteins all week โ meal fatigue, nutrition gaps No flex meals โ rigid plans break under real life Forgetting leftovers โ food waste Not tracking what worked โ repeating failures
Data that stays local: All meal plans, recipes, shopping lists stored in ~/meal-planner/ Dietary restrictions and household info in ~/meal-planner/memory.md No cloud sync, no external services This skill does NOT: Send any data to external servers Access health apps or fitness trackers Store payment information Read files outside ~/meal-planner/ User consent: Files created only when user engages with meal planning User can view/edit all stored data directly (plain markdown) User can delete ~/meal-planner/ at any time to remove all data
This skill ONLY: Manages meal planning in ~/meal-planner/ Reads/writes markdown files for plans, recipes, shopping Suggests based on preferences and inventory This skill NEVER: Orders groceries (provides list for user to order) Accesses health apps or fitness trackers Stores payment information Reads files outside ~/meal-planner/ Provides medical nutrition advice (refer to dietitian for health conditions)
Install with clawhub install <slug> if user confirms: grocery โ detailed grocery management cooking โ cooking techniques and tips nutrition โ nutritional tracking and analysis recipe โ recipe discovery and management daily-planner โ daily task management
If useful: clawhub star meal-planner Stay updated: clawhub sync
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.