Inspiration
When a contractor overcharges or an insurer asks for proof, the evidence is already at home, spread across folders, phone backups, voice memos and cameras. People spend evenings searching and still miss things, and few will paste a private contract or camera footage into a cloud chatbot.
What it does
Case File builds a case file from the sources the user approves. It has five parts: Coverage (what was searched, failed or not searched), a Timeline in which every fact cites its file and exact location, Conflicts between sources, Missing evidence for this type of case, and an Evidence register with the SHA-256 of each cited file as it was read, with the reason for any file that could not be hashed. Later, "Update my case" adds what is new from the saved scope, and "Has any evidence changed?" compares the hashed files with the register and says which could not be checked.
How it works
SKILL.md only delegates, to five registered NAS experts. Each instruction is self-contained and passes only real results. Everything before saving is read-only, and writes wait for approval. Files are hashed before reading and rechecked before saving, so facts stay tied to the version read. Cameras and recordings are opt-in, cameras are queried only on dates the other evidence names inside the approved period, camera events sit outside the register, and the Skill uses no face or plate recognition. The Skill adds no outside services. Where each expert processes content is not yet verified, so users choose local-only or allow-unknown before anything is read.
Status
Passes the official static checker with 0 errors and 0 warnings. Not yet run on a UGREEN AI NAS. See references/example-case-file.md for a fictional, hand-written example of the finished file.
Built With
- markdown
- skill
- ugos
- uliya-skill-kit
