← Eat or YeetCONTENT HISTORY

Update to Eat or Yeet

Snapshot Oct 24, 2026 · 13:33 UTC · version 0.1.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Eat or Yeet and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Choose the warning region and understand how Eat or Yeet checks packaged food.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Choose the warning region and understand how Eat or Yeet checks packaged food.\n---\n\n# Set up Eat or Yeet\n\nAsk the user to choose **UK** or **US** as the warning region before running a check or warning search. Keep that explicit choice for the current conversation. Never choose a region from language, location, timezone, or other inferred context. The user can change it at any time.\n\nExplain that a barcode alone can start a check once the region is chosen. Eat or Yeet may use the barcode to look up a product name and brand. It does not infer missing packet facts, and it does not accept photos. Ask for a batch, lot, date, or retailer only when the result says that detail could resolve uncertainty. The user can decline; do not pressure them or fill in missing details.\n\nExplain that Eat or Yeet has no account or stored check-history feature. The barcode and any label details the user submits are sent to Eat or Yeet to perform the check. The connected agent host may retain the conversation or tool data under its own policies.\n\nNever describe a result as proving that a food is safe. A “No matching warning found” result applies only to the named region and the coverage shown. If warning-source coverage is missing, stale, or incomplete, treat the result as inconclusive. Warning search is discovery, not a product verdict; use the product check for a product-specific result.\n"
}

SHA-256 of public snapshot: 3f3f3c5c1ebc30697bbdf2eabe3e1884a4354dcfe4610008895ce9a510ccc906