Trip Dossier

Inspiration

I started out wanting Google Photos on my NAS: search by place and person, automatic albums, trip recaps. Then I noticed that UGOS already does most of that. What Google Photos cannot do is see the rest of a trip: the flight booking, the hotel invoice, the train tickets, the receipts. On a NAS, the photos and the paperwork sit on the same machine, just in different places. Trip Dossier pulls both halves of a trip together.

What it does

Say "put together our Japan trip" and the skill:

1. Finds the photos and videos from that place and time.
2. Shows what it found and confirms the trip dates, album name, and an optional people filter.
3. Creates the album.
4. Finds travel documents in one folder you name, from 90 days before the trip to its end.
5. Extracts vendor, dates, places, amounts, and booking references from each document.
6. Drafts a trip summary with an itinerary, costs with a total per currency, sources, and gaps.
7. Saves the summary as a note once you approve the draft.
8. Optionally copies or moves the documents into one trip folder.

Nothing is created, saved, copied, or moved before the user says yes. It never deletes, never overwrites, and never sends anything off the NAS. Passport, ID, and card numbers are left out of the summary.

How I built it

I built it with Claude and the official UGOS Skill Creation Tool (version 0.7.3). I checked the idea against the kit's capability catalog before writing anything, so every step maps to a real capability.

The skill is a single SKILL.md that chains four registered experts across five capabilities:

• photo-agent for the photo search and the album
• file-agent for finding and gathering the documents
• document-agent for extracting the facts
• knowledge-agent for saving the summary

Each delegation is self-contained and only receives what the previous step really returned. A plain-language user guide lives in references/.

Challenges

• Guide versus checker. The starter guide recommends a root README.md, but the kit's checker rejects any root file other than SKILL.md. I moved the user guide into references/.
• Template versus checker. Some section headings in the kit's own template are not the ones the checker looks for, so I matched the checker.
• Partial trips. A trip can have photos but no documents, or documents but no photos. Each case needed its own honest path instead of one all-or-nothing flow.
• Money. Trips often mix currencies. The summary totals each currency separately and does not convert.

What I learned

• Writing a skill is mostly about deciding what happens when nothing is found, and where the user must say yes.
• Passing only real results between steps is what keeps a multi-step flow from inventing data.
• Reading the checker itself was more reliable than reading the guide.

Current status

The skill passes the kit's static checker with 0 errors and 0 warnings. It has not yet run on a real NAS, since the test environment is for finalists.

What's next

• Test on a real device and tune the document search words.
• Read photographed receipts with OCR so paper receipts count toward costs.
• A year-in-review mode that builds a dossier for every trip in a year.

Built With

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