Help us improve
Share bugs, ideas, or general feedback.
From grocery-agent
Review and set up the user's grocery profile — taste, cooking preferences, diet principles, starting pantry, heat-and-eat acceptance, and kitchen equipment. Idempotent: on a brand-new user it walks first-time setup; on a returning user it reads back what it already knows and asks what to change. Use for "get started", "set me up", "onboard me", "update my profile", "what do you know about me", "change my preferences/diet/taste", or when the read tools show an empty profile.
npx claudepluginhub caseywebb/groceries-agent --plugin grocery-agentHow this skill is triggered — by the user, by Claude, or both
Slash command
/grocery-agent:configure-grocery-profileThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Prerequisite** — if you haven't already this session, read the `grocery-core` and `grocery-corpus` skills before continuing.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Prerequisite — if you haven't already this session, read the
grocery-coreandgrocery-corpusskills before continuing.
This skill is idempotent — it both sets up a new profile and reviews/edits an existing one. Always start by reading the current state: read_preferences(), read_taste(), read_diet_principles(), read_pantry(), read_kitchen(). Then branch:
The five areas:
update_taste. A couple of sentences is plenty; don't interrogate.default_cooking_nights (nights a week they cook) and lunch_strategy (e.g. leftovers), plus any standing brand defaults. Via update_preferences. Skip anything they have no opinion on — defaults are fine.update_diet_principles. Distinguish hard restrictions (gates) from soft variety targets.update_pantry. Keep it light — the pantry self-corrects through normal use.add_draft_ready_to_eat({ meal, name, status: "active" }) — items the member explicitly accepts land active, not as drafts. Purely optional: someone with no opinion skips it and the catalog stays empty, filling later through discovery.update_kitchen({ operations: [{ op: "add", slug }] }) (slugs: pressure-cooker, sous-vide-circulator, blender, ice-cream-maker). This is the only area to seed here — don't ask about pots, pans, or oven count (that surfaces naturally during cook, into notes). Skippable: leaving it empty means I won't gate any recipes (an empty inventory shows everything), so it only ever adds precision. It keeps recipes I can't make from being suggested.Persist each change as you go (the granular write tools each commit on their own — appropriate here, since this is a sequence of standalone config writes, not one batched planning session). On a fresh setup, when the basics are in, offer the natural next step — "want me to put together a first menu?" — which hands off to the meal-plan flow. Don't block on completeness; the profile fills in through normal use.