v0.4.0 - Multi-modal interface

The skill now adapts to the environment. It probes for MCP server, HTTP API, and filesystem access at session start and routes to the best available path.

What's new:

Step 0 environment probe (MCP → HTTP API → filesystem fallback)
Surface lookup table: exactly what works on which path
Full HTTP API endpoint reference and multi-platform MCP setup guide bundled in references/tasknotes-help.md
Filesystem path covers task body and checklist reads (MCP/API limitation documented)
Schema diagnostic retained as filesystem-only workflow
Pushy conversational triggers: "remind me to", "don't let me forget", "what's blocking me", troubleshooting triggers
README updated to reflect environment-dependent capabilities; cross-platform install paths documented

Known Limitation

Currently, I see no way to retrieve the task body via mcp/API, so the skill falls back on filesystem to read that, but can update normally via mcp/API. Once that is made available by the TaskNotes project, I'll update the skill to match.

v0.2.0 - Recurring tasks, dependencies, and smoother setup

v0.2.0 - Recurring tasks, dependencies, and smoother setup

This is mostly a reliability release with two genuine feature additions. The initial version worked but had some rough edges around setup and didn't support recurring tasks or task dependencies. Both are fixed here.

Recurring tasks

You can now create tasks with a recurrence pattern. The skill writes the RRULE string and sets the first scheduled occurrence; the plugin handles the rest at runtime - advancing scheduled, tracking completion instances, respecting your configured anchor behaviour. The skill's job ends at creation; do not mark recurring tasks done via the agent (that closes the whole series, not just the current instance) - use the plugin GUI for individual occurrence completion.

Common patterns the skill knows:
Daily: DTSTART:20260501;FREQ=DAILY
Weekly on Monday: DTSTART:20260501;FREQ=WEEKLY;BYDAY=MO
Monthly on 15th: DTSTART:20260515;FREQ=MONTHLY;BYMONTHDAY=15

Configure recurring task settings in Settings → TaskNotes → Features → Recurring Tasks before creating your first recurring task - specifically whether due date offset should be maintained and whether the anchor is the scheduled date or the completion date.

Task dependencies

Tasks can now declare blockers via the blockedBy field. The structure:

blockedBy:
  - uid: "relative/path/to/blocking-task.md"
    reltype: "FINISHTOSTART"

The skill reads and writes this field when creating or updating tasks. Dependency resolution and scheduling logic remain plugin-side.

Smoother first-time setup

Config Discovery now deploys a bundled tasknotes-config.md template when no config is found, rather than stopping and prompting. The skill finds (or creates) the right location, deploys the default, and gets you started. If the config is malformed it offers to reset from the bundled default with an explicit warning that this overwrites customisations.

Reliability fixes

• All dates standardized to YYYY-MM-DD format throughout (was inconsistent in the original version)
• Canonical frontmatter field order documented and enforced - fields in a specific order render correctly in Obsidian Properties and are consistent across all agent-created tasks

Upgrading

Re-upload tasknotes.skill via Claude Desktop → Customize → Skills. No config changes required.

v0.1.0 - 1 Skill Release

Working version of a Claude skill that interacts with Obsidian (and the TaskNotes plugin) installed. Limited functionality, but works really well with my llm wiki skills. Do not expect the full comfort and workflows you might be used to from TaskNotes inside Obsidian. All this does is enable Claude to interact with your tasks, and create, update, etc. tasks for themselves on your behalf.

Use with caution: this skill interacts with tasks directly in your vault via read/write. And is meant for users not wanting the complexity of Obsidian CLI or API calls.