This skill should be used when the user asks to "create a task", "add a Todoist task", "link task to project", "manage tasks", "connect tasks to notes", discusses Todoist integration, mentions deep links, task-to-note linking, or needs guidance on when to use Todoist vs Obsidian for task management.
Manages Todoist tasks with Obsidian deep links, labels, and time sector organization for daily execution.
/plugin marketplace add oskar-dragon/claude-code/plugin install vault-manager@claude-codeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Todoist serves as the daily task manager. Obsidian holds project-level detail, goals, and reference material. The two connect via deep links. The Todoist MCP server provides task management tools.
Core principle: Obsidian is the source of truth for project task breakdowns. Todoist is for daily execution and quick reference only.
Todoist — daily execution and quick reference:
Obsidian — source of truth for planning:
Rule of thumb: if it has a due date and can be checked off, it belongs in Todoist. If it needs more than a sentence to describe, it also needs an Obsidian note.
What does NOT go in Todoist:
## Tasks sectionApply labels to every task created in Todoist:
| Label | When to use |
|---|---|
| Planning | Project in planning phase |
| Projects | Personal project work |
| Work | Work-related tasks |
| Studying | Study-related tasks |
| Admin | Administrative tasks (emails, scheduling, etc.) |
| Chores | Household chores |
Tasks are placed in Time Sector projects during planning sessions:
| Bucket | Todoist Project ID | Purpose |
|---|---|---|
| THIS WEEK | 6Fgfm6g4fC4Rp7Mq | Tasks to do this week |
| NEXT WEEK | 6Fgfm72qRmG6Qcw8 | Tasks for next week |
| THIS MONTH | 6Fgfm7VhJ5W2Wp5c | Tasks for this month |
| NEXT MONTH | 6Fgfm7x56gQVcJQg | Tasks for next month or later |
Connect Todoist tasks to Obsidian notes for navigation.
obsidian://open?vault=Vault%20V2&file=<URL-encoded-path>
Projects/My Project.md).md extension (e.g., Projects/My Project)%20, / -> %2F, special chars encoded| Note Path | Deep Link |
|---|---|
Projects/Claude Code Setup.md | obsidian://open?vault=Vault%20V2&file=Projects%2FClaude%20Code%20Setup |
Goals/Save £35k.md | obsidian://open?vault=Vault%20V2&file=Goals%2FSave%20%C2%A335k |
Notes/2026-01-15 Meeting Notes.md | obsidian://open?vault=Vault%20V2&file=Notes%2F2026-01-15%20Meeting%20Notes |
Project-reference tasks: Deep link goes IN the task name/content so it's directly clickable from the task list:
[Project Name](obsidian://open?vault=Vault%20V2&file=Projects%2FProject%20Name)
Action items (meetings, reviews): Deep link goes in the task description. The task name is the action itself.
Each Obsidian project gets ONE Todoist task — a project-reference task. This is NOT a task from the project's breakdown. It exists so the project appears in the Time Sector view and Oskar can click through to the project note.
[Project Name](deep-link) — markdown link with deep linkThe project note's ## Tasks section is the source of truth for what needs doing.
One-off actions that don't need Obsidian documentation:
For recurring/habit goals (e.g., "exercise 3x/week"):
After processing a meeting transcript with /meeting:
During weekly/monthly reviews, non-project action items that surface (e.g., "email X about Y") go to Todoist with deep links to relevant notes.
Project-related actions identified during reviews should be added to the project note's ## Tasks section, NOT created as individual Todoist tasks.
Available via the Todoist MCP server. Tool names may vary by MCP version — verify available tools on first connection.
Expected tools:
Morning planning:
find-tasks-by-date with startDate: "today" -> get today's tasks including overdue
get-overview -> see overall status
After processing a meeting:
add-tasks -> create tasks for each action item with deep links in descriptions and labels
Weekly review:
find-completed-tasks with since/until for this week -> see what got done
find-tasks with projectId for each Time Sector bucket -> see what's pending
Creating a project-reference task:
add-tasks with:
- content: "[Project Name](obsidian://open?vault=Vault%20V2&file=Projects%2FProject%20Name)"
- projectId: Time Sector bucket ID
- labels: ["Projects"] # or ["Work"], etc.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.