Inbox Triage

---
name: inbox-triage
description: "Use whenever inbox notes need classification, the user says 'inbox cleanup', 'clean up my inbox', 'разгреби inbox', or after /mn:health flags a backlog. Converts inbox captures into proper typed notes (atom, molecule, source, session) with taxonomy tags and MOC links."
user-invocable: false
model: haiku
context: fork
---

# mnemo:sort — Classify Inbox Notes

Review unclassified inbox notes one by one and convert them to proper typed notes.

## Prerequisites & config

Obsidian must be open. Config at `~/.mnemo/config.json` — reads `vault`, `taxonomy`, `links_section`. Schema in `references/config-schema.md`.

## Workflow

### Step 1: Find Inbox Notes

```bash
obsidian search query="type: inbox" vault="{vault}"
```

If none found: "No inbox notes to classify."

### Step 2: Present Each Note

For each inbox note, read it:

```bash
obsidian read file="{note_name}" vault="{vault}"
```

Show content and suggest classification:

```
📬 Inbox note 1/4: "Inbox — HisPO for pipeline stabilization"

Content: "idea: use HisPO from LongCat for pipeline stabilization"

Suggested type: atom (single concept/fact)
Suggested name: "Atom — HisPO algorithm for MoE training stabilization"
Suggested tags: [atom, agentic-rl, moe, antomate]
Suggested MOC: [[MOC — Agent Self-Correction]]

Actions:
  [1] Accept suggestion
  [2] Change type (molecule/source/session)
  [3] Edit name/tags
  [4] Skip for now
  [5] Delete (not useful)
```

### Step 3: Apply Classification

**Bulk mode:** if the user says "accept all" / "применить все" / "bulk", skip the per-note `[1-5]` prompt and apply the suggested classification for every remaining note. Still show a progress line per note ("3/7: Atom — X created") so the user can abort if something looks wrong.

On user confirmation (per-note or bulk):

1. Read the original inbox note content
2. Delete the inbox note: `obsidian delete file="{old_name}" vault="{vault}"`
3. Create new typed note via **MCP** (shell-safe for arbitrary markdown):
   ```
   mcp__obsidian__create(
     path: "{new_name}.md",
     file_text: """---
type: {chosen_type}
tags: [{type}, {tags}]
date: {original_date}
source: {if applicable}
---

# {new_name}

{original content, cleaned up}

## {links_section}
- [[{suggested MOC}]]
"""
   )
   ```

   **Why MCP, not CLI:** content from inbox may contain code blocks with backticks or `$(...)`. CLI `obsidian create content="..."` would trigger zsh command substitution (real incident 2026-04-21, accidental prod deploy).

4. Add to MOC — MCP for consistency, or CLI for plain wikilink appends:
   ```
   mcp__obsidian__str_replace(
     path: "{MOC}.md",
     old_str: "{stable anchor near list}",
     new_str: "{same anchor}\n- [[{new_name}]]"
   )
   ```
   CLI fallback (plain wikilink — no backticks, safe):
   `obsidian append file="{MOC}" vault="{vault}" content="- [[{new_name}]]"`

### Step 4: Summary

```
📊 Inbox triage complete

Classified: 3
  - Atom — HisPO algorithm → MOC — Agent Self-Correction
  - Source — WeChat agent trends → MOC — AI ML Tools
  - Molecule — CLI vs MCP cost analysis → MOC — Memory Systems
Skipped: 1
Deleted: 0
Remaining in inbox: 1
```

## Gotchas

Common failures in `references/gotchas.md`. Tool-routing (MCP for writes) in `references/tool-routing.md`. Skill-specific rules:

- **One note at a time by default** — user confirms each. Bulk mode only on explicit request (see Step 3).
- **Preserve original date** — from inbox note frontmatter, not today's date. The intent was captured when the inbox note was created.
- **Delete old inbox note after reclassification** — otherwise you end up with duplicates (inbox + typed).
- **Always add to MOC** — classified notes must not be orphans.
- **Suggest, don't force** — user picks final type, name, tags. Your role is to propose, not to decide.
- **Clean up content** — fix typos, expand abbreviations, add context if the original note was terse. The new note should be readable a month from now.