← Zylu BusinessCONTENT HISTORY
WHAT CHANGED
Update to Zylu Business
Snapshot Nov 10, 2026 · 15:20 UTC · version 1.0.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Zylu Business 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": "Record an incoming vendor delivery in Zylu and verify stock changes. Use when a user asks to receive stock, record a delivery invoice, or add purchased inventory.",
"included_files": [],
"name": "inventory-receiving",
"skill_md_contents": "---\nname: inventory-receiving\ndescription: Record an incoming vendor delivery in Zylu and verify stock changes. Use when a user asks to receive stock, record a delivery invoice, or add purchased inventory.\n---\n\nRecord an incoming inventory delivery for one Zylu business.\n\n1. Establish the business context. If it is unknown, call `list_accessible_businesses`; ask the user to choose when more than one business is available.\n2. Resolve the vendor with `search_vendors` and products with `search_products`. Do not infer IDs from names. If a vendor or product cannot be found, explain the missing record instead of creating one unless the user explicitly asks for that.\n3. Collect and restate the receipt details before writing: vendor, invoice number, purchase date, and every line item's product, whole quantity, unit purchase price, optional tax treatment, and optional expiry date.\n4. Call `create_inventory_receipt` only after the user has explicitly asked to record the delivery and the details are unambiguous. Do not set `allow_duplicate` unless the user explicitly authorizes a duplicate invoice number.\n5. Verify the returned receipt: invoice number, vendor, received lines, total cost, and each product's `new_stock`. Report discrepancies or failed items clearly.\n\nThe tool changes product stock. Do not represent a draft as recorded, and do not use a purchase order workflow unless the user specifically asks to create or receive a purchase order.\n"
}SHA-256 of public snapshot: d225deed4458b506bb38d5ea22879942e8776d3ed4f1b9c438e7042edeb99202