Inspiration

Research usually starts with a question and ends with a folder full of documents. The difficult part is turning those files into a decision you can explain.

While planning Dossier, I used a small perfume-business research scenario: supplier quotations, ingredient notes, launch plans, and compliance documents. A summary alone would not be enough. I would want to know where a price came from, whether two statements really conflict, and which files the assistant could not read.

That became the idea behind Dossier: a research brief that shows its working instead of hiding uncertainty.

What it does

Dossier is a UGREEN NAS Skill designed to turn an authorised folder of documents into a source-attributed Markdown research dossier.

The user provides a research question, a source folder, and a destination folder. Dossier inventories candidate files, attempts document processing separately for each source, and builds its findings from successfully obtained evidence.

When at least two documents are successfully processed, it compares them for candidate contradictions, unresolved discrepancies, and information gaps. It then requests a draft, checks the claims against the accepted evidence, and saves only a reviewed dossier through the approved NAS workflow.

The report separates supported findings from processing limitations. Source paths are retained, and precise locations are included only when the runtime actually returns them.

How I built it

I built Dossier using the official Uliya Skill creation kit and its published capability catalog.

The workflow delegates to three registered experts:

  • file-agent for folder inventory
  • document-agent for extraction, comparison, and drafting
  • knowledge-agent for saving the accepted report

The Skill uses only four actions: ug-filesystem/ls, ug-document/qa, ug-document/writing, and ug-knowledge/save-text.

I kept evidence collection separate from drafting. The drafting stage receives accepted evidence and processing records as text, rather than being asked to independently rediscover the research. A review gate checks source support, locators, coverage disclosures, and unsupported conclusions before saving.

Codex assisted review & validation.

Challenges I ran into

The biggest challenge was separating what the catalog documents from what still needs to be verified on a real device.

An available action does not guarantee support for every document format, complete extraction, clickable citations, or a particular approval experience. I revised the design to avoid promising those things.

Another challenge was defining a contradiction properly. Different suppliers offering different prices are not necessarily disagreeing. Dossier must preserve differences in supplier, date, quantity, and conditions before presenting a candidate discrepancy.

I also separated document coverage from folder coverage. Processing every selected document does not prove that a bounded folder inventory found everything.

Accomplishments I am proud of

Dossier now has a complete Skill specification, a linked user guide, a synthetic research corpus, and a packaged Round 1 submission.

The working package and independently extracted ZIP passed the official static checker with zero required errors. One warning remains because the checker cannot mechanically validate the dynamically assembled delegation instructions.

I am particularly pleased with the evidence rules: unread or failed sources cannot quietly become supporting facts, and a successful save is never presented as proof of complete research.

What I learned

The most useful research assistant is not necessarily the one that produces the most confident answer. It is the one that makes the evidence, uncertainty, and unfinished work easy to inspect.

I also learned to treat static validation and runtime validation as separate milestones. The local kit supports authoring and checks, but it does not execute the NAS workflow.

What's next for Dossier

Target NAS execution remains untested.

If selected for Round 2, I will validate the complete workflow on the assigned UGREEN NAS: delegation, supported formats, returned evidence, comparison, content-only drafting, approvals, and saving.

Planned tests include genuinely conflicting statements about the same supplier and item, a readable document with no relevant evidence, and a folder with no eligible documents.

The goal is not to add more features immediately. It is to demonstrate a reliable end-to-end workflow that produces a useful research dossier while being honest about what it could and could not establish.

Built With

Share this project:

Updates

Submission history