warranty-rescue

Inspiration

When an appliance breaks, the papers that decide whether the repair is free are usually already on the family NAS: a photo of the receipt, a scanned warranty card, a PDF manual. Nobody wants to dig through them, read two documents side by side, and do the date math, so people often assume the warranty has expired and pay for a repair that was covered.

What it does

warranty-rescue answers one question with evidence: is this product still under warranty on the day it broke? It finds the receipt and the warranty terms for the product on the NAS, reads the purchase date and the warranty period, checks that both papers describe the same model, and gives one of three verdicts: covered, not covered, or cannot decide. Every date comes with the document, page, and quoted line it was read from. If the user says yes, it saves the verdict as a note and copies the papers into one claim folder for the repair service.

How we built it

It is an orchestration-only Skill written to the Uliya Skill Development Standard. SKILL.md delegates each step to the NAS experts: file-agent (ug-filesystem find, and mkdir and cpmv as copy for the claim folder), photo-agent (ug-photo vision-ocr for photographed receipts), document-agent (ug-document extract with the receipt schema, qa with the period and condition intents, and reconcile), and knowledge-agent (ug-knowledge save-text). Two references hold the verdict rules and the claim-folder rules. It was authored with Claude Code using the official uliya-skill-kit 0.7.3, and the kit checker returns static-pass with 0 errors and 0 warnings.

Safety by design

Original papers are never moved, renamed, or deleted; the claim folder holds copies only and nothing is overwritten. Every write waits for the user's yes and the platform approval. Nothing is sent outside the NAS. If the purchase date or the warranty period cannot be read from completed results, the verdict is "cannot decide" and the missing document is named instead of guessed.

What's next

Round 1 is a design and static-check build. On a real AI NAS we will tune the delegation instructions to the experts' actual outputs and validate two core cases (a PDF receipt that is still covered, a photographed receipt that is past its period) and one edge case (receipt and card with different model numbers, which must end in "cannot decide" with nothing written).

Built With

• claude-code
• markdown
• ugos
• uliya-skill-kit