auto-bean-process

Process one raw statement into normalized parsed evidence via Docling CLI.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/SamArgt/auto-bean --skill auto-bean-process
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-bean-process
Source: https://github.com/SamArgt/auto-bean/tree/main/skill_sources/auto-bean-process
Command: npx skills add https://github.com/SamArgt/auto-bean --skill auto-bean-process

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process exactly one assigned raw statement file into normalized parsed evidence through the local Docling CLI. Use as the auto-bean-import raw-to-parsed worker stage. It owns parsing, process artifacts, per-input parse status updates, and processing memory suggestions; auto-bean-import owns work discovery, first-seen accounts, posting workflows, and finalization.

Core Features & Use Cases

  • Raw-to-parsed processing: transforms a single raw statement into a structured parsed representation using Docling
  • Per-input artifacts and status: tracks parse run, status, and related process artifacts under the workspace
  • Memory-driven guidance: surfaces memory suggestions and defers beyond the input to the main import workflow

Quick Start

Assign one raw statement from statements/raw/ to this skill to produce a normalized parsed output under statements/parsed/ and update the corresponding import-status entry.

Frequently Asked Questions about auto-bean-process

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse a raw bank statement into structured data for Beancount?▼

To parse a raw statement into structured data, a worker skill processes the assigned file using the local Docling CLI. It validates the input format, generates a deterministic parse run ID, and stores the normalized output under statements/parsed/.

What is the best way to track the parsing status of individual financial statements?▼

Tracking parsing status is done by a per-input worker that updates the import-status entry and writes process artifacts. It assigns a deterministic parse_run_id and stores processing metadata under .auto-bean/artifacts/process.

Does the auto-bean-process worker handle the entire Beancount import workflow?▼

No, it does not handle the entire import workflow. It only processes one assigned raw statement into parsed evidence, while the broader auto-bean-import workflow handles work discovery, first-seen accounts, posting workflows, and finalization.

Can I use Docling to validate input formats before processing a ledger statement?▼

Yes, the worker validates input formats before processing. It checks the raw statement file before using the local Docling CLI to transform it into a normalized parsed representation and writing the corresponding process artifacts.

How do memory suggestions work when parsing statements with Docling?▼

Memory suggestions work by surfacing processing guidance during the raw-to-parsed stage. The worker provides memory-driven suggestions for the individual input but defers any broader orchestration or finalization tasks to the main import workflow.

Why should I use a separate worker for parsing instead of processing all statements at once?▼

Using a separate worker ensures deterministic processing and isolated status tracking for each file. It processes exactly one assigned raw statement, writes a specific parse_run_id, and prevents one failed input from blocking the entire import workflow.