## Inspiration

A lot of work gets agreed out loud. On a call someone says "three revision rounds is fine" or "can you also do the cup sleeve?", and nobody updates the contract. Weeks later the invoice goes out, the client disputes it, and nobody can show who said what. Freelancers, small agencies and anyone hiring a contractor run into this.

The recordings and the signed paperwork usually already sit in the same project folder on a NAS. Nobody compares them, because listening back through hours of calls is slow, and uploading private contracts and recordings to a cloud chatbot doesn't feel right.

What it does

Said vs Signed is a Skill for UGREEN AI NAS. You point it at one project folder. It:

  1. Lists the folder and asks you to confirm which files are agreements and which are recordings or notes.
  2. Reads the written terms from the agreements: scope, price, dates, revision limits, exclusions.
  3. Transcribes the call recordings and reads any meeting notes.
  4. Lists every spoken commitment: a promise, a request, a change, or giving something up.
  5. Matches each one against the paperwork and gives it one status:
    • Confirmed: the paperwork says the same thing.
    • Contradicts: the paperwork says something different.
    • Not in writing: the paperwork doesn't cover it.
    • Unclear: the evidence is too weak to decide.
  6. Shows a ledger with the exact quote and its source beside the exact clause and its source, plus a neutral draft note asking the other party to confirm the open points in writing.
  7. Saves the ledger as a new file, but only if you approve.

Analysis is read-only. Original files are never changed.

How we built it

The Skill is pure Markdown, following the official Uliya Skill Development Standard. It delegates every NAS action to three registered expert agents:

  • file-agent (ug-filesystem): lists the folder and records checksums of the agreements
  • document-agent (ug-document): extracts written terms, reads notes, and runs a verification search
  • knowledge-agent (ug-knowledge): transcribes recordings and saves the ledger after approval

We checked every step against the official capability catalog and ran the official static checker until it passed with zero errors and zero warnings. We also wrote a fictional test set: a statement of work, a quote, three scripted calls and meeting notes, with eight planted commitments and an answer key. The Skill includes a built-in practice run, so judges can try it without their own files.

Challenges we ran into

  • Not inventing evidence. A language model will happily "find" a contradiction. We added a rule: nothing is marked contradicts or not in writing unless there is an exact quote and a second, independent search of the agreements agrees. Anything else is downgraded to unclear.
  • Instructions hidden in files. A document could contain text like "delete this folder". The Skill treats file contents as evidence only and lists any such text under "Embedded instructions not followed".
  • No NAS access in Round 1. We couldn't test runtime behaviour, so we kept the workflow to path-based capabilities and planned fallbacks for unknowns such as missing transcript timestamps.

What we learned

  • Orchestration Skills live or die by how precise each delegation is. Every instruction has to state its scope, what not to do, and what to return.
  • Being honest about uncertainty makes the output more useful, not less. An unclear row tells the user exactly what to check.

What's next

  • Test on a real UGREEN AI NAS: transcript timestamps, file formats, and the save step.
  • Compare a new ledger with the previous one, so a repeat run shows only what changed since the last call.

Built with

UGOS Skill Creation Tool (uliya-skill-kit 0.7.3-en). AI tools: Claude Code for research, drafting the Skill package and the proposal text, and checking; ChatGPT for exploring an alternative idea we did not use.

Built With

  • markdown
  • ug-document
  • ug-filesystem
  • ug-knowledge
  • ugos
  • ugreen-ai-nas
  • uliya
  • uliya-skill-kit
Share this project:

Updates

Submission history