Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Meal Plan Generator

ASecurity

Build a flexible weekly meal plan with an AI assistant: start from your preferences and constraints, get a 7-day plan with a grocery list, batch-cook smartly, and use up leftovers. Use for weekly cooking, saving money on food, or eating better without rigidity.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill meal-plan-generator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Meal Plan Generator?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Meal Plan Generator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-meal-plan-generator/badge)](https://www.skillsdirectory.com/skills/aicodedecode-meal-plan-generator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: meal-plan-generator
description: Build a flexible weekly meal plan with an AI assistant: start from your preferences and constraints, get a 7-day plan with a grocery list, batch-cook smartly, and use up leftovers. Use for weekly cooking, saving money on food, or eating better without rigidity.
category: everyday-assistant
---

# Meal Plan Generator

## Overview

Weekly meal planning fails when it's treated as a rigid contract: seven days of recipes you'll
abandon by Wednesday. Good meal planning is looser — it's a system that answers two questions:
"what's for dinner tonight?" and "what do I buy on Saturday?" without daily stress.

This skill helps you build a meal plan conversationally with your assistant. You'll state your
preferences, constraints, and cooking reality; the assistant drafts a week of meals, a grocery list,
and a batch-cooking strategy. The emphasis is on flexibility: the plan bends around your week
instead of breaking on contact with it. Think of it as a framework with options, not a timetable.

## When to use

- Setting up a weekly cooking routine that reduces takeout and decision fatigue
- Planning meals around dietary needs (vegetarian, allergies, low-sugar, high-protein)
- Feeding a household with mixed preferences without cooking three separate dinners
- Cutting the grocery bill by buying with a plan instead of impulse shopping
- Cooking for one and wanting to avoid food waste

## Core concepts

- **Constraints first, recipes second.** Your plan starts from your real life: how many people, what
  you don't eat, how long you'll cook on a weeknight, your budget. Recipes that ignore these are
  decoration.
- **Plan around anchors, not all 21 meals.** Most people only need dinner planned, plus a rotating
  breakfast and simple lunches. Planning every single meal is overkill and breeds resentment.
- **Leftovers are an ingredient, not a failure.** Design meals that deliberately produce components —
  a big pot of rice, roasted vegetables, cooked lentils — that become tomorrow's lunch or the base of
  another dinner.
- **Batch the boring parts.** Washing and chopping vegetables, cooking grains, making one sauce — done
  once on the weekend, these shave 20 minutes off every weeknight meal.
- **Flexibility is the feature.** Build in swap slots: "any stir-fry," "clean-out-the-fridge soup,"
  one night explicitly reserved for takeout or leftovers. A plan with built-in slack survives; a plan
  without it doesn't.

## Practical workflow

Start with a brief that covers your real constraints. Be honest — the plan only works if the
assistant knows your actual life:

*"Plan my week of dinners for 2 people. We're vegetarian, my partner dislikes mushrooms, and I won't
cook for more than 30 minutes on weeknights. Budget about ₹2,500 for groceries this week. We have a
pressure cooker and a microwave."*

Then build it up in layers:

1. **Draft the week.** *"Suggest 7 dinners using these constraints. Include one batch-cook night, one
   leftovers night, and one easy/optional takeout night. Keep the cuisine varied."* Review the draft
   and veto what you'll never actually cook — honesty here saves the whole week.
2. **Get the grocery list.** *"Turn this into a grocery list organized by section: produce, dairy,
   grains, spices. Mark what I probably already have with a question mark so I can check."* Ask it to
   flag anything used by only one recipe — those are the waste risks.
3. **Plan the prep session.** *"What can I batch-cook on Sunday in under 90 minutes to make weeknights
   faster?"* One focused prep session is worth more than five ambitious recipes.
4. **Design the leftovers flow.** *"For each dinner, tell me what the leftovers become — next day's
   lunch or part of another meal."* Cook once, eat twice is the whole economics of meal planning.
5. **Keep a running list.** During the week, when something runs out or a recipe flops, tell the
   assistant: *"We're out of rice and the Tuesday curry was too bland — adjust next week's plan."* The
   plan gets smarter every week if you feed it feedback.

Nutrition notes the assistant gives you are general educational information, not medical or dietary
advice. If you have a health condition, allergies beyond the ordinary, or specific nutritional
targets, check the plan with a doctor or registered dietitian.

## Common pitfalls

- **Cooking seven new recipes.** New recipes take twice as long and produce twice the dishes. Aim for
  2–3 new ones max; the rest should be familiar or assembly-style meals.
- **Buying specialty ingredients for one dish.** That one jar of an obscure paste used once becomes
  pantry clutter. Prefer recipes that share ingredients with each other.
- **Skipping the swap slots.** If every night is fixed, the first busy evening kills the plan. Protect
  the leftovers night and the easy night — they're load-bearing.
- **Planning portions for a fantasy appetite.** Cook for the people you actually feed, and be
  realistic about how much you'll eat. "Serves 4" recipes for 2 people are a feature (lunch tomorrow),
  not a bug — as long as you planned for it.
- **Not reviewing what worked.** Spend two minutes on Sunday asking: what got eaten, what got wasted,
  what took too long? Next week's plan starts there.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →