Inspiration
After a break-in, your insurer asks you to prove what you owned and what it cost. Most people already have that proof: a photo with the TV in the background, the laptop receipt in a documents folder, the camera clip from that night. It is just scattered across years of files. A UGREEN AI NAS already keeps that archive in one place, on hardware the household owns. I wanted the NAS to do the digging.
What it does
ClaimReady is a UGOS Skill. You say: "Prepare a claim for the break-in on 12 October: laptop, TV, camera." Then it:
- Lists the camera events from the incident window (Surveillance).
- Finds earlier photos of each item, and you confirm which ones really show it (Albums).
- Extracts receipt details and matches them to the items (Documents).
- Transcribes your spoken account into a statement (Knowledge).
- Answers policy questions by quoting the clause, without ever deciding coverage (Documents).
- Shows an evidence table (proof found, partial proof, no proof found). After your review and the platform's approval, it copies the evidence into one tagged claim folder with a summary file (Files, Knowledge).
Every value names the file it came from. Originals are never moved, renamed or deleted.
How I built it
ClaimReady is a SKILL.md with five reference files and no scripts. It orchestrates ten delegate steps across five registered experts (security-monitor-agent, photo-agent, document-agent, knowledge-agent, file-agent), covering seven CLIs from capability catalog 2.2.0. I wrote it with the UGOS Skill Creation Tool 0.7.7 and it passes the tool's static check with no errors or warnings. I used Claude as an AI assistant to draft and review the text against the catalog.
Challenges
- Not guessing. The easy failure is inventing a price for an item with no receipt. ClaimReady marks it "no proof found" instead.
- Staying out of advice. Coverage is the insurer's decision. ClaimReady quotes the clause and says so.
- Using only what exists. The catalog's reconcile action compares contracts with invoices, not an item list with receipts, so the matching is done from extracted fields under written rules.
- Building without a NAS. I listed the eight points that can only be settled on a real device, such as whether camera evidence comes back as copyable files.
What I learned
- Most of a Skill's work is knowing where to stop: the review point, the approvals and the failure handling took more thought than the main flow.
- For evidence, being able to trace an answer matters more than how well it is written.
What's next
Testing on a real NAS with three prepared cases: three stolen items with full evidence, a coverage-and-excess question, and an item with no proof at all.
ClaimReady organises evidence. It is not legal or insurance advice.
Built With
- ai-nas
- claude
- local-llm
- markdown
- ugos
- ugos-skill-creation-tool
- ugreen
