todoist-setup
Connect Todoist to Amp for two-way task sync
- License 许可
- MIT
- 最近更新
- 2026-06-04
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- todoist-setup
- description
- Connect Todoist to Amp for two-way task sync
- integration
- { "id": "todoist", "auth": "api_key", "name": "Todoist", "sync": { "entities": "tasks", "direction": "bidirectional" }, "enhances": [ { "skill": "daily-plan", "capability": "Merges Todoist tasks due today alongside Amp tasks" }, { "skill": "triage", "capability": "Routes items to Amp, Todoist, or both" }, { "skill": "process-inbox", "capability": "Creates tasks in both systems when processing captured items" }, { "skill": "week-review", "capability": "Shows cross-system completion stats (Amp + Todoist)" } ], "mcp_server": "todoist-mcp", "new_capabilities": [ { "name": "Bidirectional task sync", "trigger": "Automatic at daily plan and task creation touchpoints" } ] }
02 资源文件 16
- 参考文档references/api-permissions.md10.0 KB
- 参考文档references/auth-best-practices.md6.1 KB
- 参考文档references/BICEP-EXAMPLE.bicep5.2 KB
- 参考文档references/cli-commands.md8.6 KB
- 参考文档references/console-app-example.md10.7 KB
- 参考文档references/first-app-registration.md7.2 KB
- 参考文档references/oauth-flows.md9.3 KB
- 参考文档references/sdk/azure-identity-dotnet.md940 B
- 参考文档references/sdk/azure-identity-java.md1.2 KB
- 参考文档references/sdk/azure-identity-py.md1.1 KB
- 参考文档references/sdk/azure-identity-rust.md805 B
- 参考文档references/sdk/azure-identity-ts.md1.1 KB
- 参考文档references/sdk/azure-keyvault-py.md1.1 KB
- 参考文档references/sdk/azure-keyvault-secrets-ts.md1.0 KB
- 参考文档references/sdk/microsoft-azure-webjobs-extensions-authentication-events-dotnet.md1.5 KB
- 参考文档references/troubleshooting.md7.4 KB
03 SKILL.md 正文
Todoist Setup
Connect your Todoist account to Amp so tasks stay in sync across both systems. Create a task in Amp and it appears in Todoist. Complete one in Todoist and Amp knows about it.
What This Enables
Once connected, Amp can:
- Daily Plan (
/daily-plan): Merge Todoist tasks due today alongside your Amp tasks - Triage (
/triage): Route new items to Amp, Todoist, or both - Process Inbox (
/process-inbox): Same routing options when processing captured items - Week Review (
/week-review): See completion stats across both Amp and Todoist
How Sync Works (Plain English)
- When you create a task in Amp, it gets pushed to Todoist automatically
- When you complete a task in Todoist, Amp picks it up during your next daily plan
- Task titles, priorities, and completion status travel between both systems
- Each system keeps its own copy — if one goes offline, the other still works
- Sync happens at natural touchpoints (daily plan, triage) — not constantly in the background
- Tasks created by Amp carry a
[amp:task-ID]marker in the description so the systems never duplicate
Privacy
- Task titles and status sync between Amp and Todoist. No task content or notes are stored beyond what you already have in both systems.
- Your API key stays local on your machine in
System/integrations/config.yaml(gitignored) - Amp never shares your Todoist data with third parties
- Tasks created in Todoist are only pulled into Amp if they were NOT originally pushed from Amp (loop prevention via
[amp:...]marker)
When to Run
- User types
/todoist-setup - User asks about connecting Todoist or task sync
- User wants Todoist tasks in daily plans
- During
/integrate-mcpif Todoist is mentioned
Setup Flow
Step 1: Check if Already Connected
- Check
System/integrations/config.yamlfor atodoist:section withenabled: true - If enabled, test the connection by listing projects with the stored API key
- If healthy, skip to Reconfiguration section below
- If not configured or unhealthy, continue to Step 2
Step 2: Explain What We're Setting Up
Say:
**Let's connect Todoist to Amp.**
Two-way task sync. Create in Amp — appears in Todoist. Complete in Todoist — done in Amp.
**What you'll need:**
- Your Todoist API token (I'll show you where to find it)
- About 2 minutes
**Ready to go?**
Wait for confirmation.
Step 3: Get the API Key
Guide the user:
To get your Todoist API token:
1. Open Todoist (web or app)
2. Go to **Settings** → **Integrations** → **Developer**
3. Copy the **API token** shown there
Paste it here when you have it.
Security note: Your API token will be stored locally in
System/integrations/config.yaml(gitignored). Never paste tokens directly in terminal commands as they persist in shell history.
Wait for the user to provide their API key. Validate it's a non-empty string (Todoist API tokens are typically 40-character hex strings).
Step 4: Add MCP Server to Config
Check the user's MCP configuration. If todoist-mcp is not listed:
- Explain:
I'll add the Todoist connector to your configuration.
This lets Amp talk to Todoist using your API token.
- Add to the user's
.mcp.json(use the/amp-add-mcpskill or manual edit):
{
"todoist-mcp": {
"command": "npx",
"args": ["-y", "todoist-mcp-server"],
"env": {
"TODOIST_API_KEY": "<user's API key>"
}
}
}
- Tell the user the MCP server needs to restart for changes to take effect.
Step 5: Test the Connection
Use the API key to list projects as a connectivity test. Run a curl or use the MCP server:
curl -s -H "Authorization: Bearer $API_KEY" https://api.todoist.com/api/v1/projects
If projects load successfully:
Connected! I can see your Todoist projects:
1. Inbox
2. Work
3. Personal
...
Looking good!
If it fails:
That API key didn't work. A few things to check:
1. **Copy the full key** — it should be about 40 characters
2. **Check for extra spaces** before or after the key
3. **Regenerate the key** in Todoist Settings → Integrations → Developer
Want to try again?
Retry up to 2 times, then offer to skip and come back later.
Step 6: Choose Default Project
Ask the user which Todoist project should receive Amp tasks:
**Which Todoist project should Amp tasks go into?**
Your projects:
1. Inbox
2. Work
3. Personal
...
You can pick one default project, or map each Amp pillar to a different project.
**Option A:** All Amp tasks go to one project (simplest)
**Option B:** Map each pillar to a project:
- Deal Support → [project]
- Thought Leadership → [project]
- Product Feedback → [project]
Which works for you?
Save their choices for the config file.
Step 7: Trust Level
Ask about sync autonomy — never use the word "tier" (per integration-patterns.md):
**How hands-on do you want to be with task sync?**
1. **"Show me first"** — I'll preview changes before syncing (recommended to start)
2. **"Keep them in sync"** — Tasks auto-sync both ways, silently
3. **"Only pull in"** — Import tasks from Todoist but don't push back
Map their choice to config values:
- Show me first →
trust_level: confirm_each - Keep them in sync →
trust_level: autonomous - Only pull in →
trust_level: read_only
Step 8: Save Configuration
Write to System/integrations/config.yaml — update the todoist section:
todoist:
enabled: true
configured_at: YYYY-MM-DD
mcp_server: todoist-mcp
auth_type: api_key
api_key: <user's API key>
task_sync: true
trust_level: <confirm_each | autonomous | read_only>
project: <default project name>
pillar_map:
deal_support: <project name or omit>
thought_leadership: <project name or omit>
product_feedback: <project name or omit>
sync_labels: []
auto_sync: true
features:
task_sync: true
external_task_merge: true
If the file already exists, only update the todoist: section. Preserve other integration configs.
Step 9: Capability Cascade
Read the integration manifest from this skill's frontmatter. Present:
**Todoist is connected!** Here's what just changed:
### Enhanced (existing skills that got smarter)
- **`/daily-plan`** → Merges Todoist tasks due today alongside your Amp tasks.
Externally-created tasks show a [Todoist] label so you know where they came from.
- **`/triage`** → Now offers routing to Amp, Todoist, or both when processing items.
- **`/process-inbox`** → Same routing — "This looks like a task. Add to Amp, Todoist, or both?"
- **`/week-review`** → Shows completion stats across both systems so you see the full picture.
### New Superpowers
- Bidirectional task sync — automatic at daily plan and task creation touchpoints.
### How It Works
- **Reading:** Todoist tasks appear in your daily plan automatically
- **Writing:** [trust level description based on user's choice above]
- **Privacy:** Task titles and status sync. Your API key stays local. No data shared with third parties.
These work automatically starting now. Run `/amp-level-up` anytime to see what else you can do.
Troubleshooting
API Key Invalid or Expired
Todoist API keys don't expire unless you regenerate them. If you see auth errors:
- Go to Todoist Settings → Integrations → Developer
- Copy the current API token (or regenerate if needed)
- Update the key by running
/todoist-setupagain
Tasks Not Syncing
A few possibilities:
- Sync only happens at touchpoints — during
/daily-plan, task creation, or/triage. There's no background sync. - Check the project mapping — if your Amp pillar maps to a project that was renamed or deleted in Todoist, tasks may go to the Inbox instead.
- Rate limits — Todoist allows 450 requests per minute. The adapter handles 429 responses with automatic retry, so this is almost never an issue.
Wrong Project
If tasks are landing in the wrong Todoist project:
- Run
/todoist-setupagain - Update the pillar-to-project mapping
- Existing tasks won't move — only new tasks use the updated mapping
Duplicate Tasks
If you see duplicates, check:
- Amp-originated tasks should have
[amp:task-...]in their Todoist description. The adapter skips these during pull-in to prevent loops. - Todoist-originated tasks that you manually add to Amp won't have a mapping in
.sync-state.jsonand may get pulled again. Mark them in Amp to create the mapping.
"Todoist MCP not found"
The Todoist adapter uses direct API calls (not MCP) for the sync bridge. The MCP server is optional but enhances other skills. Re-run /todoist-setup to detect and fix configuration.
Reconfiguration
If the user runs /todoist-setup when already configured:
- Check current config from
System/integrations/config.yaml - Test the existing API key with a project list call
- Show current mapping and trust level
- Offer options:
- Update project mapping
- Change sync behavior (trust level)
- Update API key
- Disconnect Todoist
Disconnect Flow
If user wants to disconnect:
- Update
System/integrations/config.yaml:todoist: enabled: false - Confirm: "Todoist is disconnected. Tasks will no longer sync between systems. Your existing tasks in both Amp and Todoist are unchanged. Run
/todoist-setupanytime to reconnect."
04 同仓库更多 Skills
zoom-setup
Connect Zoom to Amp for meeting recordings, scheduling, and transcript context
xray
Understand what just happened under the hood - learn AI by seeing it in action
week-review
Review week's progress with concrete accomplishments (not fake percentages), pattern detection, and goal tracking.
week-plan
Set weekly priorities and plan the week ahead with intelligent suggestions based on goals, calendar shape, and task effort.
triage
Strategically route orphaned files and extract scattered tasks
trello-setup
Connect Trello to Amp for visual Kanban task sync