Inspiration

A restore finishes. The files are back in a folder. But did the documents you actually need come back as expected?

Restore Rehearsal started with that question. Households and freelancers need a practical way to rehearse recovery before an emergency. Comparing an older backup with today’s originals can also be confusing: a difference might reflect a legitimate edit rather than a recovery problem.

What it does

Restore Rehearsal is a Uliya Skill designed to guide users through checking a small, important selection of restored files on UGREEN AI NAS.

The user names a reference folder and an already restored folder, then optionally selects priority files. The workflow compares file sizes and SHA-256 fingerprints and presents an evidence-linked report showing matches, differences, and items it could not check.

Users can approve saving a fingerprint record for another rehearsal later. That record provides a comparison baseline even after the original files change.

How I built it

The pre-test package contains a Markdown Skill and two linked references defining comparison rules, limits, and disclosures.

The workflow delegates supported NAS operations to registered expert agents: file discovery and hashing, optional document or media metadata checks, and saving an approved report. Uliya’s configured model coordinates the workflow and explains the returned evidence.

Development used the UGREEN Skill Developer Package. Cursor assisted with the Skill and checks, Grok supported research, and ChatGPT helped refine the proposal.

Challenges

The hardest design problem was deciding what each result actually proves.

Different bytes do not automatically mean corruption. An access error does not mean a file is missing. Matching fingerprints do not prove that a document opens correctly. The workflow keeps those distinctions visible and reports incomplete coverage.

Accomplishments

The Skill instructions, reusable record workflow, comparison rules, and failure handling are written. The ZIP passes local structure, size, frontmatter, and reference-link checks.

This is a pre-test submission. Installation and actual execution on UGREEN AI NAS remain unvalidated.

What I learned

A useful recovery report needs clear evidence and an actionable next step. Its value comes from helping someone understand a small rehearsal and repeat it later.

What’s next

On the assigned NAS, I plan to test identical files, a restored file checked against an earlier record after its original changes, and denied folder access. I will also validate permissions, report saving, and repeat-use behavior.

The initial scope stays deliberately small: up to 20 files per side. Restore Rehearsal checks an existing restored copy; it does not perform restores or delete files.

Built With

  • cursor
  • grok
  • markdown
  • sha-256
  • ugos
  • ugreen-ai-nas
  • uliya
Share this project:

Updates

Submission history