obsidian-tasks

Create and format GTD tasks in Obsidian with dynamic category tagging.

4|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-vault-skills --skill obsidian-tasks-flowing-abyss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-tasks
Source: https://github.com/flowing-abyss/obsidian-vault-skills/tree/main/skills/obsidian-tasks
Command: npx skills add https://github.com/flowing-abyss/obsidian-vault-skills --skill obsidian-tasks-flowing-abyss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually formatting GTD tasks in Obsidian is error-prone and hard to scale; this Skill standardizes task lines and leverages dynamic category discovery for consistent tagging.

Core Features & Use Cases

  • Task Format: Create tasks with the exact line pattern "- [ ] #task/TYPE #category/CATEGORY Description" to ensure uniform structure.
  • Dynamic Categories: Categories are discovered from base/categories/*.md at runtime, avoiding hard-coded values and keeping tagging flexible.
  • Diverse Task Types: Supports inbox, next_action, one-off, multistep, waiting_for, regular, idea, reference, someday for varied workflows.
  • Real-World Use Case: Capture a new task like "Prepare quarterly report" and tag it with the appropriate category for future planning.

Quick Start

Create a new task using the Task Format and select the most relevant category.

Frequently Asked Questions about obsidian-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format GTD tasks in Obsidian to ensure consistent structure?

Standardize GTD tasks in Obsidian by applying the strict line syntax "- [ ] #task/TYPE #category/CATEGORY Description". This ensures uniform structure and consistent tagging across your vault.

How do I dynamically discover categories for task tagging instead of hard-coding them?

Dynamically discover categories for task tagging by reading category files from the base/categories/*.md directory at runtime. This avoids hard-coded values and keeps your GTD tagging flexible as your categories evolve.

What GTD task types are supported for capturing notes in Obsidian?

Supported GTD task types for Obsidian notes include inbox, next_action, one-off, multistep, waiting_for, regular, idea, reference, and someday. These diverse types accommodate varied personal knowledge management workflows.

Can I use this dynamic task format for GTD workflows without hard-coded category values?

Yes, you can use this task format for GTD workflows without hard-coded values. The Skill discovers categories dynamically at runtime from your base/categories directory, ensuring tagging remains flexible and scalable.

Why manually formatting Obsidian tasks is error-prone and how to fix it?

Manually formatting Obsidian tasks is error-prone because it is hard to scale and maintain syntax consistency. Fix it by using a standardized task format that automatically applies strict line syntax and proper category tagging.