vault-triage

Triages Obsidian inbox notes in batches with promote, merge, discard, or defer decisions.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/DoctorMozg/claude-pipelines --skill vault-triage-doctormozg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-triage
Source: https://github.com/DoctorMozg/claude-pipelines/tree/main/plugins/mz-knowledge/skills/vault-triage
Command: npx skills add https://github.com/DoctorMozg/claude-pipelines --skill vault-triage-doctormozg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fleeting notes pile up in an Obsidian inbox faster than they can be reviewed, and clearing them one by one is slow and inconsistent. This Skill runs a fast batch triage over inbox notes, proposing a decision for each so the backlog gets cleared in one short session. ## Core Features & Use Cases - Deterministic batch scoring: A triage-scorer agent applies a heuristic ladder (age, stub length, outlinks, status) to propose one of four decisions per note: promote, merge, discard, or defer. - Human approval gate: Every decision is presented for explicit approval before any vault write occurs; the user can override individual decisions by index, and merge targets are always named by the user, never the agent. - Auditable execution: Each applied decision is logged with a SHA-256 hash of the pre-operation content, enabling recovery verification from snapshots or git history. - Use Case: After a week of bursty capture, run a weekly inbox review to clear up to 7 fleeting notes at once — promoting keepers to your permanent-notes folder, merging fragments into existing notes, and deferring the rest with a review_after stamp. ## Quick Start Ask the assistant to triage the inbox of your Obsidian vault, optionally passing the vault path, then approve or override the proposed decisions when prompted.

Frequently Asked Questions about vault-triage

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

FAQPage Schema
How do I triage my Obsidian inbox notes in bulk?

Run the vault-triage skill against your vault path to score up to 7 inbox notes per session with a heuristic ladder. It proposes promote, merge, discard, or defer for each note, and you approve or override the decisions before any file changes are made.

How does the triage decide between promote, merge, discard, and defer?

A triage-scorer agent computes body word count, note age, outlink count, and status, then applies a first-match heuristic ladder. Stubs under 20 words and notes older than 14 days influence the proposed decision, but the user always confirms the final call.

Can the skill choose merge targets automatically in Obsidian?

No, merge targets are never auto-selected. The scorer leaves proposed_merge_target as null, and the user must supply the exact target note name using merge::Target Note Name syntax before the merge is executed.

Is it safe to let the skill delete or move notes in my vault?

All vault writes are gated behind an explicit approval step, and deletions only happen after destination writes are verified by re-reading. Every operation records a SHA-256 hash of the original content in a decision log so changes can be verified or recovered from snapshots.

Why does vault-triage only process 7 notes at a time?

The batch size is capped at 7 to keep each session under roughly 30 seconds and prevent decision fatigue. Larger batches degrade the quality of individual decisions, so the inbox is cleared across multiple short sessions instead.

When should I not use vault-triage for my notes?

Do not use it to edit a single known note, atomize a long fleeting note into permanent notes, or propose wikilinks between existing notes. Those cases are handled by direct editing, the process-notes skill, or the vault-connect skill respectively.