Inspiration
Small agencies, AV installers and service teams keep customer deliverables in shared project folders. A file called “final” may still be superseded, unapproved or missing customer acceptance. Customer Handoff Check turns that uncertainty into a focused evidence review before a person releases files.
What it does
The proposed Uliya skill reviews an authorized NAS project scope and produces cited findings, per-item blockers and a draft customer manifest. It binds approval and acceptance to the exact file version, checks the intended audience, and excludes internal material. A human reviews and releases the handoff; the skill does not send files or modify source records.
How it is built
The entry is a Markdown skill with directly linked references. Its instructions use file-agent/ug-filesystem for discovery and metadata, and document-agent/ug-document for extraction, questions and reconciliation. Reviews are bounded to 40 files and two searches. The instructions preserve incomplete coverage, errors and resumable waits; unknown model routing stops the review, and cloud use requires permission.
Version-specific repair is central: adding matching approval and acceptance for one item must not clear another item's blocker. The planned B11 test checks that an informal coordinator “OK” changes nothing and that one valid repair leaves the remaining item and overall handoff blocked. A source-dated chronology helps reviewers trace the evidence.
What is verified
The v3 skill and extracted ZIP pass the official Uliya skill-kit 0.7.7 diagnostic with zero errors and zero warnings. Synthetic fixtures and the selective repair/rerun protocol are prepared and their integrity checked. These are local static checks, not model-behavior results.
An owned DXP4800 Plus running UGOS Pro 1.21.1.0016 was inspected, but it does not support Uliya. No Customer Handoff runtime tests were run. There are no measured customer outcomes, latency results or privacy/ACL validation. The optional review interface remains unimplemented.
Next validation
On a supported NAS: capture actual outputs for a clean manifest, B11 selective repair and unreadable approval evidence, then compare against ordinary Q&A.
AI use and sources
New work was authored in November 2026 with Codex assistance for skill instructions, tests and proposal preparation. The package discloses the official toolkit and applicable terms, source-linked chronology inspiration from TableHistory, and unimplemented interface inspiration from Pinrail. No third-party code/assets, toolkit code, external API integration or model weights are bundled. Full disclosures are in the proposal PDF and linked development reference in the ZIP.
