things-to-todoist
Migrate tasks from Things 3 to Todoist with duplicate detection and merge support. Use when the user asks to migrate, export, sync, or move tasks from Things to Todoist.
What this skill does
# Things to Todoist Migration
Migrate tasks, projects, areas, and tags from Things 3 for Mac to Todoist with intelligent duplicate detection and merge support.
## Trigger Phrases
- `/things-to-todoist`
- "migrate things to todoist"
- "export things to todoist"
- "merge things with todoist"
## Prerequisites
### 1. Todoist MCP (Recommended)
The Todoist MCP handles rate limiting, batching, and provides a cleaner interface:
- Batch task creation with `mcp__todoist__add-tasks` (up to 50 tasks per call)
- Project/sub-project creation with `mcp__todoist__add-projects`
- Project lookup with `mcp__todoist__find-projects`
- Task search with `mcp__todoist__find-tasks`
---
## Todoist Usage Limits
Understanding these limits is critical for large migrations. Source: [Todoist Help](https://www.todoist.com/help/articles/usage-limits-in-todoist-e5rcSY)
### Per-Project Limits (All Plans)
| Resource | Limit |
|----------|-------|
| **Active tasks per project** | **300** <- Most common migration blocker |
| Sections per project | 20 |
| Task name | 500 characters |
| Task description | 16,383 characters |
| Task comment | 15,000 characters |
| Labels per task | 100 |
### Account Limits
| Resource | Beginner | Pro |
|----------|----------|-----|
| Active personal projects | 5 | 300 |
| Total active projects | 500 | 500 |
| Labels per account | 500 | 500 |
| Filters | 3 | 150 |
### API Limits
| Limit | Value |
|-------|-------|
| Sync API commands per request | 100 |
| Rate limit | ~450 requests per 15 minutes |
| Rate limit response | HTTP 429 |
| Project limit response | HTTP 403 with `MAX_ITEMS_LIMIT_REACHED` |
### Workaround: Sub-Projects
When a project hits the 300-task limit, create sub-projects:
```
mcp__todoist__add-projects({
"projects": [{"name": "Work Backlog", "parentId": "WORK_PROJECT_ID"}]
})
```
Sub-projects have their own separate 300-task limit, effectively extending capacity.
### 2. Python Libraries (for Things export)
```bash
uv pip install things.py thefuzz python-Levenshtein
```
### 3. Things 3 Must Be Installed
The `things.py` library reads directly from the Things SQLite database at:
```
~/Library/Group Containers/JLMPQHK86H.com.culturedcode.ThingsMac/Things Database.thingsdatabase/main.sqlite
```
## Concept Mapping
| Things 3 | Todoist | Notes |
|----------|---------|-------|
| Area | Project | Top-level organizational container |
| Project | Section or Sub-project | Can be nested under Area's project |
| Heading | Section | Dividers within projects |
| To-Do | Task | Individual actionable items |
| Checklist Item | Subtask | Nested under parent task |
| Tag | Label | Applied to tasks |
| Notes | Description | Task description field |
| When (Today/Evening/Anytime/Someday) | Priority + Due Date | Map scheduling to Todoist equivalents |
| Deadline | Due Date | Direct mapping |
## Workflow Overview
This is an **interactive migration** with user decision points:
1. **Export** - Extract data from Things
2. **Fetch** - Get current Todoist state
3. **Analyze** - Detect duplicates and conflicts
4. **Present** - Show merge report to user
5. **Decide** - User chooses merge strategy per conflict
6. **Execute** - Apply decisions
7. **Verify** - Confirm results
---
## Step 1: Retrieve Todoist API Token
```bash
# If using 1Password
op item get "Todoist" --fields "API Token"
# Or use environment variable
echo $TODOIST_API_TOKEN
```
---
## Step 2: Export Both Systems
### Export Things Data
```python
#!/usr/bin/env python3
"""Extract all data from Things 3 for migration."""
import things
import json
from datetime import datetime
def export_things_data():
"""Export complete Things database to structured dict."""
data = {
"exported_at": datetime.now().isoformat(),
"source": "things",
"areas": [],
"projects": [],
"todos": [],
"tags": []
}
# Export areas
for area in things.areas():
data["areas"].append({
"uuid": area.get("uuid"),
"title": area.get("title"),
"tags": area.get("tags", [])
})
# Export projects (including area association)
for project in things.projects(include_items=True):
data["projects"].append({
"uuid": project.get("uuid"),
"title": project.get("title"),
"area_uuid": project.get("area"),
"notes": project.get("notes", ""),
"tags": project.get("tags", []),
"status": project.get("status"),
"deadline": project.get("deadline"),
"items": project.get("items", []) # Headings and todos
})
# Export standalone todos (not in projects)
for todo in things.todos():
if not todo.get("project"):
data["todos"].append({
"uuid": todo.get("uuid"),
"title": todo.get("title"),
"area_uuid": todo.get("area"),
"notes": todo.get("notes", ""),
"tags": todo.get("tags", []),
"status": todo.get("status"),
"when": todo.get("when"),
"deadline": todo.get("deadline"),
"checklist": todo.get("checklist", [])
})
# Export tags
for tag in things.tags():
data["tags"].append({
"uuid": tag.get("uuid"),
"title": tag.get("title"),
"parent_uuid": tag.get("parent")
})
return data
if __name__ == "__main__":
data = export_things_data()
with open("things_export.json", "w") as f:
json.dump(data, f, indent=2, default=str)
print(f"Exported: {len(data['areas'])} areas, {len(data['projects'])} projects, "
f"{len(data['todos'])} standalone todos, {len(data['tags'])} tags")
```
### Export Todoist Data
```python
#!/usr/bin/env python3
"""Export current Todoist state for comparison."""
import json
import os
from todoist_api_python.api import TodoistAPI
def export_todoist_data(api_token: str):
"""Export complete Todoist state to structured dict."""
api = TodoistAPI(api_token)
data = {
"source": "todoist",
"projects": [],
"sections": [],
"tasks": [],
"labels": []
}
# Export projects
for project in api.get_projects():
data["projects"].append({
"id": project.id,
"name": project.name,
"parent_id": project.parent_id,
"color": project.color,
"is_favorite": project.is_favorite
})
# Export sections
for section in api.get_sections():
data["sections"].append({
"id": section.id,
"name": section.name,
"project_id": section.project_id,
"order": section.order
})
# Export tasks (active only)
for task in api.get_tasks():
data["tasks"].append({
"id": task.id,
"content": task.content,
"description": task.description or "",
"project_id": task.project_id,
"section_id": task.section_id,
"parent_id": task.parent_id,
"labels": task.labels,
"priority": task.priority,
"due": task.due.string if task.due else None,
"is_completed": task.is_completed
})
# Export labels
for label in api.get_labels():
data["labels"].append({
"id": label.id,
"name": label.name,
"color": label.color
})
return data
if __name__ == "__main__":
token = os.environ.get("TODOIST_API_TOKEN")
data = export_todoist_data(token)
with open("todoist_export.json", "w") as f:
json.dump(data, f, indent=2)
print(f"Exported: {len(data['projects'])} projects, {len(data['sections'])} sections, "
f"{len(data['tasks'])} tasks, {len(data['labels'])} labels")
```
---
## Step 3: Analyze and Detect Conflicts
Use fuzzy matching to detect duplicates:
```python
#!/usr/bin/envRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.