todoist-task — Claude Code skill: create tasks in Todoist
A skill for Claude Code, Cursor and other IDEs that creates Todoist tasks directly from your editor. Recognises task requests, resolves project and date details, shows a preview before creating, and verifies the result in Todoist.
MIT 315 installs ★ 6 updated 2026-11-10
npx skills add prathamdby/skills --skill todoist-task -a claude-codeWhat todoist-task does
When you ask to create a task, it uses the Todoist API to resolve projects and adjust dates to your configured timezone. A preview always appears before creation—showing exactly what will be saved. If a project or parent task is ambiguous, the skill asks one clarifying question and continues without re-prompting.
Task titles get an action verb and specific deliverable; descriptions include context and any supplied requirements. Relative dates like “by Friday” are resolved to your timezone; a casual deadline phrase becomes a due date, while an explicit deadline request is handled separately. After creation, the skill verifies the record matches what you asked for and reports the ID and status.
You need an active Todoist account connected via API. The skill will not create duplicates that match an existing title and parent task.
What it helps with
- Create a Todoist task without leaving your editor
- Auto-fill project, date and priority from context
- Preview a task before saving it to Todoist
- Resolve missing project or parent identifiers in one question
- Prevent duplicate tasks by title and hierarchy
Example prompts for the agent
- Create a task in Todoist: finish Stripe integration, project Backend, due Friday, priority 1
- Show me the preview: write unit tests for utils.js, folder Tests
- Create a subtask under Release launch, include a note about checking database migrations
How to install todoist-task
1Skills CLI (Vercel)
npx skills add prathamdby/skills --skill todoist-task -a claude-code2Manually: put the files in place
~/.claude/skills/todoist-task/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/todoist-task/
1Skills CLI (Vercel)
npx skills add prathamdby/skills --skill todoist-task -a codex2Manually: put the files in place
.agents/skills/todoist-task/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add prathamdby/skills --skill todoist-task -a cursor2Manually: put the files in place
.cursor/skills/todoist-task/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install prathamdby/skills skills/personal/todoist-task2Manually: put the files in place
.github/skills/todoist-task/SKILL.md1Skills CLI (Vercel)
npx skills add prathamdby/skills --skill todoist-task -a gemini-cli2Platform CLI
gemini skills install https://github.com/prathamdby/skills --path skills/personal/todoist-taskManually: put the files in place
.devin/skills/todoist-task/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add prathamdby/skills --skill todoist-task -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about todoist-task
How do I install todoist-task in Claude Code?
Run npx skills add prathamdby/skills --skill todoist-task -a claude-code, then open the skill config at ~/.claude/skills/todoist-task/SKILL.md. For other IDEs, the command changes (Cursor, GitHub Copilot, Gemini CLI)—pick your platform and use the matching -a flag.
What does todoist-task do?
It recognises requests to create or preview Todoist tasks, resolves project names and dates using your account data, displays a preview, and creates the task with the correct title, description, due date, priority and parent.
Can the skill create a subtask if I know the parent task?
Yes—pass the parent's URL, ID or exact title. The subtask will have no due date unless you specify one or explicitly request it to inherit from the parent.
Source text
SKILL.md · MIT
--- name: todoist-task description: > When the user wants a Todoist task created, or shown before it is created. --- # Todoist task Preserve meaning, literals, links, and constraints; invent no requirements or completion criteria. Default Inbox, no parent/date, p4; creation unless preview. Record `request | title/description | project/parent/date/priority | missing | duplicate | IDs | verified | terminal`. ## 1. Resolve and clarify Use Todoist connector only. Unavailable/disconnected blocks, not substitution. Preview uses read-only metadata resolution and never creates a task/project. Resolve relative dates with user's Todoist timezone/configured week; ordinary deadline/done-by means due date, dedicated deadline only when explicitly asked and supported. Resolve project exactly, create one only if requested. Parent needs URL/ID/ unique title; subtasks have no date unless supplied or inheritance was requested. Apply future-reader test: identifiable/executable six months later without the conversation? Projects do not name tools/repos/branches/files/issues. Ask one question listing missing identifiers, create nothing that turn, then resume without another confirmation. User-accepted ambiguity is recorded. Done when metadata and references resolve or uncertainty is explicitly accepted. ## 2. Format Title: action verb + specific deliverable + necessary qualifier, sentence case, no period; aim 4–10 words, specificity wins. Preserve exact technical names. Description: short context/result sentence, bullets for distinct supplied requirements, supplied test/delivery/follow-up last. Hyperlink links. Use headings only for distinct areas of a long task; avoid imposed Objective/ Requirements/Done when boilerplate, repeated metadata, and invented work. Done when title and description stand alone and read naturally. ## 3. Preview or create Resolve project/parent and search active normalized title + parent; match → DUPLICATE. Preview shows exact payload and returns PREVIEW without write calls. Otherwise create each item once; never retry batch successes. Done when preview is sent or each creation has an ID/identified failure. ## 4. Verify Read back every created title/description/project/parent/date/priority. Correct an authorized mismatch once; remaining difference → BLOCKED with ID. Report verified title, project, parent if present, due date. Done when every reported success matches the service. Terminals: CREATED, PREVIEW, NEEDS_CONTEXT, DUPLICATE, BLOCKED.
© prathamdby · MIT · prathamdby/skills