skills/todoist-api/SKILL.md
Todoist API v1 integration reference. Use when building or operating code, tools, scripts, or agents that call Todoist directly over HTTP for tasks, projects, sections, labels, comments, reminders, filters, completed-task history, sync, or Quick Add. Prefer this for API mechanics, endpoint shapes, authentication, pagination, and migration caveats; keep product workflow and task-management preferences in the calling agent's own instructions.
npx skillsauth add miguelalcalde/agentfiles todoist-apiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to call Todoist's current unified API v1 directly.
This skill is API reference only. Do not decide task workflow, default projects, default due dates, confirmation policy, or personal task-management conventions from this skill. Read those from the calling agent's instructions or the user.
https://api.todoist.com/api/v1 as the base URL./rest/v2 examples unless the user explicitly asks for a
legacy integration.Authorization: Bearer $TODOIST_API_TOKEN or
an OAuth access token.Content-Type: application/json.For personal automation, read TODOIST_API_TOKEN from the environment:
curl -s "https://api.todoist.com/api/v1/tasks?limit=50" \
-H "Authorization: Bearer $TODOIST_API_TOKEN"
For multi-user apps, use OAuth and request the smallest scopes needed:
task:add: add new tasks onlydata:read: read tasks, projects, labels, filters, and related datadata:read_write: read and write application datadata:delete: delete tasks, labels, filters, and related dataproject:delete: delete projectsUse explicit task creation when the caller already knows fields:
curl -s -X POST "https://api.todoist.com/api/v1/tasks" \
-H "Authorization: Bearer $TODOIST_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"content": "Review launch checklist",
"description": "Confirm owners and dates",
"project_id": "PROJECT_ID",
"labels": ["planning"],
"priority": 1,
"due_string": "tomorrow"
}'
Use Quick Add when the caller wants Todoist natural-language parsing:
curl -s -X POST "https://api.todoist.com/api/v1/tasks/quick" \
-H "Authorization: Bearer $TODOIST_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"text": "Review launch checklist tomorrow #Work @planning p1",
"meta": true
}'
Quick Add supports project markers (#Project), section markers (/Section),
labels (@label), priorities (p1 to p4), deadlines in braces, reminders,
assignees, and trailing descriptions after //.
Paginated endpoints return:
{
"results": [],
"next_cursor": null
}
Loop until next_cursor is null. Keep the same filters and limit across
cursor requests. Do not parse or modify cursor strings. Default page size is
50; maximum limit is 200 per official docs.
Official reference: https://developer.todoist.com/api/v1
references/endpoints.md for endpoint paths and common request fields.references/api-semantics.md for pagination, errors, field semantics,
completed-task access, and migration caveats.development
Lightweight project backlog workflow. Use when starting a project, creating or maintaining a `.backlog/` folder, capturing inbox ideas, promoting work to GitHub Issues, refining work into PRDs, planning implementation, or keeping project task memory current without a larger agent framework.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------