paperless-classify

Classify Paperless-ngx inbox documents by extracting OCR text and assigning metadata.

12|Updated Jun 22, 2025
One-click install
npx skills add https://github.com/rcdailey/home-ops --skill paperless-classify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperless-classify
Source: https://github.com/rcdailey/home-ops/tree/main/.opencode/skills/paperless-classify
Command: npx skills add https://github.com/rcdailey/home-ops --skill paperless-classify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you quickly triage and organize Paperless-ngx documents by turning raw OCR text into consistent metadata, so you stop manually guessing correspondents, types, tags, and titles.

Core Features & Use Cases

  • Inbox-first classification workflow: Review documents that still carry the inbox tag and classify them with human-visible context for accuracy.
  • Metadata assignment with taxonomy alignment: Assign correspondent, document type (finite set), tags, and a normalized title using your existing taxonomy conventions.
  • Bulk application + safety rails: Apply classifier decisions in batches from structured stdin, remove the inbox tag on update, and prompt for creation only when taxonomy gaps require it (with correspondent always created automatically).
  • Compact-to-full content strategy: Use brief (compact content) for most docs, then selectively re-run with full content for ambiguous cases to improve classification quality.

Quick Start

Use the paperless-classify skill to review and classify your inbox documents by running the classify inbox flow.

Frequently Asked Questions about paperless-classify

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

FAQPage Schema
How do I automatically classify Paperless-ngx inbox documents using OCR content?

Paperless-ngx document classification supports bulk batch updates from stdin using pipe-delimited fields. This allows you to process multiple documents at once, removing the inbox tag and preserving existing metadata when optional fields are omitted from the input.

What is the best way to handle ambiguous documents during Paperless-ngx taxonomy assignment?

For ambiguous documents during taxonomy assignment, use a compact-to-full content strategy. Run the classifier initially with brief content for most docs, then selectively re-run with full content analysis on ambiguous cases to improve classification quality and accuracy.

Do I need a prepopulated taxonomy to classify documents in Paperless-ngx?

Yes, you need a prepopulated taxonomy and the inbox tag workflow enabled before classifying documents. The classifier aligns assignments to your existing taxonomy conventions, prompting for creation only when taxonomy gaps require it, while correspondents are always created automatically.

Can I preserve existing metadata when updating document types and tags in Paperless-ngx?

Yes, existing metadata is preserved when fields are omitted during updates. The classifier CLI interface ensures that bulk batch updates only modify the fields you explicitly provide, removing the inbox tag while leaving other correspondent, type, and tag assignments intact.