process-notes

Invoke the skill with a note name, a daily note date in YYYY-MM-DD format, a #fleeting tag, or pasted raw text. It proposes atomic note drafts with claim-style titles, waits for your approval, then writes them to the vault with status: draft frontmatter.

Pass the long note as input and the atomization step detects idea boundaries, splitting content into notes of one claim each, capped at 10 proposals per run. Inputs over 2000 words should be split across multiple runs to preserve quality.

No. The pipeline has two mandatory approval gates: one before writing any note drafts and one before adding any wikilinks. You can approve, reject, skip numbered items, or send feedback to revise the proposals.

Each note carries title, created date, type: permanent, source, tags, and status: draft. The skill also merges in your vault CLAUDE.md conventions for folder placement, frontmatter schema, and tag taxonomy.

Skip it for quick single-note edits, which you can do directly, and for vault maintenance like orphan detection or broken links, which belongs to a vault-health skill. Linking notes that already exist in the vault is handled by a separate vault-connect skill.