inbox-processor

Categorize 00_Inbox notes into PARA destinations and generate an action plan.

2.6k|194|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/heyitsnoah/claudesidian --skill inbox-processor-heyitsnoah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inbox-processor
Source: https://github.com/heyitsnoah/claudesidian/tree/main/.agents/skills/inbox-processor
Command: npx skills add https://github.com/heyitsnoah/claudesidian --skill inbox-processor-heyitsnoah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Inbox Processor helps you organize and triage items in the 00_Inbox folder according to the PARA method, reducing clutter and decision fatigue.

Core Features & Use Cases

  • Scan the Inbox: list all files in 00_Inbox, excluding README.md and Welcome.md.
  • Analyze Each Item: read content, identify type, and suggest a destination.
  • Categorization Rules: route items to Projects, Areas, Resources, Archive, or Delete based on deadlines, ongoing status, material type, or redundancy.
  • Output & Patterns: generate action plan for moves, combinations, deletions, and context needs.

Quick Start

Scan the 00_Inbox/ and categorize items according to PARA rules.

Frequently Asked Questions about inbox-processor

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

FAQPage Schema
How do I organize and triage notes in my Inbox using the PARA method?

To triage notes using the PARA method, this Skill scans your 00_Inbox folder, analyzes each file, and suggests routing items to Projects, Areas, Resources, Archive, or Delete based on content and ongoing status.

What is the best way to automate note categorization for vault-management?

Automating note categorization is achieved by reading inbox content and generating an action plan that details recommended file moves, linkages, deletions, and context requirements to reduce clutter.

How does the PARA workflow handle redundant notes during inbox triage?

During inbox triage, the PARA workflow identifies redundant items and categorizes them for deletion or archiving, producing a specific action plan to remove clutter and manage context.

Can I use this PARA triage workflow on an existing inbox with many file types?

You can use this workflow on an existing inbox because it evaluates various material types and ongoing statuses to route notes appropriately, automatically excluding standard files like README.md.

What are the limitations of automated inbox triage for vault-management?

A limitation of automated inbox triage is that it only produces an action plan recommending moves and deletions; it identifies context requirements but relies on your existing PARA folder structure to complete the routing.