tasknotes
Skill545 starsChanged 54 days agoMITView on GitHub
Manage tasks in Obsidian via TaskNotes plugin API. Use when user wants to create tasks, list tasks, query by status or project, update task status, delete tasks, or check what they need to do.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- vanillaflava/tasknotes-skilltheir own version, first seen Oct 29, 2026
- ArtemXTech/claude-code-obsidian-startertheir own version, first seen Jan 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ArtemXTech/claude-code-obsidian-starter★ 225same name
- vanillaflava/tasknotes-skill★ 18same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- chief-of-aiSkill
- granolaSkill
- notebooklm-importSkill
- notebooklmSkill
- recallSkill
- sync-claude-sessionsSkill
- wispr-flowSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If TaskNotes has no auth token set, you don't need a .env file.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TaskNotes Skill
Manage Obsidian tasks via the TaskNotes plugin HTTP API.
Requirements
- TaskNotes plugin installed in Obsidian
- Enable HTTP API in TaskNotes settings:
- Open Obsidian Settings → TaskNotes
- Enable "HTTP API" toggle
- Set API port (default: 8080)
- API token: leave empty for no auth, or set a token for security
- Environment variables in
.envfile at vault root (if using auth):
If TaskNotes has no auth token set, you don't need aTASKNOTES_API_PORT=8080 TASKNOTES_API_KEY=your_token_here.envfile.
CLI Commands
# List all tasks
uv run scripts/tasks.py list
# List by status (use your configured status values)
uv run scripts/tasks.py list --status "in-progress"
# List by project
uv run scripts/tasks.py list --project "My Project"
# Create task
uv run scripts/tasks.py create "Task title" --project "My Project" --priority high
# Create task with scheduled time
uv run scripts/tasks.py create "Meeting prep" --scheduled "2025-01-15T14:00:00"
# Update task status
uv run scripts/tasks.py update "Tasks/task-file.md" --status done
# Add/update task description
uv run scripts/tasks.py update "Tasks/task-file.md" --details "Additional context here."
# Delete task
uv run scripts/tasks.py delete "Tasks/task-file.md"
# Get available options (statuses, priorities, projects)
uv run scripts/tasks.py options --table
# Human-readable output (add --table)
uv run scripts/tasks.py list --tableTask Properties
Status and Priority values: Configured in your TaskNotes plugin settings. Run options command to see available values:
uv run scripts/tasks.py options --tableOther fields:
projects- Array of project links, e.g.["[[Project Name]]"]contexts- Array like["office", "energy-high"]due- Due date (YYYY-MM-DD)scheduled- Scheduled date/time (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS)timeEstimate- Minutes (number)tags- Array of tagsdetails- Task description (writes to markdown body, not frontmatter)
API Reference
Base URL: http://localhost:8080/api
| Method | Endpoint | Description |
| GET | /tasks | List tasks (supports filters) |
| POST | /tasks | Create task |
| GET | /tasks/{id} | Get single task |
| PUT | /tasks/{id} | Update task |
| DELETE | /tasks/{id} | Delete task |
| GET | /filter-options | Available statuses, priorities, projects |
Query Parameters for GET /tasks
status- Filter by statusproject- Filter by project namepriority- Filter by prioritytag- Filter by tagoverdue- true/falsesort- Sort fieldlimit- Max resultsoffset- Pagination offset
When to Use
- "create a task for X" → create task
- "show my tasks" → list all tasks
- "show in-progress tasks" → list --status in-progress
- "mark X as done" → update task status to done
- "what should I work on" → list tasks by status
Example Workflow
# Morning: Check what to work on
uv run scripts/tasks.py list --status in-progress --table
uv run scripts/tasks.py list --limit 5 --table
# Create task linked to project
uv run scripts/tasks.py create "Finish landing page" \
--project "Website Redesign" \
--priority high
# Complete a task
uv run scripts/tasks.py update "Tasks/finish-landing-page.md" --status doneDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

