Paperless-ngx

**Judgement**: This skill is strong and practical for users who already run a Paperless-ngx instance. It exposes most of the important REST API endpoints, allowing an assistant to fully manage documents and their organization. **What it does well** - Enables robust document management: search, upload, download (original and OCR’d), and metadata updates. - Supports organizational structures (tags, correspondents, document types) and bulk operations, which is critical for keeping large archives tidy. - Uses simple, standard HTTP with token auth and clear pagination/ordering patterns, so behavior should closely match the Paperless-ngx API documentation. **Key risks / limitations** - **Destructive operations**: The skill supports deleting individual documents and bulk delete via `bulk_edit`. If misused, the assistant could permanently remove documents or apply unwanted bulk changes. - **Privacy/security**: Access requires an API token with potentially broad permissions. Any compromise of that token would expose or allow modification of sensitive documents. - **Environment-specific**: Only useful for users who already have a reachable Paperless-ngx server and a valid API token; not applicable outside that context. **Recommended scenarios** - You use Paperless-ngx as your central document archive and want the assistant to handle practical tasks such as filing new PDFs, finding past invoices, or tagging documents by project/client. - You need help maintaining order at scale (e.g., bulk tagging, changing document types, or reprocessing documents after OCR/processing configuration changes). - You are comfortable granting the assistant write/delete access to your archive and ideally have backups or retention policies in place to mitigate accidental destructive actions.