Where It Is

Inspiration

A post on r/personalfinance with more than 2,700 upvotes starts with a father who passed away unexpectedly. His wife "doesn’t know where anything is outside of their joint bank accounts." When the papers are already scanned onto a home NAS, the information exists. What the family lacks is a map of it.

What it does

Where It Is analyzes a NAS folder and builds a family dossier that lists the documents found and which expected categories were not found in that folder.

The dossier has three parts:

• Start here: a guide to where to start at a difficult moment, with who to call first and where the will and legal papers are.
• To finish this dossier: what was not found, items missing a detail (for example, a life policy with no beneficiary), files that could not be read clearly, and documents with two versions.
• Inventory: every account, policy, property, debt and key contact found, each with the file it came from.

The user selects a folder and the Skill reads the files while showing its progress. It then shows a preview, and the dossier is saved only after the user approves it. Running it again later shows what is new, what is no longer found and what expires in the next 90 days.

How I built it

Where It Is is a Markdown Skill that follows the Uliya Skill Development Standard. I built it with the official uliya-skill-kit 0.7.3. The parent Skill only delegates, and each step uses the real result of the previous one:

To test it, I created a synthetic family (the Ruiz family) with 16 files. The set includes two categories left out on purpose, a policy with no beneficiary, two versions of the same policy, an expired passport and a blurry receipt. For every file I wrote down the result the Skill should return. The package passes the official static checker with no errors or warnings.

Privacy and data handling

• The Skill reads only the folder the user selects, and never moves or deletes files.
• The dossier shows only the last four digits of account, policy and identity numbers. Optional copies of originals show full numbers, and the user is told so before choosing.
• If the user selects a cloud model in Uliya, document text read by document-agent and photo-agent is sent to that Uliya-supported service. The Skill calls no other external service.

Challenges

• There is no NAS in Round 1, so the whole workflow was designed against the public capability catalog. Behaviors the catalog does not describe in detail are listed as pending NAS validation instead of being assumed. One example is whether text recognition accepts paths outside the photo library.
• The kit's template and its checker disagree on the format of the capability evidence section. I followed the checker.
• Wording mattered more than I expected. A category that was not found is reported as "not found in this folder", because the paper may exist somewhere else.

What I learned

A family dossier is useful as much for what it shows is missing as for what it lists. A Skill that touches sensitive papers has to be clear about scope, approvals and where the text is processed before it does anything.

What's next

If selected as a finalist, I will run three test cases on the assigned NAS:

• Core case 1: a complete family folder.
• Core case 2: missing documents, duplicate versions and an update.
• Edge case: an empty or photos-only folder, where the Skill must stop without inventing results.

AI disclosure

I used Claude Code (Anthropic) for these tasks:

• drafting and structuring the Skill's Markdown from my design decisions;
• running the official checker;
• generating the synthetic test documents;
• running simulated reviews;
• researching sources;

Built With

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