Stats
Links
Categories
Auto-discovered marketplace from jr-xing/tasknote-skill
npx claudepluginhub jr-xing/tasknote-skillManage research task lifecycle using mdbase-tasknotes (mtn) CLI — task creation, time tracking, experiment/data logs, meeting notes, and project hierarchy in an Obsidian vault.
A Claude Code plugin for managing research task lifecycle using mdbase-tasknotes (mtn) CLI. Tracks tasks, experiments, data processing, and meetings in an Obsidian vault with markdown files.
This plugin provides two skills:
tasknote-quick — Lightweight task creation and updates. Use for everyday task operations: creating tasks, marking done, listing what's on your plate, checking overdue items. Fast and minimal.
tasknote — Full lifecycle management. Use when you need the complete research workflow: experiment logs with run tracking, data logs with pipeline tables, meeting notes with action items, multi-session tasks with time tracking, and project hierarchy management.
Both skills share the same conventions: proper project/task matching (always verifies wikilinks before creating them), filename convention (YYYY-MM-DD-TYPE Title.md), and prompt-first workflow.
All notes are plain markdown with YAML frontmatter, stored in your Obsidian vault. They work with both the mtn CLI and the TaskNotes Obsidian plugin.
mtn) CLI installedmtn initclaude plugin add /path/to/tasknote-skill
Or from GitHub:
claude plugin add github:jr-xing/tasknote-skill
.tasknote.yaml in your repo root:collection: "/path/to/your/obsidian-vault"
projects:
- "[[projects/2026-02-01-PROJECT Your Project Name]]"
CLAUDE.md.template to your repo as CLAUDE.md (or append its contents to your existing CLAUDE.md). This tells Claude Code to use the task system during coding sessions.For simple, everyday task operations (~80 lines). Triggers on: "create a task", "add a task", "mark done", "what's on my plate", "what's overdue", "todo", "remind me to".
Covers: create, update, complete, list/search, time tracking, filename convention.
For comprehensive research workflow management (~430 lines + references). Triggers on: "I need to...", "I just finished...", "the results are...", "update the data log", "create a meeting note", "what's the status of...".
Covers everything in tasknote-quick, plus: experiment logs, data logs, meeting notes, multi-session task tracking, detail/reference cards, project hierarchy, cross-updating between tasks and logs.
On session start: Claude reads .tasknote.yaml, lists active tasks for your projects, and matches your prompt to a task (or creates a new one). A timer starts automatically.
During the session: As you work, Claude appends log entries to the active task. Experiment results go to both the task and the experiment log. Data changes update the data log.
On session end: Claude stops the timer, writes a session summary, and asks when you plan to continue (updates scheduled for calendar visibility).
| Type | Prefix | Purpose |
|---|---|---|
| Project | PROJECT | Top-level research initiative (paper, grant) |
| Task | TASK | Specific piece of work with lifecycle |
| Detail Card | CARD | Technical details extracted from a task |
| Reference Card | REF | Permanent shared knowledge (access procedures, contacts) |
| Data Log | DATA-LOG | Per-dataset changelog with pipeline stage table |
| Experiment Log | EXP-LOG | Per-project run log with metrics tracking |
| Meeting | MEETING | Notes with decisions and linked action items |
All files follow the naming convention: YYYY-MM-DD-TYPE Title.md
You don't need to explicitly say "create a task." Just describe what you're doing:
Both skills verify project and task references before creating wikilinks. If you say "add a subtask for project BII", Claude will search existing projects, find the best match, and confirm with you rather than guessing a path that may not exist.