Inspiration
A family can back up several phones to one NAS. A phone's backup can stop, for example on low battery or limited photo access, and it can go unnoticed because the other phones keep the library growing. We wanted a Skill that answers one question: which device has gone quiet, and since when?
What it does
Photo Gap Check reads monthly photo counts per camera model, names the device that stopped arriving and any empty months, and, given an earlier report, says what has arrived since. Each device gets one label: "Needs a look," "Explained," "Fine," or "Not enough history."
How we built it
The Skill is Markdown only: a SKILL.md and five reference files. It delegates to UGREEN's built-in experts (photo, file, document, and knowledge agents) and is read-only except one optional saved report.
A device gets "Needs a look" when at least six active months are followed by two or more empty months. If another device started arriving within one month of that stop, the label is "Explained" instead, since the family likely switched phones.
We used Claude through Claude Code to read the kit documentation, compare ideas, draft the files, and run reviews. We chose the idea and reviewed the files.
Challenges we ran into
- No NAS in Round 1. Every rule was written against the capability catalog alone.
- No device list. The Skill finds devices from sample photo metadata and asks the user to confirm them.
- One state per device. Our first rules overlapped, so we rewrote them as one ordered procedure.
Accomplishments that we're proud of
- The package passed UGREEN's official checker with 0 errors and 0 warnings.
- Every step maps to a capability in the official catalog.
What we learned
The hard part of a Skill is wording: telling each expert exactly what to return so the parent can check it.
What's next for Photo Gap Check
If we reach the finals, we will build the synthetic photo set from our validation plan and run our test cases on the assigned NAS.
Built With
- markdown
- ugos
- ugreen-ai-nas
- uliya