Inspiration
I build things that keep a record of a life. My other project, Curator, files a day into a life context file, chapter by chapter, and never overwrites anything. Families store years of photos, videos and documents on a NAS and never look at them again — the day's material lands in scattered folders and the story of the day is lost. I wanted a small version of that idea that lives on the NAS itself: say "close out today" and the day gets filed.
What it does
day-chapter closes out one day on a UGREEN NAS as a single chapter. It gathers that day's photos, videos, documents and notes, writes one dated chapter summary as a new file, and creates one album for the day's photos. Only after your confirmation does it move the files into the dated chapter folder. The record is append-only — a later pass writes a second chapter, it never rewrites the first. An empty day is reported as empty, never invented.
How we built it
A UGREEN Skill is not code — it's a Markdown orchestration spec. I downloaded UGREEN's Skill Developer Package (uliya-skill-kit 0.7.3) and read its capability catalog, then wrote SKILL.md plus one reference file describing the chapter format. The Skill delegates in order — photo-agent, file-agent, document-agent, media-agent, knowledge-agent, then photo-agent and file-agent again — each step passing only its verified real result to the next, using only supported NAS capabilities: ug-photo, ug-filesystem, ug-filemgr, file-workflow, ug-document, ug-video and ug-knowledge. Moves, saves and album creation all need user confirmation.
Challenges we ran into
The hard part was learning the format, not the idea. The official checker is strict: a README at the package root is an error, the capability evidence has to be in an exact format, and the orchestration heading has to match its expected names. It took three rounds to get a clean pass. The other challenge is honest: I have no NAS, so the full run on real NAS data is still untested — that's what the finalist round is for.
Accomplishments that we're proud of
The Skill passes UGREEN's official checker clean — static-pass, 0 errors, 0 warnings, catalog version 2.0.0. The proposal answers all ten required items in 492 words, under the 500-word limit. And the core idea survived the format: a chapter is still a chapter, even when it's a Markdown file.
What we learned
A Skill is a promise about a workflow, not a program. Every step has to map to a capability that actually exists in the catalog, every write needs confirmation, and if there's no result you say so and stop — you don't substitute something close. That's a good discipline, and it's the same discipline behind the append-only record.
What's next for day-chapter
Test the full run on a real UGREEN AI NAS as a finalist: a normal day, a day with one photo, and a date with nothing at all. After that, the obvious next step is rolling chapters up — day into week, week into month — the same way Curator does, but on the NAS where the life actually lives.