Inspiration

Family NAS owners often scan warranties, invoices, and repair papers onto the NAS, but still cannot find them when an appliance fails. Non-technical relatives will not browse folders, so the evidence sits unused. Cloud chat can invent warranty dates; a generic extract-then-archive pipeline stops short of answering the question.

What it does

household-evidence-qa is a local UGOS Skill for answer-first, cited Q&A on household warranties, bills, home contracts, and repairs. It searches only an authorized NAS scope, reads documents (with optional photo OCR or audio), and returns a plain-language answer with path and snippet citations in a Direct / Evidence / Coverage structure. It is honest about empty, partial, conflict, and location-only evidence. Optional archive stays in waiting_approval. It is not for music, surveillance, firmware, or general chat.

How I built it

The Skill is built with the official UGREEN Skill Developer Package (uliya-skill-kit, capability catalog 2.0.0). The parent Skill only delegates; it never calls cli.invoke. The flow is: confirm scope → file-agent discovery → document-agent cited Q&A → optional photo-agent or knowledge-agent → compose under a hard citation rule → optional archive behind confirmation.

Capabilities used:

  • ug-filesystem / file-agent: read-only discovery; approved writes only in archive mode
  • ug-document / document-agent: cited Q&A and field extract after real paths exist
  • ug-photo / photo-agent (optional): picture search and OCR for receipts
  • ug-knowledge / knowledge-agent (optional): evidence collect and audio transcription

Challenges and current status

The hard rule is that every factual claim needs an expert-returned path and snippet—no invented merchants, amounts, dates, or paths. Empty expert results stop later steps; a location-only request skips content extraction.

Round 1 static checks have passed (SKILL.md, citation and refusal rules, example scenarios A–I). check-skill.mjs reports 0 errors/warnings. Live NAS validation (receipt recall, archive UX, timing) is pending and is not claimed as verified in Round 1. Known limits: it cannot fix Sync, Backup, encryption, or firmware; OCR quality depends on NAS experts; an explicit authorized scope is required.

Built With

Share this project:

Updates

Submission history