Grocery

Build and manage grocery lists with pantry inventory, household quantities, and dietary restriction safety.

Security Scan

The skill is internally consistent: it just manages grocery data in a user-owned ~/grocery/ folder, requests no external credentials or installs, and its instructions match its stated purpose.

Purpose & Capability

Name/description match the behavior: all operations are local list/pantry management and dietary checks. No unrelated credentials, binaries, or services are requested.

Instruction Scope

Instructions explicitly create and read/write files under ~/grocery/ (memory.md, pantry.md, history.md, stores.md). This is appropriate for a local grocery memory skill, but it does persist personal data (household size, restrictions, preferences) to plaintext files in the home directory.

Install Mechanism

Instruction-only skill with no install spec or code files. No downloads or package installs are performed.

Credentials

No environment variables, credentials, or external config paths are required. The requested data access (user's ~/grocery/ directory) is proportional to the stated functionality.

Persistence & Privilege

The skill persistently stores user data in ~/grocery/. It does not request always:true and does not modify other skills or system-wide settings, but users should be aware that personal info (allergies, household details) is kept on disk until removed.

Assessment

This skill is coherent and low-risk from a code/permission perspective: it stores grocery memory as plaintext files under ~/grocery/ and does not contact external services or request credentials. Before installing, consider: 1) Sensitive data (allergies, household members) will be saved locally—set restrictive file permissions (e.g., chmod 600 ~/grocery/*) or choose a different storage location if needed. 2) Back up or delete ~/grocery/ when you uninstall to remove persisted data. 3) Because it’s an instruction-only skill, there’s no installed binary to inspect, but you can open the SKILL.md, memory-template.md, and lists.md to verify behavior. 4) If you ever see the skill asking to read files outside ~/grocery/ or to send data to an external endpoint, stop and review—those would be unexpected. Overall this appears coherent and appropriate for the stated purpose.

When to Use

User needs help with grocery shopping logistics — creating lists, tracking pantry inventory, remembering household quantities, or checking items against dietary restrictions. Focus: the shopping itself, not meal planning.

Architecture

Memory lives in ~/grocery/. See memory-template.md for setup.

~/grocery/
├── memory.md          # HOT: preferences, restrictions, current list
├── pantry.md          # WARM: what's at home, quantities, expiry
├── history.md         # COLD: past purchases, patterns
└── stores.md          # User's preferred stores, aisle layouts

Quick Reference

Topic	File
Memory setup	memory-template.md
List operations	lists.md

Data Storage

All data stored in ~/grocery/. Create on first use:

mkdir -p ~/grocery

Scope

This skill ONLY:

• Maintains shopping lists from user input
• Tracks pantry inventory user reports
• Remembers dietary restrictions and preferences
• Suggests quantities based on household size

This skill NEVER:

• Accesses real store inventories or prices
• Makes purchases or places orders
• Scans barcodes or receipts
• Reads files outside ~/grocery/

Core Rules

1. Learn Household Context

What to capture	Example
Household size	"2 adults, 1 picky toddler"
Dietary restrictions	"gluten-free, no shellfish"
Preferred stores	"Mercadona primary, Carrefour backup"
Typical quantities	"4L milk/week, not 1L"

Store in memory.md on first mention. Never ask repeatedly.

2. Quantity Intelligence

• Default to household-appropriate portions (solo = small, family = bulk)
• Remember past quantities: "You usually get 2kg chicken"
• Flag unusual requests: "That's 3x your normal pasta amount — meal prep?"

3. Restriction Safety

• Always check new items against stored restrictions
• Know hidden names: caseína = dairy, gluten in soy sauce
• When uncertain: "Contains wheat — checking your restrictions: you're gluten-free. Skip?"

4. List Organization

• Group by store section when requested (produce, dairy, frozen)
• Support multiple active lists (weekly, party, camping)
• Deduplicate automatically, merge quantities

5. Pantry Awareness

When user reports what's home:

• Update pantry.md with quantities and dates
• Cross-check against list to avoid duplicates
• "You have 6 eggs at home — still adding 12 more?"

6. Recipe Input (Not Planning)

If user shares a recipe or meal:

• Extract ingredients to add to list
• Adjust for pantry stock
• Scale to household size
• Note: meal PLANNING belongs to meals skill — grocery just receives ingredient lists

Common Traps

• Suggesting 4-person recipes to single person → check household size first
• Recommending exotic ingredients unavailable locally → stick to user's stores
• Forgetting restrictions between sessions → always load memory.md
• Ignoring "picky eater" family members → track per-person preferences

Boundary with meals Skill

grocery (this skill)	meals (different skill)
What to BUY	What to EAT
Pantry inventory	Weekly meal plan
Quantities, brands	Recipes, variety
Restriction safety	Dietary balance
Store organization	Meal scheduling

If user asks "what should I eat this week?" → suggest meals skill. This skill handles: "what do I need to buy?"