process-[sua-empresa]-inbox

Scan, classify, extract insights, and route inbox files to destinations.

79|33|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/thiagofinch/mega-brain --skill process-sua-empresa-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-[sua-empresa]-inbox
Source: https://github.com/thiagofinch/mega-brain/tree/main/.claude/skills/process-company-inbox
Command: npx skills add https://github.com/thiagofinch/mega-brain --skill process-sua-empresa-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatiza o processamento de conteúdos internos da INBOX da empresa, simplificando a organização, extração de insights e movimentação para destinos designados.

Core Features & Use Cases

  • Varredura da INBOX para identificar arquivos não processados
  • Classificação por tipo e categoria de conteúdo
  • Extração de CHUNKS e INSIGHTS relevantes
  • Movimentação para pastas destino e atualização de _INDEX.md e [SUA EMPRESA]-STATE.json
  • Geração de logs de pipeline em /logs/[SUA EMPRESA]-PIPELINE/

Quick Start

Execute o pipeline de processamento da INBOX da empresa para começar a processar novos arquivos.

Frequently Asked Questions about process-[sua-empresa]-inbox

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

FAQPage Schema
How do I automate company inbox processing and file classification?

Automating company inbox processing involves running a deterministic workflow that scans new files, classifies content, extracts insights, and routes items to designated destinations. This pipeline updates contextual artifacts like _INDEX.md and state JSON files while generating processing logs.

What is the best way to extract insights from internal inbox files?

Extracting insights from internal inbox files is handled by a structured pipeline that scans your /[empresa]/inbox/ directory, classifies content types, and pulls relevant chunks. The workflow automatically moves files to target folders and logs the extracted insights for knowledge management.

How does deterministic file routing work for knowledge management pipelines?

Deterministic file routing for knowledge management works by enforcing a strict SCAN, CLASSIFY, EXTRACT, MOVE, INDEX, and LOG sequence. This ensures files appearing in the inbox are processed predictably, backed up non-destructively, and routed to exact designated destinations.

Do I need external dependencies to run the inbox indexing workflow?

No external dependencies are required to run the inbox indexing workflow. The processing pipeline operates autonomously to scan files, update the _INDEX.md file, and maintain the state JSON file without relying on external components or scripts.

Can I process scripts and references alongside standard inbox files?

Yes, you can process scripts and references alongside standard inbox files. The pipeline includes optional support for these asset types during the extraction and classification phases, ensuring they are routed and indexed appropriately within the knowledge management system.

What happens to original files after inbox processing and extraction?

Original files are preserved using non-destructive backups after inbox processing and extraction. Once insights are extracted and contextual artifacts are updated, the workflow moves the processed items to designated destination folders while maintaining the backup integrity.