Inspiration

Small accounting and bookkeeping firms spend a huge portion of tax season chasing missing client paperwork. Clients drop poorly named PDFs and phone scans (IMG_0024.pdf, scan_final_2.pdf) into shared folders. Because those folders hold tax returns, bank statements, and contracts, firms keep them on local storage rather than uploading client folders to public cloud chatbots.

While researching how NAS owners feel about local AI on r/UgreenNASync, we also saw a clear concern: people do not want an AI moving, renaming, or deleting their original files. At the same time, almost every AI document tool only summarizes what is already in a folder. Bookkeepers need the opposite — a tool that checks a folder locally and tells them what is missing without touching the originals.

What it does

Tickmark (tickmark) is a Uliya Skill for UGREEN AI NAS that audits a client's year-end folder against a plain-text checklist owned by the firm (checklist.txt).

When a bookkeeper asks Uliya in chat: "Check 2026 Smith Corp against our checklist", Tickmark runs a 4-step workflow:

  1. Inventory & Checklist Read (file-agent / ug-filesystem): Lists up to 50 documents in the client folder in read-only mode (find, ls) and reads the firm's checklist.txt (cat).
  2. Classification & Cited Extraction (document-agent / ug-document): Inspects document metadata and page counts (metadata, page-count), classifies bank statements, contracts, invoices, receipts, and tax forms (extract), records exact filenames and page numbers, and flags blurry or low-confidence scans.
  3. Contract-to-Invoice Reconciliation (document-agent / ug-document): Runs reconcile to compare matched invoice totals against contract amounts and reports any numeric differences with source filename and page citations.
  4. Gap Report & Unsent Chase Draft (knowledge-agent / ug-knowledge): Under platform waiting_approval, saves two review files into a separate audit-summary/ subfolder (save-text):
    • gap-report.md (Present & Verified, Missing from Folder, Contract vs. Invoice Discrepancies, and Needs Manual Check)
    • draft-client-email.txt (an unsent plain-text follow-up email ready for the bookkeeper to review)

Finally, Uliya replies in chat with a 4-line summary. All original client files remain untouched, and no email is ever sent automatically.

How we built it

We built Tickmark using UGREEN's official uliya-skill-kit (v0.7.7) and capability catalog (v2.2.0):

  • Skill Definition (tickmark/SKILL.md): Written using single-quoted delegate --target <agent> --instruction '...' calls across file-agent, document-agent, and knowledge-agent, passing only verified upstream paths and extracted figures to downstream steps.
  • Reference Specification (tickmark/references/checklist-and-report-format.md): Defines the checklist.txt format, the three-part fallback prompt via waiting_user when a folder has no checklist, mandatory filename + page citation rules, and the output templates for gap-report.md and draft-client-email.txt.
  • State & Boundary Handling: Explicitly handles completed, failed, cancelled, waiting_user, and waiting_approval, plus empty directory stops (zero matches) and partial reads.
  • Automated Verification (scripts/build-and-verify.mjs): Validates tickmark/ and the extracted tickmark.zip against UGREEN's official check-skill.mjs static checker (static-pass, 0 errors, 0 warnings, 0 info).

Challenges we ran into

  1. Hardcoded tax law vs. firm-owned checklists: Our earliest concept checked for a fixed US 1099 reporting threshold. We quickly realized tax thresholds change over time and vary by country. We redesigned Tickmark around a plain-text checklist.txt that any firm in any country can edit without touching the Skill.
  2. Handling imperfect OCR honestly: If a blurry scan causes OCR to misread $3,800 as $3,300, a blind math check will output a confident wrong number. Instead of claiming guaranteed accuracy on raw scans, we designed Tickmark so every finding cites its exact filename and page number, and any shaky or unreadable scan is routed into Needs Manual Check for a 5-second human review.
  3. Strict static checker compliance: UGREEN's check-skill.mjs enforces strict rules against unquoted placeholders, shell commands outside delegations, and conflating save-text completion with search index readiness. Iterating against the checker helped us tighten every instruction string.

Accomplishments that we're proud of

  • Putting UGREEN's built-in ug-document (extract and reconcile) and ug-knowledge (save-text) capabilities to work on a real daily bottleneck for small accounting firms.
  • Designing a "negative-space" audit that finds what is missing from a folder while keeping 100% of original client files read-only.
  • Passing check-skill.mjs cleanly with static-pass (0 errors, 0 warnings, 0 info).

What we learned

  • How Uliya's parent-expert model separates workflow routing in SKILL.md from concrete CLI execution inside file-agent, document-agent, and knowledge-agent.
  • Why explicit pause states (waiting_user for missing scope/checklists and waiting_approval before writing files) are essential for building trust on a local NAS.

What's next for Tickmark

In Round 2 on physical UGREEN AI NAS hardware running UGOS Pro, we plan to:

  1. Run end-to-end tests with realistic client folders (11 of 12 monthly bank statements to verify missing-month detection, plus mismatched contract and invoice PDFs to test reconcile).
  2. Stress-test extract and metadata scanned-document detection on skewed, multi-page, and low-resolution scans.
  3. Verify the live waiting_approval prompt and resumption flow when writing gap-report.md and draft-client-email.txt into audit-summary/.

Built With

Share this project:

Updates

Submission history