The Executor's Binder

Inspiration

When someone dies, the person left to sort things out, usually an adult child, spouse or sibling, faces three questions in the first two weeks: what policies and accounts exist and who must be told, which photos to show at the service, and how to keep their voice. If that life was kept on a UGREEN NAS, the answers are already on the box. Nobody should have to upload a parent's will, bank letters and last recordings to a cloud chatbot to find them.

What it does

The Executor's Binder is a Uliya Skill that works only with what is already on the NAS:

• Inventory: every policy, account, pension and contract, each row citing the document it came from, with flags for anything that names a beneficiary or asks to be notified on death.
• Memorial album: photos of the person with the family members you name, created only after you approve it.
• Keepsake: voice memos transcribed and saved, with your approval.
• Service chapter: if discharge papers or medal citations are found, a military record where every fact is labelled by its source: a document, a recording, or the family.
• Not found: an honest list of what no document supports, and who to ask.

Everything lands in one new dated binder file. It is an inventory, not advice: it never values assets, moves or overwrites files, sends anything off the box, or summarises medical papers.

How I built it

Pure Markdown, following the official Uliya Skill Development Standard. The skill delegates only to four on-box experts (file-agent, document-agent, photo-agent and knowledge-agent), fills every value from real upstream results, handles all five states (completed, failed, cancelled, waiting_user, waiting_approval) and asks for approval before any write. It passes the official uliya-skill-kit 0.7.3 checker with zero errors and zero warnings, backed by an automated test suite.

Challenges I ran into

Keeping medical content out without pretending a model can filter it. Medical papers are screened by file name and metadata before anything reads them, and appear in the binder only as a four-column table: issuer, date, reference and contact.

What's next

Round 2: run it on a real UGREEN AI NAS with a consenting family's photos and recordings, and confirm two-person photo search, transcript segments and the PDF metadata fields.

Built With

• markdown
• ugos
• ugreen-ai-nas
• uliya
• uliya-skill-kit