agentleFS
Itsme23476Itsme23476/everyday-claude-skills/meal-planner/SKILL.md

meal-planner

Skill1 starsChanged 3 months agoMITView on GitHub

Plan a week of meals around the user's preferences and time, then produce a single organized grocery list. Use when the user says "plan my meals", "what should I cook this week", "make me a meal plan", or "sort out dinner for the week".

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep it to a couple of quick questions.

    line 18
  2. Distinctive:

    Keep weeknights fast; put anything involved on the weekend.

    line 26
  3. Distinctive:

    Don't plan meals around ingredients that are hard to find or wildly out of season unless the user asks.

    line 48
  4. Distinctive:

    If they gave a budget, stay in it and show a rough total.

    line 50
  5. Distinctive:

    Never order groceries or spend money — the list is the output.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meal Planner

Plan real meals a real person will actually cook, then hand over one clean shopping list.

Ask first (only what you don't already know)

  • How many people, how many days?
  • Any diet, allergies, or hard dislikes?
  • How much time on a weeknight — 15 minutes or happy to cook properly?
  • Anything already in the fridge to use up?

Keep it to a couple of quick questions. Don't interrogate.

Plan

  • One meal per day unless they asked for more. Vary the protein and cuisine so it doesn't feel repetitive.
  • Reuse ingredients across meals so nothing's bought for a single dish and left to rot — call this out ("half the coriander here, the rest in Thursday's").
  • Keep weeknights fast; put anything involved on the weekend.
  • Note roughly how long each takes.

Deliver

MON  Chicken traybake — 35m
TUE  Black bean tacos — 20m
WED  Leftover chicken fried rice — 15m
...

GROCERY LIST
Produce: onions ×3, coriander, limes ×4, ...
Protein: chicken thighs 1kg, ...
Pantry: black beans ×2 tins, ...
(skip — already have: rice, olive oil, garlic)

Group the list by aisle/section so shopping is one pass, not five laps.

Rules

  • Don't plan meals around ingredients that are hard to find or wildly out of season unless the user asks.
  • If they gave a budget, stay in it and show a rough total.
  • Never order groceries or spend money — the list is the output.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.