How do I install the Inbox Process skill?

Run npx skillmds@latest add slogsdon/inbox-process in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Inbox Process safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Inbox Process?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Inbox Process free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Inbox Process?

slogsdon (@slogsdon) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Inbox Process by slogsdon — Agent Skill

Name: Inbox Process
Author: slogsdon

Inbox Process

Process the Obsidian Inbox interactively — reads all files, generates routing recommendations, then walks through each item one at a time with user confirmation before acting. Use when /inbox-process is invoked or when Shane wants to clear the Inbox.

slogsdon b485082 3.4 KB Updated Sep 17, 2026

File contents

Skill: /inbox-process

Interactive inbox triage. Review each item, confirm the action, execute.

Fixtures to Skip

These files are permanent Inbox fixtures — do not include them in processing:

Inbox Processing.md
todo.md
Chores.md

Destination Routing

Recommendation	When to use
Move to Projects/	Describes an active project, initiative, or ongoing effort
Move to Concepts/	A mental model, framework, reusable idea, or principle
Move to Context/	Background reference material, standing context, or reference docs
Move to Meetings/	Raw conversation or meeting note — process with /meeting first
Move to Clippings/	Article, link, or external source saved for later
Archive	Done, resolved, or superseded — worth keeping but not active
Delete	Transient, already captured elsewhere, or no longer relevant
Keep in Inbox	Genuinely needs more thought before acting

Steps

List inbox contents
- Run: ls "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal/Inbox/"
- Filter out fixture files (see above)
- If inbox is empty: report "Inbox is clear." and stop
Read each file briefly
- For each file, strip the .md extension and run: obsidian read file='Note Name'
- Skim the output for content type and intent (first ~40 lines is enough)
- Note the filename and content type
Generate recommendations upfront
- For every non-fixture file, produce a one-line summary and a routing recommendation
- Be opinionated — give a clear call, don't hedge
- Present the full list as a table:
```
| File | Summary | Recommendation |
|------|---------|----------------|
| [filename] | [one-line summary] | [destination] |
```
Walk through items one at a time
- For each item, show:
```
[N/Total] filename.md
Summary: [one-line]
Recommendation: [destination]

Handle as recommended, or do something else?
```
- Wait for user response before acting
- Valid responses: "yes" / "ok" / blank → execute recommendation; "skip" / "keep" → note and move on; any other instruction → execute that instead
Execute each confirmed action
- Move: mv "[full vault path/Inbox/filename]" "[full vault path/Destination/filename]" — bash exception; obsidian CLI has no move command
- Archive: mv "[full vault path/Inbox/filename]" "[full vault path/Inbox/Archive/filename]" (create Archive/ if needed)
- Delete: rm "[full vault path/Inbox/filename]" — bash exception; obsidian CLI has no delete command
- Keep in Inbox: no action, note it
- Raw meeting note → Meetings/: remind Shane to run /meeting [filename] first; skip the move for now

Report summary

After all items are handled, output:

Inbox processed: N items
- Moved to Projects: N
- Moved to Concepts: N
- Moved to Context: N
- Moved to Meetings: N
- Moved to Clippings: N
- Archived: N
- Deleted: N
- Kept in Inbox: N
- Skipped: N

---name: inbox-processdescription: Process the Obsidian Inbox interactively — reads all files, generates routing recommendations, then walks through each item one at a time with user confirmation before acting. Use when /inbox-process is invoked or when Shane wants to clear the Inbox.---# Skill: /inbox-processInteractive inbox triage. Review each item, confirm the action, execute.## Fixtures to SkipThese files are permanent Inbox fixtures — do not include them in processing:- `Inbox Processing.md`- `todo.md`- `Chores.md`## Destination Routing| Recommendation | When to use ||---|---|| **Move to Projects/** | Describes an active project, initiative, or ongoing effort || **Move to Concepts/** | A mental model, framework, reusable idea, or principle || **Move to Context/** | Background reference material, standing context, or reference docs || **Move to Meetings/** | Raw conversation or meeting note — process with /meeting first || **Move to Clippings/** | Article, link, or external source saved for later || **Archive** | Done, resolved, or superseded — worth keeping but not active || **Delete** | Transient, already captured elsewhere, or no longer relevant || **Keep in Inbox** | Genuinely needs more thought before acting |## Steps1. **List inbox contents** - Run: `ls "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal/Inbox/"` - Filter out fixture files (see above) - If inbox is empty: report "Inbox is clear." and stop2. **Read each file briefly** - For each file, strip the `.md` extension and run: `obsidian read file='Note Name'` - Skim the output for content type and intent (first ~40 lines is enough) - Note the filename and content type3. **Generate recommendations upfront** - For every non-fixture file, produce a one-line summary and a routing recommendation - Be opinionated — give a clear call, don't hedge - Present the full list as a table: ``` | File | Summary | Recommendation | |------|---------|----------------| | [filename] | [one-line summary] | [destination] | ```4. **Walk through items one at a time** - For each item, show: ``` [N/Total] filename.md Summary: [one-line] Recommendation: [destination] Handle as recommended, or do something else? ``` - Wait for user response before acting - Valid responses: "yes" / "ok" / blank → execute recommendation; "skip" / "keep" → note and move on; any other instruction → execute that instead5. **Execute each confirmed action** - **Move**: `mv "[full vault path/Inbox/filename]" "[full vault path/Destination/filename]"` — bash exception; obsidian CLI has no move command - **Archive**: `mv "[full vault path/Inbox/filename]" "[full vault path/Inbox/Archive/filename]"` (create Archive/ if needed) - **Delete**: `rm "[full vault path/Inbox/filename]"` — bash exception; obsidian CLI has no delete command - **Keep in Inbox**: no action, note it - **Raw meeting note → Meetings/**: remind Shane to run `/meeting [filename]` first; skip the move for now6. **Report summary** - After all items are handled, output: ``` Inbox processed: N items - Moved to Projects: N - Moved to Concepts: N - Moved to Context: N - Moved to Meetings: N - Moved to Clippings: N - Archived: N - Deleted: N - Kept in Inbox: N - Skipped: N ```

Frequently asked questions