Claim Kit

Inspiration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for Claim Kit

What it does

Claim Kit turns "my dishwasher broke" into a verified, ready-to-send warranty claim pack built only from evidence already on your NAS.

For anyone who has ever thrown away a warranty claim because finding the receipt, the serial number and the manual was too much hassle. Say "my dishwasher broke". Claim Kit searches your own NAS for the receipt, reads the warranty term, finds the photo of the rating plate and reads the serial number, opens the right troubleshooting page of the manual, and checks your door camera for the delivery date. You get a verdict (covered, act now, expired), a claim letter where every fact is linked to its source, and a list of anything still missing. If you agree, it saves everything into one claim folder. Your documents never leave your NAS, and Claim Kit never sends anything for you.

Target user and problem

Households who own dozens of appliances and devices. When one fails, the receipt sits in an email export, the serial number on a photo, the manual in a downloads folder. Hunting takes an hour, so many valid claims are never filed and people pay for repairs that warranty would cover.

Proposed solution

One sentence triggers a six-step workflow: find purchase proof, compute the warranty verdict (covered, act now, expired, unknown), read model and serial from the rating plate photo, pull matching troubleshooting pages, add door-camera delivery evidence, and assemble a claim letter where every fact cites its source file and page, plus a gap list.

Core user flow

User: "My dishwasher broke, it won't drain." Claim Kit replies with a verdict line ("Covered: 214 days left"), summary card, evidence index, draft letter and gaps. It asks once: "Save as a claim folder?" Only after yes and gateway approval are copies saved. Nothing is sent.

Difference from existing tools

Cloud assistants never see your receipts, photos and camera footage together, and users will not upload them. Warranty apps need manual entry upfront. Claim Kit needs zero setup: it works retroactively on data people already keep, cross-checks independent sources (invoice versus photo OCR versus delivery footage), and refuses to invent missing facts.

NAS capabilities by step

• Step 1: Knowledge collect-evidence plus Documents extract finds and reads receipts.
• Step 2: Documents qa and reconcile reads warranty terms.
• Step 3: Albums search-picture, object-albums and vision-ocr read the serial plate.
• Step 4: Knowledge plus Documents qa finds manual pages.
• Step 5: Surveillance cameras, event-timeline, event-evidence prove delivery date.
• Step 6: Files get-user-dir, mkdir, cpmv and Knowledge save-text build the folder.

Technical approach

SKILL.md follows the Uliya standard and only uses delegate to five registered experts (document, knowledge, photo, security-monitor, file). Each instruction is self-contained and receives only real upstream results. Input: product name; optional fault and date. Steps 1 to 5 are read-only; writes need user confirmation and gateway approval and never overwrite. Local NAS AI handles OCR, extraction and QA; no external models, services or data flows. Face and identity actions are deliberately unused.

Development status

Implemented: complete SKILL.md with references (capability map, warranty rules, claim template, test plan), passing the official checker with zero errors and zero warnings. Pending NAS validation: OCR quality on real plates, extraction accuracy across invoice layouts, surveillance event matching, approval prompts.

Validation plan

Core 1: invoice, plate photo, manual and delivery event seeded; verdict, serial and citations must be correct, and nothing is written before approval. Core 2: no receipt; verdict "Unknown", serial still reported, nothing invented. Edge: two dishwasher invoices; one clarifying question, model mismatch flagged, no merging.

Known limitations

Depends on users having kept some evidence. OCR may misread worn plates, so conflicts are shown, not resolved. Warranty terms are only taken from documents, so statutory rights are not calculated. Delivery matching is heuristic and optional. It drafts the claim; the user sends it.

Built With

• ai
• ugos-skill-creation-tool
• ugreen