← IZeatCONTENT HISTORY
WHAT CHANGED
Update to IZeat
Snapshot Oct 31, 2026 · 01:22 UTC · version 1.0.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save IZeat and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Present results from IZeat tools so customers can identify which facts were read from or recorded in their IZeat account.",
"included_files": [],
"name": "izeat-receipts",
"skill_md_contents": "---\nname: izeat-receipts\ndescription: Present results from IZeat tools so customers can identify which facts were read from or recorded in their IZeat account.\n---\n\n# Present IZeat results\n\nWhenever an IZeat tool result contributes to a customer-facing reply, begin the visible reply with\nthe exact prefix `IZeat ·`.\n\nThe prefix identifies the facts returned by IZeat. It reassures the customer that information was\nread from or recorded in their IZeat account rather than inferred from the assistant's conversation.\n\nTreat the returned `statement` as the authoritative receipt. Preserve every fact it contains and\nkeep the prefix unchanged when presenting those facts in the customer's language. If the reply also\nincludes general assistant guidance, put the signed IZeat information first and clearly separate the\nguidance that follows.\n\nAn IZeat interactive report accompanies a day or period result. A day report shows calorie and macro\ntotals, targets and remaining amounts, every recorded meal, and each food's quantity, calories,\nmacros and source. A period report shows coverage, calorie and macro averages, targets, and the daily,\nweekly or monthly trend.\n\nDo not add the prefix to a question asked before any IZeat tool has been called. Do not expose tool\nnames, connector names, request fields, identifiers, tokens, schemas, or other implementation details\nin customer-facing text.\n\n## Catalogue and preparation results\n\nOffer catalogue recipes only in response to the customer's request for meal ideas.\nUse the returned recipe references and plate sizes when they choose a recipe, including\nthrough the “I'll cook it” button. A choice requests preparation; it is not evidence\nthat the customer ate anything. Wait for their actual consumption and quantities\nbefore recording a meal.\n\nPresent ingredients scaled to the selected plate. The returned steps are the original\nmethod for the whole recipe: do not confuse quantities in those steps with the scaled\nplate ingredients. Credit the creator or inspiration exactly as returned.\n\nA catalogue proposal records a deduplicated view. A successful complete-method request\nrecords a separate deduplicated use for creator royalties. Neither is proof of cooking\nor consumption, and a later meal log does not add another recipe use.\n\nShow the interactive recipe and report cards when supported by the host. Do not claim\na card rendered successfully without observing it. If the host cannot display a card,\nanswer from the returned data and explain the display limitation without inventing data.\n"
}SHA-256 of public snapshot: 50132d860b1ffdb5e7c2374036b7c5ea791d0b3ad5e1bc5e52aa2b8cdffd0a91