todoist-api-7-sync-api
Sub-skill of todoist-api: 7. Sync API.
Best use case
todoist-api-7-sync-api is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of todoist-api: 7. Sync API.
Teams using todoist-api-7-sync-api 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/7-sync-api/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How todoist-api-7-sync-api Compares
| Feature / Agent | todoist-api-7-sync-api | 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?
Sub-skill of todoist-api: 7. Sync API.
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
# 7. Sync API
## 7. Sync API
**Sync API Basics:**
```bash
# Initial sync (full read)
curl -s -X POST "https://api.todoist.com/sync/v9/sync" \
-H "Authorization: Bearer $TODOIST_API_KEY" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "sync_token=*&resource_types=[\"all\"]" | jq
# Incremental sync (with sync token)
SYNC_TOKEN="your-sync-token-from-previous-response"
curl -s -X POST "https://api.todoist.com/sync/v9/sync" \
-H "Authorization: Bearer $TODOIST_API_KEY" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "sync_token=$SYNC_TOKEN&resource_types=[\"items\",\"projects\"]" | jq
# Batch operations with commands
curl -s -X POST "https://api.todoist.com/sync/v9/sync" \
-H "Authorization: Bearer $TODOIST_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"commands": [
{
"type": "item_add",
"temp_id": "temp1",
"uuid": "unique-uuid-1",
"args": {
"content": "Task 1",
"project_id": "PROJECT_ID"
}
},
{
"type": "item_add",
"temp_id": "temp2",
"uuid": "unique-uuid-2",
"args": {
"content": "Task 2",
"project_id": "PROJECT_ID"
}
}
]
}' | jq
```
**Python Sync Operations:**
```python
import requests
import json
import uuid
TODOIST_API_KEY = os.environ["TODOIST_API_KEY"]
SYNC_URL = "https://api.todoist.com/sync/v9/sync"
def sync_read(sync_token="*", resource_types=None):
"""Read data using Sync API"""
if resource_types is None:
resource_types = ["all"]
response = requests.post(
SYNC_URL,
headers={"Authorization": f"Bearer {TODOIST_API_KEY}"},
data={
"sync_token": sync_token,
"resource_types": json.dumps(resource_types)
}
)
return response.json()
def batch_add_tasks(tasks):
"""Add multiple tasks in one request"""
commands = []
for task in tasks:
commands.append({
"type": "item_add",
"temp_id": f"temp_{uuid.uuid4().hex[:8]}",
"uuid": str(uuid.uuid4()),
"args": task
})
response = requests.post(
SYNC_URL,
headers={
"Authorization": f"Bearer {TODOIST_API_KEY}",
"Content-Type": "application/json"
},
json={"commands": commands}
)
return response.json()
# Example: Add multiple tasks at once
tasks_to_add = [
{"content": "Task 1", "project_id": "2345678901", "priority": 4},
{"content": "Task 2", "project_id": "2345678901", "priority": 3},
{"content": "Task 3", "project_id": "2345678901", "priority": 2},
]
result = batch_add_tasks(tasks_to_add)
print(f"Added {len(tasks_to_add)} tasks")
```Related Skills
worktree-branch-sync-hygiene
Class-level branch, worktree, dirty-main, stash, sync, and hook hygiene for workspace-hub style multi-repo work.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
multi-repo-sync-diagnosis-repair
Diagnose and repair failed pulls across multi-repo ecosystems with stale locks, submodule conflicts, and untracked files
multi-repo-sync-diagnosis-and-repair
Systematic approach to diagnosing and repairing failures across a multi-repo workspace
workspace-hub-sync-root-churn-catchup
Catch up workspace-hub root changes that continue to appear during repo sync because live review/agent processes keep writing files after commits
workspace-hub-sync-concurrent-writer-blocks
Handle repository_sync cleanup when workspace-hub root is being mutated by concurrent Codex/Codex/Gemini sessions.
user-approved-plan-state-sync
Reconcile GitHub and local repo state when a plan has been user-approved, including direct approval messages that require creating the local marker and moving the issue to status:plan-approved.
repo-sync-deleted-remote-branch-and-unrelated-history-recovery
Recover multi-repo sync failures caused by deleted upstream branches, stale git index locks, and local branches with unrelated history to the remote default branch.
plan-rerun-review-state-sync
Keep iterative plan-review reruns truthful by syncing prompt files, canonical review artifacts, and the plan's own review-summary narrative after each adversarial wave.
github-sync
Multi-repository synchronization coordinator for version alignment, dependency sync, and cross-package integration. Use for package synchronization, version management, documentation alignment, and coordinated releases across multiple repositories.
git-sync-manager-5-safe-branch-operations
Sub-skill of git-sync-manager: 5. Safe Branch Operations.
git-sync-manager-3-repository-status-check
Sub-skill of git-sync-manager: 3. Repository Status Check (+1).