Inspiration
When a package never arrives, an item arrives broken, a warranty is denied or a card charge needs a dispute, the proof is scattered across receipts, statements and phone photos. People file from memory and miss what the seller or bank asks for. These are private files, so a self-hosted tool on your own NAS is a natural fit.
What it does
Claim Binder is a Skill for the UGOS AI NAS, and it is a self-hosted AI build. All of its AI work (OCR, vision, document reading and Q&A) goes only through the NAS's own UGOS expert agents and the models they use. It adds no cloud model, no third-party AI service and no external API, and your receipts, statements and photos stay on your own storage. You describe the claim and name the folders. It lists the proof that claim type usually needs and checks your files against it, marking each item found, partly found or missing. It builds a timeline in which every date names its source, and gives each file a SHA-256 fingerprint, a code that changes if the file changes. If a seller or bank letter lists what it wants, that list replaces ours. It saves the binder, and copies the evidence files into one folder, only after you approve each step. When two files disagree, it shows both sources and picks no winner.
How we built it
I used the official UGOS Skill Creation Tool (uliya-skill-kit 0.7.3, capability catalog 2.0.0). The main Skill only delegates to five NAS experts: file, document, photo, security-monitor and knowledge. They use the UGREEN capabilities ug-filesystem, ug-document, ug-photo, ug-surveillance and ug-knowledge, including their OCR and vision models. No third-party services are used, and the Skill itself sends nothing off the NAS. In Round 2 I will confirm on the test NAS where each expert's model runs. The package is SKILL.md plus two reference files. The kit's own checker gives a static pass with no errors or warnings. I used Claude through Claude Code, directed by me, to propose the idea and its name, draft the Skill and the proposal, and draft this text. Claude is a development tool only; it is not part of the Skill and is never called when the Skill runs. The full disclosure is in references/disclosures.md in the ZIP, and the PDF names the same tool.
Challenges
The capability catalog lists permissions and error codes as unknown, so the Skill assumes neither. It never uses a file's saved time as an event date, because copying a file can change it. It cannot look up tracking numbers or read a mailbox, so those items are listed as gaps.
What we learned
Ranking dates by how reliable their source is, and showing conflicts instead of settling them, keeps a binder honest. The approval steps keep the user in charge.
What's next
Validate on a real NAS with two core tests (package never arrived; item arrived broken) and one edge case (statement amount differs from receipt). On the same tests, confirm where each expert's model runs and that no file content leaves the NAS. Then test file formats and blurry receipts, which are unconfirmed.
Built With
- claude
- claude-code
- markdown
- ug-document
- ug-filesystem
- ug-knowledge
- ug-photo
- ug-surveillance
- ugreen-ugos
- uliya-skill-kit
