File car receipts with a proposed destination and no overwrites
At a glance
Will Pike's Claude Code filing skill extracts receipt text, proposes a service folder, and moves the files after confirmation. This workflow is listed under Life Admin, Document Filing, Car Maintenance.
- Agents / tools
- Claude Code, Docling, Local filing skill
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Prepare Claude Code with filesystem access, a local Docling service at localhost:5001, and a filing skill containing destination rules, filename conventions, and duplicate handling. Pike's skill is named ingest-inbox. 2) Put the receipt PDF in Documents/Car/inbox. His email pipeline also supplies metadata, download provenance, and extracted-text sidecars. 3) Request the Car inbox operation. Resolve it to Car subtree mode; reuse existing extracted text or run Docling for PDFs without it. 4) Identify the receipt and compare destination copies before proposing a dated service folder and descriptive PDF name. Keep sidecars with the document; route duplicates to _duplicates for review. 5) Confirm the proposal, then move with mv -n so an existing file is not overwritten.
How it went
The worked example filed a Valvoline receipt for the author's Forester into its dated service folder.
Worth knowing
The custom skill and Docling service are prerequisites. The article describes their rules, rather than supplying a complete installation package.