Help us improve
Share bugs, ideas, or general feedback.
From obsidian-forge
AI inbox classification pipeline — runs `of process-all` to classify inbox notes with AI, inject frontmatter, and route to PARA folders. Trigger: process inbox, classify notes, empty inbox, PARA routing.
npx claudepluginhub epicsagas/plugins --plugin obsidian-forgeHow this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-forge:inbox-processThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Process all notes in the vault's Inbox directory using AI classification, frontmatter injection, and PARA routing.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Process all notes in the vault's Inbox directory using AI classification, frontmatter injection, and PARA routing.
Verify AI provider is configured:
of doctor --vault <name>
Check the AI section of the output. If AI provider is not configured, the user needs to set up [ai] in vault.toml and add API keys to ~/.obsidian-forge/.env.
of doctor --vault <name>
Note the inbox item count from the output.
of process-all --vault <name>
This reads all files from the Inbox directory, calls the configured AI provider for classification, injects frontmatter, and moves each file to the appropriate PARA folder.
of doctor --vault <name>
Check that inbox count is now 0 (or reduced).
Report in Korean:
| Excuse | Rebuttal | What to do instead |
|---|---|---|
| "AI provider should be fine" | Config drift, key rotation happen silently | Verify with of doctor before processing |
| "100% success is guaranteed" | API limits, malformed notes can cause failures | Check before/after inbox counts |
| "Just re-run if some fail" | Repeated failures indicate systemic issue | Investigate failures before re-running |
of doctorNo evidence = not done.
~/.obsidian-forge/.env and [ai] config in vault.toml