obsidian-task — Claude Code command for tasks and installation
The obsidian-task command places a task on the right Obsidian kanban board and infers its priority and due date. Use it to capture tasks from a request or recent conversation.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-task does
The command looks for the relevant board, then adds a card to 📋 This Week or 📥 Backlog based on its due date. It infers priority, a linked project, and a linked person from the task or conversation. Longer tasks get their own note, with links from the project note and today’s daily note.
Before making changes, it reads _CLAUDE.md if that file is at the vault root. Board and task folders are resolved through references/folder-map.md; notes it creates or edits must follow references/ai-first-rules.md. If it cannot read those rules, it must say so before writing. That means the command cannot safely proceed with note creation when the rules file is unavailable.
What it helps with
- put a task on the appropriate kanban board
- sort task cards into columns according to their due dates
- link a task to its project and today’s daily note
- create a separate note for a substantial task
Example prompts for the agent
- Add a task to prepare the release plan for next week.
- Remind me to check the database migration.
- Put a task from our conversation on the
Websiteproject board.
How to install obsidian-task
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/obsidian-task.mdCall it with /obsidian-task. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-task.mdCall it with /prompts:obsidian-task. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-task.prompt.mdManually: put the files in place
.gemini/commands/obsidian-task.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-task
How do I install obsidian-task in Claude Code?
Run these commands in order: /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain.
What does obsidian-task do?
It adds a task to a suitable Obsidian kanban board, infers its priority and due date, and links it to a project and the daily note. Longer tasks also get a separate note.
What note rules does the command follow?
Notes it creates or updates must follow references/ai-first-rules.md. If the command cannot read that file, it must report the issue before writing.
Source text
obsidian-task.md · MIT
--- description: Add a task to the right kanban board with inferred priority and due date category: vault trigger-mode: proactive triggers_en: ["add task", "new todo", "track this", "remind me"] triggers_de: ["Aufgabe hinzufügen", "neues To-do", "das verfolgen", "erinnere mich"] triggers_es: ["añade una tarea", "nuevo pendiente", "haz seguimiento de esto", "recuérdamelo"] triggers_pt: ["adicione uma tarefa", "novo a fazer", "acompanhe isto", "me lembre disto"] triggers_zh: ["添加一个任务", "记个待办", "跟踪这件事", "提醒我处理这个", "把这件事放到看板"] --- Use the obsidian-second-brain skill. Execute `/obsidian-task $ARGUMENTS`: 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Parse the task from the argument, or pull from recent conversation context if no argument given 3. Infer: priority (🔴/🟡/🟢), due date, linked project, linked person 4. Search for the right kanban board - use `_CLAUDE.md` board list or search the boards folder (resolved per `references/folder-map.md`) 5. Add the task card to the correct column (`📋 This Week` or `📥 Backlog` depending on due date) 6. Create a task note in the tasks folder (resolved per `references/folder-map.md` - wiki-style `wiki/tasks/`, Obsidian-style `Tasks/`) if the task is substantial (more than a one-liner) 7. Link the task from the relevant project note and today's daily note --- **AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading. **Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain