Inspiration
Every household has the same blind spot: if something happened to you tomorrow, could your partner or family find your insurance policies, bank accounts, will or power of attorney? Many NAS owners have these documents scanned somewhere, scattered across folders, with nobody knowing what is missing or out of date. Building a proper emergency binder by hand takes days, so almost nobody does it. And uploading your most sensitive paperwork to a cloud AI is exactly what most people want to avoid. A local AI NAS is the one place where this can be solved privately.
What it does
Emergency Binder is a Uliya Skill for UGREEN AI NAS. You say "Create my emergency binder from my Paperwork folder", and the Skill:
- scans only the folders you approve (read-only),
- reads documents and phone photos of paper letters locally,
- extracts key facts: category, provider, holder, reference numbers (account and ID numbers masked), dates, contact and original file location,
- checks everything against an essential-document checklist,
- builds an action list: missing essentials, expired or soon-expiring documents, cancellation notice deadlines, superseded versions and unreadable files,
- shows a preview and, after your confirmation, saves a dated plain-language overview in your binder folder and optionally copies the originals into category subfolders.
Run it again later ("Update my emergency binder") and it processes only new or changed files, flags documents that disappeared, and keeps the previous overview as history. Nothing ever leaves the device.
How we built it
The Skill is a pure orchestration workflow written to the Uliya Skill Development Standard with the official UGOS Skill Creation Tool. A ten-step plan delegates self-contained tasks to four registered NAS experts:
- file-agent: folder scan, binder folder, copy-only file operations
- document-agent: classification, key-fact extraction, expiry and notice dates
- photo-agent: text recognition for photographed paper documents
- knowledge-agent: saving the dated overview
Every step uses only verified results from the previous one, all terminal results and both waiting flows are handled, and every write happens only after a preview and the platform's approval. Supporting references define the checklist, the overview format, privacy rules and test cases. Claude (via Claude Code) served as the AI writing assistant alongside the kit's static checker.
Challenges we ran into
- Designing a workflow without any NAS hardware: every step had to be mapped to capabilities listed in the published catalog, without guessing.
- Privacy by design: the overview must be useful in a crisis without exposing passwords, full account or ID numbers, or health details.
- Making it trustworthy for repeat use: no overwritten files, no moved originals, no invented data, and honest reporting of empty or partial results.
- A smaller local model: instructions had to be simple, explicit and split into small batches.
Accomplishments that we're proud of
- A Skill that reasons about what is missing, what is expiring and which version is current, not just what is there.
- Zero errors and zero warnings in the official static checker.
- An update mode that turns a one-off task into a yearly life-admin check.
What we learned
Good AI workflows on a NAS are less about clever prompts and more about clear boundaries: which expert does what, what needs confirmation, and what to do when nothing is found. Local AI changes which problems are worth solving, because the most sensitive data is finally usable.
What's next for Emergency Binder
- Validating and tuning extraction on a real UGREEN AI NAS iDX6011 Pro
- Optional tagging of original files for quick lookup
- Country-specific checklists (e.g. Germany, US, UK)
- A printable version of the overview for the physical emergency folder
Built With
- claude-code
- local-ai
- markdown
- ugos
- uliya