meal-planning — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited meal-planning (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Build weekly meal plans in Mealie using the family's recipe library, protein rotation philosophy, and batch cooking strategy.
get_meal_plans(start_date="YYYY-MM-DD", end_date="YYYY-MM-DD")Always check what's already planned before filling in a week. This avoids duplicating entries.
create_meal_plan_entry(
date="YYYY-MM-DD", # Required
entry_type="dinner", # "breakfast" | "lunch" | "dinner" | "side"
recipe_slug="beef-stew-foundation" # Or use title/note for no-recipe entries
)Entry types:
"dinner" — default for weekly planning"breakfast" — morning meals"lunch" — midday meals"side" — accompaniments to a mainDates must be in `YYYY-MM-DD` format. Always verify the date format before making API calls.
delete_meal_plan_entry(entry_id="...")Entry IDs are returned by get_meal_plans.
After planning the week, add all recipe ingredients to a shopping list:
add_recipe_to_shopping_list(list_id="...", recipe_slug="...")Call this for each planned recipe to build a comprehensive grocery list.
YYYY-MM-DDCall get_meal_plans for the week. Note which dates are already filled and which are open.
Use search_recipes to browse the library. Get a variety across:
Useful searches:
search_recipes(tags=["beef"]) — beef recipessearch_recipes(tags=["chicken"]) — chicken recipessearch_recipes(categories=["Main Courses"]) — all mainssearch_recipes(tags=["quick"]) — weeknight-friendlyBuild a balanced plan following the protein rotation:
| Day | Protein Anchor | Character |
|---|---|---|
| Monday | Chicken | Often lighter, transitioning from weekend |
| Tuesday | Beef | Hearty midweek |
| Wednesday | Quick / Leftovers | Busy night — use Monday's extra batch |
| Thursday | Lamb or Turkey | Variety protein |
| Friday | Fish or Pasta | End-of-week flexibility |
| Saturday | Beef or Chicken | Family dinner — more elaborate |
| Sunday | Batch cook + Soup/Stew | Sets up the week |
Adjust based on what's in the recipe library and what the user requests.
Before creating entries in Mealie, present the draft plan to the user:
Here's the week I'm planning:
Monday 2/24 — Roasted Chicken Thighs with Root Vegetables (45 min)
Tuesday 2/25 — Beef Stew — Foundation (3 hrs, batch cook Sunday)
Wednesday 2/26 — Leftover stew + fresh bread rolls
Thursday 2/27 — [Turkey dish or lamb if available]
Friday 2/28 — [Fish or pasta dish]
Saturday 3/1 — [Elaborate beef or chicken dish]
Sunday 3/2 — Batch cook: stock + chili
Shall I add these to Mealie's meal planner? I can also suggest recipes if any slots are empty.On approval, call create_meal_plan_entry for each dinner. For recipes that don't have a slug yet or are placeholder ideas, use the title parameter instead of recipe_slug.
Would you like me to add all the ingredients to a shopping list?If yes: call get_shopping_lists to find or create a list, then add_recipe_to_shopping_list for each planned recipe.
Rotate through four protein anchors each week:
Avoid the same protein two days in a row unless using leftovers intentionally.
Sunday (or a designated batch cook day) sets up the week:
Plan intentional leftovers rather than treating them as accidents:
In the meal plan, list "Leftover [dish]" using the title parameter instead of a recipe slug.
Adjust plans by season:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.