Final Version Finder

Inspiration

Every shared folder ends up with the same problem: Proposal_final.docx, Proposal_FINAL_v2.docx, Proposal_v2_Mark.docx, and one more copy in someone's Downloads. Nobody knows which one is real. In a 2026 Smallpdf survey of 1,002 US employees, 35% were delayed by version confusion three or more times in a single month, and 60% had to rebuild a document from scratch.

Existing tools do not solve this. Snapshots track one file over time, but these are separate files with different names. Search finds names, not history. Duplicate finders only catch identical files. A phone assistant sees one device. A NAS is the one place where every copy from every person already sits together.

What it does

You ask: "Which is the final version of the Q3 proposal?" The Skill:

1. Finds every copy across the NAS, by name and by content, including renamed copies.
2. Compares the copies and rebuilds the lineage: which copy came from which, and what changed.
3. Recommends one final with its reasons, or reports a split when no single copy is complete.
4. Warns when edits exist only in another copy, for example a section that never made it into the final.
5. After you confirm, tags the final, moves drafts into a _versions folder (nothing is deleted), and saves a VERSION-HISTORY.md.

On a second run it reads that history, checks only new or changed copies, and warns about edits made after the final was confirmed.

How I built it

The Skill follows the Uliya Skill Development Standard. SKILL.md delegates each step to UGREEN's registered experts: file-agent for search, checksums, folders, moves and tags; document-agent for content lookup and version comparison; knowledge-agent for saving the history. Each step uses only the real result of the previous one. Every capability was confirmed against the public capability catalog in the UGOS Skill Creation Tool, and the package passes the static checker with 0 errors and 0 warnings.

Challenges

• Choosing the final without guessing. Newest date fails (copying changes dates), longest file fails (sections get cut on purpose), and the name "final" fails (several files carry it). The Skill uses a fixed order: content lineage, then status markers inside the text, then dates only as a tie-breaker.
• Safety. It never deletes, never moves files in another user's personal space, and sends every change through the NAS approval flow.
• Honesty about limits. If a file's content cannot be read, the Skill says so and lowers its confidence instead of pretending it compared it.

What I learned

A useful Skill is mostly decision rules and failure handling. The happy path is short; the edge cases (split copies, unreadable formats, refused approvals, a hand-edited history) are where it earns trust.

What's next

Validate per-format readability on a real UGREEN AI NAS, then extend from one document per run to a folder-wide version audit.

Built With

• claude
• file-agent
• mattpocock-skills
• ugos
• ugreen-ai-nas
• uliya-skill