Client Handoff Check

Check promised deliverables against actual NAS files before sending a client handoff.

Comment

Client Handoff Check

The problem

A freelance designer can finish the creative work and still overlook a promised export. The approved brief says what should be delivered; the project folder shows what exists. Checking the two by hand is repetitive and easy to rush.

What the Skill is designed to do

Client Handoff Check compares one approved brief with one authorized NAS delivery folder and produces an evidence-linked checklist.

Each explicit requirement receives one of three outcomes:

  • Found: a unique named file has verified presence, type and non-zero size.
  • Missing within checked scope: the promised named file is absent from a completely checked scope.
  • Needs review: a name is ambiguous, evidence is incomplete, or the requirement needs human judgment.

The checklist retains source excerpts, actual file evidence and coverage limitations. File presence is not a judgment of visual quality, valid file contents, freshness or client approval.

Workflow

The user chooses the governing brief and delivery scope. The document expert extracts explicit requirements. The file expert inventories authorized files. The parent Skill connects the verified results and explains gaps. After reviewing the exact report, the user may approve saving it outside the delivery folder.

The check does not move, rename, delete or send source files. A changed report or destination requires renewed save approval.

Implementation

This entry is a newly authored Markdown orchestration Skill following the official Uliya development standard. It uses:

  • ug-document / document-agent for document reading and requirement extraction.
  • ug-filesystem / file-agent for scoped file discovery and metadata.
  • ug-knowledge / knowledge-agent for approved report saving.

The parent delegates supported NAS work to registered experts. The package contains SKILL.md and four directly linked Markdown references, with no custom executable or runtime library.

Current status

The official creation-kit checker reports static-pass with zero errors and zero warnings. The Skill, matching rules, report format, failure handling, disclosures and validation plan are authored.

Installation and actual NAS behavior have not yet been tested. Static validation does not prove device execution, model behavior, expert output compatibility or save collision protection.

Finalist validation plan

Use a synthetic brief explicitly requesting five files. First check a complete delivery. Then check a delivery missing two exports, add them and rerun with fresh evidence. The edge case makes a subfolder unreadable; the Skill must report uncertainty instead of an all-clear.

Also verify empty results, ambiguous matches, cancellation, pending approval, unchanged source files, destination collisions and verified report-save completion.

AI assistance and third-party tools

Codex assisted requirement analysis, Skill authoring, documentation, static validation and local artifact production. The official UGREEN uliya-skill-kit 0.7.3-en and its catalog 2.0.0 supplied development guidance and the checker; no kit code is redistributed. Uliya experts are proprietary platform dependencies under the applicable terms.

ElevenLabs generated narration for a separate concept preview, which was assembled and exported in Wondershare Filmora. ReportLab, Pillow and FFmpeg produced separate local PDF, image and storyboard assets. Their sources and licenses are disclosed in the proposal and Skill references. These production tools are not runtime dependencies.

The concept preview contains illustrative cards, not real NAS footage. The Round 2 demonstration will be recorded on the assigned NAS during the testing day.

Data and limitations

Only the user-approved sources and directory scope may be processed through supported platform capabilities. Local processing is preferred when available; offline-only operation has not been established. No direct external API endpoint or credential is configured by the Skill.

Unknown coverage, extraction failures and concurrent edits limit conclusions. Broader requirements without explicit names remain visible for human review.

Project links

Built With

Share this project:

Updates

Submission history