Pantry Tracker

Track grocery purchases and monitor food freshness using Supabase. Use when monitoring grocery orders, checking what food is expiring, logging pantry items,...

This skill appears coherent and limited to operating a Supabase-backed pantry. Before installing: (1) ensure you provide only the Supabase anon key (not the service_role key) and confirm your Supabase project enforces Row Level Security (RLS) or otherwise restricts access for that anon key; anon keys can still expose data if RLS/policies are misconfigured. (2) Verify that the email parsing is performed by your agent's separate email skill and that you do not accidentally provide email credentials to this skill. (3) Review the provided SQL schema in your own Supabase project and run it there (do not point the skill at a production DB you don't control). (4) Note the registry summary shows a malformed env listing ([object Object])—double-check the platform's install UI shows the two required env vars. (5) If you operate this in a multi-user environment, add RLS policies so anon keys can only access that user's items. Other than these standard cautions, the skill's behavior and resource needs are consistent with its description.

Type: OpenClaw Skill Name: pantry-tracker Version: 1.3.0 The pantry-tracker skill is a legitimate tool designed to monitor food freshness and log grocery purchases using a user-provided Supabase backend. The Python script (scripts/pantry.py) uses standard libraries to interact with the Supabase REST API and contains no evidence of malicious intent, data exfiltration, or unauthorized execution. While the skill instructs the agent to scan emails for grocery orders, this behavior is central to its stated purpose and relies on the agent's existing authenticated email tools rather than attempting to harvest credentials.