inbox-processor
The inbox-processor skill organizes notes in a Vault's 00_Inbox folder using the PARA method, categorizing items into Projects, Areas, Resources, or Archive folders based on their deadline status and ongoing relevance. Use it when you need to triage captured ideas, sort accumulated notes, or declutter your inbox by identifying which items should be moved, combined, deleted, or retained for daily capture.
git clone --depth 1 https://github.com/heyitsnoah/claudesidian /tmp/inbox-processor && cp -r /tmp/inbox-processor/.agents/skills/inbox-processor ~/.claude/skills/inbox-processorSKILL.md
# Inbox Processor Help organize and process items in the 00_Inbox folder according to the PARA method. ## Task Review all notes in `00_Inbox/` and help categorize them: 1. **Scan the Inbox** - List all files currently in 00_Inbox - Exclude README.md and Welcome.md 2. **Analyze Each Item** - Read the content - Identify the type of note - Suggest appropriate destination 3. **Categorization Rules** - **→ 01_Projects**: Has deadline, specific outcome - **→ 02_Areas**: Ongoing responsibility, no end date - **→ 03_Resources**: Reference material, knowledge - **→ 04_Archive**: Old/completed, no longer active - **→ Delete**: No value, redundant, or temporary 4. **Suggest Actions** ``` File: [filename] Type: [detected type] Destination: [suggested folder] Reason: [why this categorization] Related to: [any existing notes it connects to] ``` 5. **Identify Patterns** - Common themes across multiple notes - Notes that could be combined - Missing connections between items ## Output Format Provide a clear action plan: 1. Items to move (with destinations) 2. Items to combine or link 3. Items to delete 4. Items needing more context ## Remember - Some items legitimately belong in the Inbox (daily notes, quick captures) - Don't over-organize - sometimes "good enough" is perfect - Look for opportunities to connect ideas, not just file them
Add or update YAML frontmatter properties to enhance Obsidian note organization. Use when the user asks to add, fix, normalize, or improve frontmatter, properties, metadata, tags, or YAML on a note or folder of notes.
Conduct an end-of-day review to capture progress and set up tomorrow. Use when the user asks for a daily review, end of day wrap-up, EOD note, what they did today, or wants to reflect on the day and plan tomorrow.
Remove AI-generated jargon and restore human voice to text. Use when the user asks to de-AI-ify, humanize, remove AI tone, or make text sound less machine-generated.
Download files from URLs to the Obsidian attachments folder and organize them with descriptive names. Use when the user provides URLs to download, asks to save files from the web, or wants to add web content as attachments.
Work with git worktrees for isolated parallel development. Use when starting feature work in isolation, when need separate workspace without branch switching, or when cleaning up worktrees after PR merge.
Interactive setup wizard that helps new users create a personalized CLAUDE.md file based on their Obsidian workflow preferences. Use when the user wants to set up claudesidian, onboard a new vault, or run the bootstrap/init/setup wizard.
Install claudesidian shell command to launch Claude Code from anywhere. Use when the user wants to install a shell alias/launcher for their vault, or asks to set up the claudesidian command.
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.