tasknotes
Create, update, delete, and list tasks via HTTP API. USE WHEN user wants to create tasks, mark done, update status, or manage tasks.
Best use case
tasknotes is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create, update, delete, and list tasks via HTTP API. USE WHEN user wants to create tasks, mark done, update status, or manage tasks.
Teams using tasknotes should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tasknotes/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tasknotes Compares
| Feature / Agent | tasknotes | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create, update, delete, and list tasks via HTTP API. USE WHEN user wants to create tasks, mark done, update status, or manage tasks.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# TaskNotes Skill
CRUD operations on tasks via TaskNotes plugin HTTP API.
## API Endpoint
```
http://127.0.0.1:8090/api
```
## List Tasks
```bash
curl -s "http://127.0.0.1:8090/api/tasks"
curl -s "http://127.0.0.1:8090/api/tasks?status=in-progress"
```
## Create Task
```bash
curl -X POST "http://127.0.0.1:8090/api/tasks" \
-H "Content-Type: application/json" \
-d '{
"title": "Task title",
"status": "open",
"priority": "high",
"projects": ["[[Project Name]]"],
"due": "2026-01-15",
"scheduled": "2026-01-10"
}'
```
**Fields:**
| Field | Values |
|-------|--------|
| title | Task name (required) |
| status | `open`, `in-progress`, `done` |
| priority | `none`, `low`, `normal`, `high` |
| projects | `["[[Project Name]]"]` - array of wikilinks |
| due | `YYYY-MM-DD` |
| scheduled | `YYYY-MM-DD` or `YYYY-MM-DDTHH:MM:SS` |
## Update Task
```bash
curl -X PUT "http://127.0.0.1:8090/api/tasks/Tasks%2Fmy-task.md" \
-H "Content-Type: application/json" \
-d '{"status": "done"}'
```
**Note:** Path must be URL-encoded (`/` → `%2F`, space → `%20`)
## Delete Task
```bash
curl -X DELETE "http://127.0.0.1:8090/api/tasks/Tasks%2Fmy-task.md"
```
## Get Options
```bash
curl -s "http://127.0.0.1:8090/api/options"
```
Returns available statuses, priorities, and projects.
## Example Workflow
```bash
# Create
curl -X POST "http://127.0.0.1:8090/api/tasks" \
-H "Content-Type: application/json" \
-d '{"title": "Review proposal", "status": "open", "projects": ["[[Website Redesign]]"]}'
# Start working
curl -X PUT "http://127.0.0.1:8090/api/tasks/Tasks%2FReview%20proposal.md" \
-H "Content-Type: application/json" \
-d '{"status": "in-progress"}'
# Complete
curl -X PUT "http://127.0.0.1:8090/api/tasks/Tasks%2FReview%20proposal.md" \
-H "Content-Type: application/json" \
-d '{"status": "done"}'
```Related Skills
review
Daily and weekly review workflows. USE WHEN user says "morning routine", "evening routine", "weekly review", "start my day", "end of day".
query
Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.
granola
Query and sync Granola meetings to Obsidian vault. Use when user mentions Granola, meeting transcripts, or wants to sync meeting notes. Reads from local cache - no API needed.
client
Manage client relationships. USE WHEN user asks about clients, follow-ups, client emails, or who needs attention.
tasknotes
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.
tasknotes
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.
tasknotes
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.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
santa-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.