curador

Classify local document batches into approved ERP knowledge ingestion outputs.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill curador
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curador
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/curador
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill curador

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, mjs, and includes scripts (resource) components.

What problem does it solve?

Curador turns messy, large document collections into an organized, policy-compliant knowledge ingestion workflow that a human can approve before anything is applied to the repo or memory.

Core Features & Use Cases

  • Heuristics-first ingestion pipeline: discovers, classifies, and generates a human review report using deterministic rules first, with Claude applied only to ambiguous cases.
  • Safety-first batch approvals: blocks sensitive material and enforces approval before any commit, move-to-repo, or apply step happens.
  • LGPD consent controls for multi-user scans: prevents scanning another developer’s local folders without a recorded opt-in consent entry.
  • Targets the right outcomes: moves sensitive files to a vault-pending location, quarantines discardable items, and routes memory/spec outputs into the correct git/MCP pathways.

Quick Start

Ask the AI: /curador scan D:\Conhecimento\triagem --user wagner

Frequently Asked Questions about curador

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

FAQPage Schema
How do I batch process and triage large directories of PDFs for knowledge ingestion?

Yes, you can batch classify manuals and PDFs by running a recursive directory scan that applies deterministic heuristics first, then uses Claude for ambiguous items. The pipeline generates a human review report and requires approval before routing files to memory or git repositories.

How does document triage handle sensitive files during batch processing?

Batch processing handles sensitive files by blocking them from standard ingestion and routing them to a vault-pending location. The system enforces safety approvals and quarantines discardable items before any commit or memory update occurs.

Do I need user consent to scan local folders belonging to another developer?

Yes, LGPD consent controls require a recorded opt-in entry before scanning another developer's local folders. The system prevents directory triage and batch processing of other users' paths without this explicit consent.

What is the best way to classify ambiguous items during batch document ingestion?

The best way to classify ambiguous items during batch document ingestion is a two-step pipeline applying deterministic heuristics first, then invoking Claude only for unresolved items. This ensures safe ingestion outputs while minimizing AI processing overhead.

Can I use Node.js scripts for recursive directory triage and file classification?

Yes, you can use Node.js scripts for recursive directory triage and file classification. The pipeline relies on Node and MJS modules to execute deterministic heuristics, track file states in JSONL files, and route outputs to git or MCP pathways.

Why does batch processing require an approval gate before applying files to the repo?

Batch processing requires an approval gate to ensure policy-compliant knowledge ingestion. It blocks sensitive material and prevents automatic commits, requiring human review of the generated report before any move-to-repo or apply step happens.