Inspiration
Before writing a line, I read 16,928 public comments from NAS owners on 27 sources, from Reddit and the UGREEN community to bilibili and Chiphell. Three worries kept coming back: safe bulk changes, keeping files and AI under their own control, and help with documents. One user told how an AI agent with Python access batch-renamed their files and overwrote more than 200 videos, with no report and nothing to stop it. Paperwork is where that fear meets a real chore: invoices, receipts and contracts pile up in one NAS folder, and nobody wants to open, read, rename and file each one by hand.
What it does
On a UGREEN AI NAS, the Skill takes one folder of paperwork and:
- reads each contract, invoice and receipt, and quotes the exact line behind every counterparty, date, total and due date;
- shows a plain BEFORE / AFTER preview of every new name and folder, e.g.
Archive/2026/Invoices/2026-03-14_Northwind_invoice_1250.00EUR.pdf; - reads each contract's billing terms and lists the periods it expects, then marks each one received, not found in this folder, amount differs, not yet due, or not enough evidence, quoting the contract clause and any matching invoice line (amounts are compared by the NAS's own
ug-document reconcile); - asks when a document has two totals or two dates, showing both quoted lines, and never guesses;
- leaves anything unreadable in place on a check list;
- after you confirm and the platform approves, moves each file without overwriting, verifies the new path, and saves a before/after ledger with the gap list and a one-time due-date list on the NAS. The next run reuses earlier invoice facts from the latest verified ledger; coverage stays limited to the supplied folder and that ledger.
Nothing is deleted. Before any document is read, the Skill tells you which model reads it and whether content leaves the NAS, as far as the platform reports, and waits for your consent.
How I built it
The Skill is pure Markdown, written against the Uliya Skill Kit 0.7.6 and its capability catalogue. It contains no code of its own, so it orchestrates the NAS's registered experts through delegate: file-agent with ug-filesystem (find, stat, sha256sum, cpmv with overwrite=false), document-agent with ug-document extract and reconcile, and knowledge-agent with ug-knowledge save-text. Normally I would enforce safety with a code hook; here platform approval is my safety hook. A script would normally compute billing periods; Skills may not contain one, so the periods are listed line by line for the user to check. Claude (Anthropic) helped me design the workflow, draft SKILL.md and analyse the user research; I reviewed every decision and the final text.
Challenges I ran into
- Making "nothing is overwritten" true at move time, not only at preview time: the Skill rechecks source and target right before each move.
- Large folders: batches of 60 from a frozen manifest, resumable from the saved ledger without processing a file twice.
- Saying only what the files prove: "not found in this folder" is reported, never "this invoice was not issued".
- Being honest about privacy: storing files on a NAS does not prove local inference, so the Skill states what the platform reports and asks first.
Accomplishments that I'm proud of
The official checker passes with no errors or warnings, every step maps to a real catalogue action, and every value in the preview can be traced to its page and line.
What I learned
Users asked for safe, checkable changes before clever ones, so I kept the Skill deliberately simple.
What's next
If selected as a finalist, I will run three fixture folders on the iDX6011 Pro: a monthly contract with one invoice removed and one amount changed, documents with name collisions, and an unreadable or two-total scan, checking that the ledger matches the real paths and that nothing is overwritten.
Built With
- claude
- markdown
- ug-document
- ug-filesystem
- ug-knowledge
- uliya-skill-kit