This skill should be used when the user asks to "find tasks", "show tasks", "list tasks", "query tasks", "tasks with status", "fire tasks", "incomplete tasks", "tasks in inbox", "tasks in projects", or mentions task checkboxes with status markers (x, f, /, b, ?). Provides task querying across PARA directories in Obsidian vaults.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
Vault Task Management
description
This skill should be used when the user asks to "find tasks", "show tasks", "list tasks", "query tasks", "tasks with status", "fire tasks", "incomplete tasks", "tasks in inbox", "tasks in projects", or mentions task checkboxes with status markers (x, f, /, b, ?). Provides task querying across PARA directories in Obsidian vaults.
version
0.1.0
Vault Task Management
This skill provides Claude with knowledge about task management in Obsidian vaults using checkbox syntax with status markers, and tools to efficiently find and query tasks across PARA directories.
Task Definition
A task is any line in a markdown file that starts with - [ ] where the character within the brackets denotes the current status.
Task Status Markers
x - Complete
f - Fire (important/urgent)
/ - Partial (in progress)
b - Bookmarked (deferred)
? - Has open questions
Task Syntax Examples
- [ ] This is an incomplete task
- [x] This is a completed task
- [f] This is a fire/urgent task
- [/] This is a partial/in-progress task
- [b] This is a bookmarked/deferred task
- [?] This task has open questions
Task Categories
Tasks are organized into three primary categories based on their location in the PARA structure:
Inbox - Tasks in 00_Inbox/ files (unprocessed, need categorization)
Projects - Tasks in 01_Projects/ files (time-bound initiatives)
Areas - Tasks in 02_Areas/ files (ongoing responsibilities)
Note: Tasks may exist in 03_Resources/ and 04_Archive/ directories, but these are considered secondary for active task management purposes.
Finding Tasks
Two scripts are available for querying tasks:
scripts/find-tasks.sh - Raw pipe-delimited output for parsing
status_filter - Filter tasks by status (default: all)
all - Show all tasks regardless of status
incomplete - Show all tasks that are NOT complete (excludes x)
x, f, /, b, ? - Show only tasks with specific status
vault_path - Path to Obsidian vault (default: current directory)
Script Output Format
The script outputs pipe-delimited results:
category|status|file_path|line_number|task_text
Example output:
inbox|f|00_Inbox/2026-01-14.md|15|Follow up with team on SDK adoption
projects|/|01_Projects/Epic-Social-39.00/README.md|42|Complete authentication integration
areas|?|02_Areas/EOS-SDK-Team/Team-Project-Status.md|8|Clarify deployment timeline with ops
Common Query Patterns
Find all fire tasks (formatted):
./scripts/show-tasks.sh f /path/to/vault
Find all incomplete tasks (formatted):
./scripts/show-tasks.sh incomplete /path/to/vault
Find tasks with open questions (raw for parsing):
./scripts/find-tasks.sh ? /path/to/vault
Find all tasks in current vault:
./scripts/show-tasks.sh all .
Using the Scripts in Claude Sessions
When a user asks about tasks, prefer show-tasks.sh for direct presentation to users, or find-tasks.sh when you need to parse and analyze the data programmatically.
Example Workflow (Formatted Output)
User asks: "Show me all my fire tasks"
Execute: ./scripts/show-tasks.sh f /home/rjroy/Projects/Vaults/second-brain
Present the formatted output directly
Example output from show-tasks.sh:
Inbox:
[f] Unreal Fest Chicago 2026 proposal (due Jan 22)
File: 00_Inbox/2026-01-05.md (line 158)
Areas:
[f] SDK Performance: Get it formally tied to Epic Social Overlay
File: 02_Areas/Leadership-Development/2026-Manager-Operating-System.md (line 38)
Total tasks: 2
Example Workflow (Parsed Analysis)
User asks: "How many incomplete tasks do I have in each category?"
