[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3D8S2YSHSB0BN73W9HA0W":3,"skill-same:01M6D3D8S2YSHSB0BN73W9HA0W":163},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":6,"ownerHtmlUrl":79,"ownerBlogUrl":80,"ownerDescription":81,"updatedAt":82,"install":83,"resources":96},"01M6D3D8S2YSHSB0BN73W9HA0W","todoist-setup",null,"Connect Todoist to Amp for two-way task sync","hemory\u002Famp-legacy-do-not-use","hemory","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21179881?v=4","01M6D31HFJ391DN8N0JP8AQGFE","Hemory Phifer","01M6D31HKXVTEN27AT6R4PP2ZJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftodoist-setup\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"todoist setup","setup","todoist","plan","daily plan","systems","creation","task","daily","process","system","MCP","api","stats","inbox","connect","tasks","sync","triage","review","2026-11-10 10:12:30",false,"---\nname: todoist-setup\ndescription: Connect Todoist to Amp for two-way task sync\nintegration:\n  id: todoist\n  name: Todoist\n  mcp_server: todoist-mcp\n  auth: api_key\n  enhances:\n    - skill: daily-plan\n      capability: \"Merges Todoist tasks due today alongside Amp tasks\"\n    - skill: triage\n      capability: \"Routes items to Amp, Todoist, or both\"\n    - skill: process-inbox\n      capability: \"Creates tasks in both systems when processing captured items\"\n    - skill: week-review\n      capability: \"Shows cross-system completion stats (Amp + Todoist)\"\n  new_capabilities:\n    - name: Bidirectional task sync\n      trigger: \"Automatic at daily plan and task creation touchpoints\"\n  sync:\n    direction: bidirectional\n    entities: tasks\n---\n\n# Todoist Setup\n\nConnect 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.\n\n## What This Enables\n\nOnce connected, Amp can:\n- **Daily Plan** (`\u002Fdaily-plan`): Merge Todoist tasks due today alongside your Amp tasks\n- **Triage** (`\u002Ftriage`): Route new items to Amp, Todoist, or both\n- **Process Inbox** (`\u002Fprocess-inbox`): Same routing options when processing captured items\n- **Week Review** (`\u002Fweek-review`): See completion stats across both Amp and Todoist\n\n## How Sync Works (Plain English)\n\n- When you create a task in Amp, it gets pushed to Todoist automatically\n- When you complete a task in Todoist, Amp picks it up during your next daily plan\n- Task titles, priorities, and completion status travel between both systems\n- Each system keeps its own copy — if one goes offline, the other still works\n- Sync happens at natural touchpoints (daily plan, triage) — not constantly in the background\n- Tasks created by Amp carry a `[amp:task-ID]` marker in the description so the systems never duplicate\n\n## Privacy\n\n- Task titles and status sync between Amp and Todoist. No task content or notes are stored beyond what you already have in both systems.\n- Your API key stays local on your machine in `System\u002Fintegrations\u002Fconfig.yaml` (gitignored)\n- Amp never shares your Todoist data with third parties\n- Tasks created in Todoist are only pulled into Amp if they were NOT originally pushed from Amp (loop prevention via `[amp:...]` marker)\n\n## When to Run\n\n- User types `\u002Ftodoist-setup`\n- User asks about connecting Todoist or task sync\n- User wants Todoist tasks in daily plans\n- During `\u002Fintegrate-mcp` if Todoist is mentioned\n\n---\n\n## Setup Flow\n\n### Step 1: Check if Already Connected\n\n1. Check `System\u002Fintegrations\u002Fconfig.yaml` for a `todoist:` section with `enabled: true`\n2. If enabled, test the connection by listing projects with the stored API key\n3. If healthy, skip to **Reconfiguration** section below\n4. If not configured or unhealthy, continue to Step 2\n\n### Step 2: Explain What We're Setting Up\n\nSay:\n\n```\n**Let's connect Todoist to Amp.**\n\nTwo-way task sync. Create in Amp — appears in Todoist. Complete in Todoist — done in Amp.\n\n**What you'll need:**\n- Your Todoist API token (I'll show you where to find it)\n- About 2 minutes\n\n**Ready to go?**\n```\n\nWait for confirmation.\n\n### Step 3: Get the API Key\n\nGuide the user:\n\n```\nTo get your Todoist API token:\n\n1. Open Todoist (web or app)\n2. Go to **Settings** → **Integrations** → **Developer**\n3. Copy the **API token** shown there\n\nPaste it here when you have it.\n```\n\n> **Security note:** Your API token will be stored locally in `System\u002Fintegrations\u002Fconfig.yaml` (gitignored). Never paste tokens directly in terminal commands as they persist in shell history.\n\nWait for the user to provide their API key. Validate it's a non-empty string (Todoist API tokens are typically 40-character hex strings).\n\n### Step 4: Add MCP Server to Config\n\nCheck the user's MCP configuration. If `todoist-mcp` is not listed:\n\n1. Explain:\n\n```\nI'll add the Todoist connector to your configuration.\nThis lets Amp talk to Todoist using your API token.\n```\n\n2. Add to the user's `.mcp.json` (use the `\u002Famp-add-mcp` skill or manual edit):\n\n```json\n{\n  \"todoist-mcp\": {\n    \"command\": \"npx\",\n    \"args\": [\"-y\", \"todoist-mcp-server\"],\n    \"env\": {\n      \"TODOIST_API_KEY\": \"\u003Cuser's API key>\"\n    }\n  }\n}\n```\n\n3. Tell the user the MCP server needs to restart for changes to take effect.\n\n### Step 5: Test the Connection\n\nUse the API key to list projects as a connectivity test. Run a curl or use the MCP server:\n\n```bash\ncurl -s -H \"Authorization: Bearer $API_KEY\" https:\u002F\u002Fapi.todoist.com\u002Fapi\u002Fv1\u002Fprojects\n```\n\n**If projects load successfully:**\n\n```\nConnected! I can see your Todoist projects:\n\n1. Inbox\n2. Work\n3. Personal\n...\n\nLooking good!\n```\n\n**If it fails:**\n\n```\nThat API key didn't work. A few things to check:\n\n1. **Copy the full key** — it should be about 40 characters\n2. **Check for extra spaces** before or after the key\n3. **Regenerate the key** in Todoist Settings → Integrations → Developer\n\nWant to try again?\n```\n\nRetry up to 2 times, then offer to skip and come back later.\n\n### Step 6: Choose Default Project\n\nAsk the user which Todoist project should receive Amp tasks:\n\n```\n**Which Todoist project should Amp tasks go into?**\n\nYour projects:\n1. Inbox\n2. Work\n3. Personal\n...\n\nYou can pick one default project, or map each Amp pillar to a different project.\n\n**Option A:** All Amp tasks go to one project (simplest)\n**Option B:** Map each pillar to a project:\n  - Deal Support → [project]\n  - Thought Leadership → [project]\n  - Product Feedback → [project]\n\nWhich works for you?\n```\n\nSave their choices for the config file.\n\n### Step 7: Trust Level\n\nAsk about sync autonomy — **never use the word \"tier\"** (per integration-patterns.md):\n\n```\n**How hands-on do you want to be with task sync?**\n\n1. **\"Show me first\"** — I'll preview changes before syncing (recommended to start)\n2. **\"Keep them in sync\"** — Tasks auto-sync both ways, silently\n3. **\"Only pull in\"** — Import tasks from Todoist but don't push back\n```\n\nMap their choice to config values:\n- **Show me first** → `trust_level: confirm_each`\n- **Keep them in sync** → `trust_level: autonomous`\n- **Only pull in** → `trust_level: read_only`\n\n### Step 8: Save Configuration\n\nWrite to `System\u002Fintegrations\u002Fconfig.yaml` — update the todoist section:\n\n```yaml\ntodoist:\n  enabled: true\n  configured_at: YYYY-MM-DD\n  mcp_server: todoist-mcp\n  auth_type: api_key\n  api_key: \u003Cuser's API key>\n  task_sync: true\n  trust_level: \u003Cconfirm_each | autonomous | read_only>\n  project: \u003Cdefault project name>\n  pillar_map:\n    deal_support: \u003Cproject name or omit>\n    thought_leadership: \u003Cproject name or omit>\n    product_feedback: \u003Cproject name or omit>\n  sync_labels: []\n  auto_sync: true\n  features:\n    task_sync: true\n    external_task_merge: true\n```\n\nIf the file already exists, only update the `todoist:` section. Preserve other integration configs.\n\n### Step 9: Capability Cascade\n\nRead the integration manifest from this skill's frontmatter. Present:\n\n```\n**Todoist is connected!** Here's what just changed:\n\n### Enhanced (existing skills that got smarter)\n\n- **`\u002Fdaily-plan`** → Merges Todoist tasks due today alongside your Amp tasks.\n  Externally-created tasks show a [Todoist] label so you know where they came from.\n\n- **`\u002Ftriage`** → Now offers routing to Amp, Todoist, or both when processing items.\n\n- **`\u002Fprocess-inbox`** → Same routing — \"This looks like a task. Add to Amp, Todoist, or both?\"\n\n- **`\u002Fweek-review`** → Shows completion stats across both systems so you see the full picture.\n\n### New Superpowers\n\n- Bidirectional task sync — automatic at daily plan and task creation touchpoints.\n\n### How It Works\n\n- **Reading:** Todoist tasks appear in your daily plan automatically\n- **Writing:** [trust level description based on user's choice above]\n- **Privacy:** Task titles and status sync. Your API key stays local. No data shared with third parties.\n\nThese work automatically starting now. Run `\u002Famp-level-up` anytime to see what else you can do.\n```\n\n---\n\n## Troubleshooting\n\n### API Key Invalid or Expired\n\nTodoist API keys don't expire unless you regenerate them. If you see auth errors:\n\n1. Go to Todoist Settings → Integrations → Developer\n2. Copy the current API token (or regenerate if needed)\n3. Update the key by running `\u002Ftodoist-setup` again\n\n### Tasks Not Syncing\n\nA few possibilities:\n- **Sync only happens at touchpoints** — during `\u002Fdaily-plan`, task creation, or `\u002Ftriage`. There's no background sync.\n- **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.\n- **Rate limits** — Todoist allows 450 requests per minute. The adapter handles 429 responses with automatic retry, so this is almost never an issue.\n\n### Wrong Project\n\nIf tasks are landing in the wrong Todoist project:\n1. Run `\u002Ftodoist-setup` again\n2. Update the pillar-to-project mapping\n3. Existing tasks won't move — only new tasks use the updated mapping\n\n### Duplicate Tasks\n\nIf you see duplicates, check:\n- **Amp-originated tasks** should have `[amp:task-...]` in their Todoist description. The adapter skips these during pull-in to prevent loops.\n- **Todoist-originated tasks** that you manually add to Amp won't have a mapping in `.sync-state.json` and may get pulled again. Mark them in Amp to create the mapping.\n\n### \"Todoist MCP not found\"\n\nThe Todoist adapter uses direct API calls (not MCP) for the sync bridge. The MCP server is optional but enhances other skills. Re-run `\u002Ftodoist-setup` to detect and fix configuration.\n\n---\n\n## Reconfiguration\n\nIf the user runs `\u002Ftodoist-setup` when already configured:\n\n1. Check current config from `System\u002Fintegrations\u002Fconfig.yaml`\n2. Test the existing API key with a project list call\n3. Show current mapping and trust level\n4. Offer options:\n   - Update project mapping\n   - Change sync behavior (trust level)\n   - Update API key\n   - Disconnect Todoist\n\n### Disconnect Flow\n\nIf user wants to disconnect:\n\n1. Update `System\u002Fintegrations\u002Fconfig.yaml`:\n   ```yaml\n   todoist:\n     enabled: false\n   ```\n2. Confirm: \"Todoist is disconnected. Tasks will no longer sync between systems. Your existing tasks in both Amp and Todoist are unchanged. Run `\u002Ftodoist-setup` anytime to reconnect.\"\n","# Todoist Setup\n\nConnect 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.\n\n## What This Enables\n\nOnce connected, Amp can:\n- **Daily Plan** (`\u002Fdaily-plan`): Merge Todoist tasks due today alongside your Amp tasks\n- **Triage** (`\u002Ftriage`): Route new items to Amp, Todoist, or both\n- **Process Inbox** (`\u002Fprocess-inbox`): Same routing options when processing captured items\n- **Week Review** (`\u002Fweek-review`): See completion stats across both Amp and Todoist\n\n## How Sync Works (Plain English)\n\n- When you create a task in Amp, it gets pushed to Todoist automatically\n- When you complete a task in Todoist, Amp picks it up during your next daily plan\n- Task titles, priorities, and completion status travel between both systems\n- Each system keeps its own copy — if one goes offline, the other still works\n- Sync happens at natural touchpoints (daily plan, triage) — not constantly in the background\n- Tasks created by Amp carry a `[amp:task-ID]` marker in the description so the systems never duplicate\n\n## Privacy\n\n- Task titles and status sync between Amp and Todoist. No task content or notes are stored beyond what you already have in both systems.\n- Your API key stays local on your machine in `System\u002Fintegrations\u002Fconfig.yaml` (gitignored)\n- Amp never shares your Todoist data with third parties\n- Tasks created in Todoist are only pulled into Amp if they were NOT originally pushed from Amp (loop prevention via `[amp:...]` marker)\n\n## When to Run\n\n- User types `\u002Ftodoist-setup`\n- User asks about connecting Todoist or task sync\n- User wants Todoist tasks in daily plans\n- During `\u002Fintegrate-mcp` if Todoist is mentioned\n\n---\n\n## Setup Flow\n\n### Step 1: Check if Already Connected\n\n1. Check `System\u002Fintegrations\u002Fconfig.yaml` for a `todoist:` section with `enabled: true`\n2. If enabled, test the connection by listing projects with the stored API key\n3. If healthy, skip to **Reconfiguration** section below\n4. If not configured or unhealthy, continue to Step 2\n\n### Step 2: Explain What We're Setting Up\n\nSay:\n\n```\n**Let's connect Todoist to Amp.**\n\nTwo-way task sync. Create in Amp — appears in Todoist. Complete in Todoist — done in Amp.\n\n**What you'll need:**\n- Your Todoist API token (I'll show you where to find it)\n- About 2 minutes\n\n**Ready to go?**\n```\n\nWait for confirmation.\n\n### Step 3: Get the API Key\n\nGuide the user:\n\n```\nTo get your Todoist API token:\n\n1. Open Todoist (web or app)\n2. Go to **Settings** → **Integrations** → **Developer**\n3. Copy the **API token** shown there\n\nPaste it here when you have it.\n```\n\n> **Security note:** Your API token will be stored locally in `System\u002Fintegrations\u002Fconfig.yaml` (gitignored). Never paste tokens directly in terminal commands as they persist in shell history.\n\nWait for the user to provide their API key. Validate it's a non-empty string (Todoist API tokens are typically 40-character hex strings).\n\n### Step 4: Add MCP Server to Config\n\nCheck the user's MCP configuration. If `todoist-mcp` is not listed:\n\n1. Explain:\n\n```\nI'll add the Todoist connector to your configuration.\nThis lets Amp talk to Todoist using your API token.\n```\n\n2. Add to the user's `.mcp.json` (use the `\u002Famp-add-mcp` skill or manual edit):\n\n```json\n{\n  \"todoist-mcp\": {\n    \"command\": \"npx\",\n    \"args\": [\"-y\", \"todoist-mcp-server\"],\n    \"env\": {\n      \"TODOIST_API_KEY\": \"\u003Cuser's API key>\"\n    }\n  }\n}\n```\n\n3. Tell the user the MCP server needs to restart for changes to take effect.\n\n### Step 5: Test the Connection\n\nUse the API key to list projects as a connectivity test. Run a curl or use the MCP server:\n\n```bash\ncurl -s -H \"Authorization: Bearer $API_KEY\" https:\u002F\u002Fapi.todoist.com\u002Fapi\u002Fv1\u002Fprojects\n```\n\n**If projects load successfully:**\n\n```\nConnected! I can see your Todoist projects:\n\n1. Inbox\n2. Work\n3. Personal\n...\n\nLooking good!\n```\n\n**If it fails:**\n\n```\nThat API key didn't work. A few things to check:\n\n1. **Copy the full key** — it should be about 40 characters\n2. **Check for extra spaces** before or after the key\n3. **Regenerate the key** in Todoist Settings → Integrations → Developer\n\nWant to try again?\n```\n\nRetry up to 2 times, then offer to skip and come back later.\n\n### Step 6: Choose Default Project\n\nAsk the user which Todoist project should receive Amp tasks:\n\n```\n**Which Todoist project should Amp tasks go into?**\n\nYour projects:\n1. Inbox\n2. Work\n3. Personal\n...\n\nYou can pick one default project, or map each Amp pillar to a different project.\n\n**Option A:** All Amp tasks go to one project (simplest)\n**Option B:** Map each pillar to a project:\n  - Deal Support → [project]\n  - Thought Leadership → [project]\n  - Product Feedback → [project]\n\nWhich works for you?\n```\n\nSave their choices for the config file.\n\n### Step 7: Trust Level\n\nAsk about sync autonomy — **never use the word \"tier\"** (per integration-patterns.md):\n\n```\n**How hands-on do you want to be with task sync?**\n\n1. **\"Show me first\"** — I'll preview changes before syncing (recommended to start)\n2. **\"Keep them in sync\"** — Tasks auto-sync both ways, silently\n3. **\"Only pull in\"** — Import tasks from Todoist but don't push back\n```\n\nMap their choice to config values:\n- **Show me first** → `trust_level: confirm_each`\n- **Keep them in sync** → `trust_level: autonomous`\n- **Only pull in** → `trust_level: read_only`\n\n### Step 8: Save Configuration\n\nWrite to `System\u002Fintegrations\u002Fconfig.yaml` — update the todoist section:\n\n```yaml\ntodoist:\n  enabled: true\n  configured_at: YYYY-MM-DD\n  mcp_server: todoist-mcp\n  auth_type: api_key\n  api_key: \u003Cuser's API key>\n  task_sync: true\n  trust_level: \u003Cconfirm_each | autonomous | read_only>\n  project: \u003Cdefault project name>\n  pillar_map:\n    deal_support: \u003Cproject name or omit>\n    thought_leadership: \u003Cproject name or omit>\n    product_feedback: \u003Cproject name or omit>\n  sync_labels: []\n  auto_sync: true\n  features:\n    task_sync: true\n    external_task_merge: true\n```\n\nIf the file already exists, only update the `todoist:` section. Preserve other integration configs.\n\n### Step 9: Capability Cascade\n\nRead the integration manifest from this skill's frontmatter. Present:\n\n```\n**Todoist is connected!** Here's what just changed:\n\n### Enhanced (existing skills that got smarter)\n\n- **`\u002Fdaily-plan`** → Merges Todoist tasks due today alongside your Amp tasks.\n  Externally-created tasks show a [Todoist] label so you know where they came from.\n\n- **`\u002Ftriage`** → Now offers routing to Amp, Todoist, or both when processing items.\n\n- **`\u002Fprocess-inbox`** → Same routing — \"This looks like a task. Add to Amp, Todoist, or both?\"\n\n- **`\u002Fweek-review`** → Shows completion stats across both systems so you see the full picture.\n\n### New Superpowers\n\n- Bidirectional task sync — automatic at daily plan and task creation touchpoints.\n\n### How It Works\n\n- **Reading:** Todoist tasks appear in your daily plan automatically\n- **Writing:** [trust level description based on user's choice above]\n- **Privacy:** Task titles and status sync. Your API key stays local. No data shared with third parties.\n\nThese work automatically starting now. Run `\u002Famp-level-up` anytime to see what else you can do.\n```\n\n---\n\n## Troubleshooting\n\n### API Key Invalid or Expired\n\nTodoist API keys don't expire unless you regenerate them. If you see auth errors:\n\n1. Go to Todoist Settings → Integrations → Developer\n2. Copy the current API token (or regenerate if needed)\n3. Update the key by running `\u002Ftodoist-setup` again\n\n### Tasks Not Syncing\n\nA few possibilities:\n- **Sync only happens at touchpoints** — during `\u002Fdaily-plan`, task creation, or `\u002Ftriage`. There's no background sync.\n- **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.\n- **Rate limits** — Todoist allows 450 requests per minute. The adapter handles 429 responses with automatic retry, so this is almost never an issue.\n\n### Wrong Project\n\nIf tasks are landing in the wrong Todoist project:\n1. Run `\u002Ftodoist-setup` again\n2. Update the pillar-to-project mapping\n3. Existing tasks won't move — only new tasks use the updated mapping\n\n### Duplicate Tasks\n\nIf you see duplicates, check:\n- **Amp-originated tasks** should have `[amp:task-...]` in their Todoist description. The adapter skips these during pull-in to prevent loops.\n- **Todoist-originated tasks** that you manually add to Amp won't have a mapping in `.sync-state.json` and may get pulled again. Mark them in Amp to create the mapping.\n\n### \"Todoist MCP not found\"\n\nThe Todoist adapter uses direct API calls (not MCP) for the sync bridge. The MCP server is optional but enhances other skills. Re-run `\u002Ftodoist-setup` to detect and fix configuration.\n\n---\n\n## Reconfiguration\n\nIf the user runs `\u002Ftodoist-setup` when already configured:\n\n1. Check current config from `System\u002Fintegrations\u002Fconfig.yaml`\n2. Test the existing API key with a project list call\n3. Show current mapping and trust level\n4. Offer options:\n   - Update project mapping\n   - Change sync behavior (trust level)\n   - Update API key\n   - Disconnect Todoist\n\n### Disconnect Flow\n\nIf user wants to disconnect:\n\n1. Update `System\u002Fintegrations\u002Fconfig.yaml`:\n   ```yaml\n   todoist:\n     enabled: false\n   ```\n2. Confirm: \"Todoist is disconnected. Tasks will no longer sync between systems. Your existing tasks in both Amp and Todoist are unchanged. Run `\u002Ftodoist-setup` anytime to reconnect.\"\n",{"name":5,"description":7,"integration":52},{"id":29,"auth":53,"name":54,"sync":55,"enhances":57,"mcp_server":69,"new_capabilities":70},"api_key","Todoist",{"entities":43,"direction":56},"bidirectional",[58,61,63,66],{"skill":59,"capability":60},"daily-plan","Merges Todoist tasks due today alongside Amp tasks",{"skill":45,"capability":62},"Routes items to Amp, Todoist, or both",{"skill":64,"capability":65},"process-inbox","Creates tasks in both systems when processing captured items",{"skill":67,"capability":68},"week-review","Shows cross-system completion stats (Amp + Todoist)","todoist-mcp",[71],{"name":72,"trigger":73},"Bidirectional task sync","Automatic at daily plan and task creation touchpoints","main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Ftodoist-setup",0,"https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use","https:\u002F\u002Fgithub.com\u002Fhemory","https:\u002F\u002Fwww.heminthehat.com\u002F","The People Developer | L&D Program Manager | Software Engineer","2026-06-04 23:46:30",{"source":8,"skillName":5,"commands":84,"prompt":94,"zipAvailable":95},[85,88,91],{"tool":86,"command":87},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill todoist-setup",{"tool":89,"command":90},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill todoist-setup",{"tool":92,"command":93},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill todoist-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftodoist-setup\u002FSKILL.md",true,[97,103,107,111,115,119,123,127,131,135,139,143,147,151,155,159],{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-permissions.md","REFERENCE","参考文档",10198,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fapi-permissions.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fauth-best-practices.md",6207,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fauth-best-practices.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002FBICEP-EXAMPLE.bicep",5328,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002FBICEP-EXAMPLE.bicep",{"path":112,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fcli-commands.md",8852,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fcli-commands.md",{"path":116,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fconsole-app-example.md",11005,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fconsole-app-example.md",{"path":120,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Ffirst-app-registration.md",7415,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Ffirst-app-registration.md",{"path":124,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Foauth-flows.md",9540,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Foauth-flows.md",{"path":128,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fsdk\u002Fazure-identity-dotnet.md",940,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-identity-dotnet.md",{"path":132,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fsdk\u002Fazure-identity-java.md",1248,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-identity-java.md",{"path":136,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fsdk\u002Fazure-identity-py.md",1148,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-identity-py.md",{"path":140,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fsdk\u002Fazure-identity-rust.md",805,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-identity-rust.md",{"path":144,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fsdk\u002Fazure-identity-ts.md",1144,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-identity-ts.md",{"path":148,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":149,"sourceHtmlUrl":150},"references\u002Fsdk\u002Fazure-keyvault-py.md",1135,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-keyvault-py.md",{"path":152,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":153,"sourceHtmlUrl":154},"references\u002Fsdk\u002Fazure-keyvault-secrets-ts.md",1043,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fazure-keyvault-secrets-ts.md",{"path":156,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":157,"sourceHtmlUrl":158},"references\u002Fsdk\u002Fmicrosoft-azure-webjobs-extensions-authentication-events-dotnet.md",1522,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Fsdk\u002Fmicrosoft-azure-webjobs-extensions-authentication-events-dotnet.md",{"path":160,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":161,"sourceHtmlUrl":162},"references\u002Ftroubleshooting.md",7594,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fentra-app-registration\u002Freferences\u002Ftroubleshooting.md",[164,191,200,213,226,236],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":176,"publishedAt":47},"01M6D3DVEAHJTTK4W21B15ZZKK","zoom-setup","Connect Zoom to Amp for meeting recordings, scheduling, and transcript context","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzoom-setup\u002FSKILL.md",[170,171],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":172,"categoryName":173,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[177,28,178,38,46,42,179,180,40,181,182,183,184,36,185,186,187,188,189,190],"zoom setup","schedule","transcript","search","oauth2","confirmation","context","meetings","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":47},"01M6D3DRAK8VWESYDZDF8JJDSH","xray","Understand what just happened under the hood - learn AI by seeing it in action","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxray\u002FSKILL.md",[],[193,198,199],"learn","just",{"skillNo":201,"name":67,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":47},"01M6D3DN7BZQDY6143A2QSDP9A","Review week's progress with concrete accomplishments (not fake percentages), pattern detection, and goal tracking.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-review\u002FSKILL.md",[205],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[207,46,208,209,210,211,212],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":47},"01M6D3DJ7F1TCFXBBSTQW82WE7","week-plan","Set weekly priorities and plan the week ahead with intelligent suggestions based on goals, calendar shape, and task effort.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-plan\u002FSKILL.md",[],[220,30,221,222,223,224,34,225],"week plan","calendar","SET","shape","goals","priorities",{"skillNo":227,"name":45,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":231,"publishedAt":47},"01M6D3DF90D7RC8ZJE4AW2P9VC","Strategically route orphaned files and extract scattered tasks","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[45,43,232,233,234,235],"fast","extract","files","route",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":244,"publishedAt":47},"01M6D3DC9BBHK5TASE34SQYXSQ","trello-setup","Connect Trello to Amp for visual Kanban task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftrello-setup\u002FSKILL.md",[242,243],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,28,44,42,38,247,34,248,249,250,39,251],"trello","trello setup","token","kanban","bun","visual","server"]