[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3DC9BBHK5TASE34SQYXSQ":3,"skill-same:01M6D3DC9BBHK5TASE34SQYXSQ":72},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6D3DC9BBHK5TASE34SQYXSQ","trello-setup",null,"Connect Trello to Amp for visual Kanban 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\u002Ftrello-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],"trello","setup","trello setup","MCP","sync","connect","server","api","bun","kanban","task","visual","token","2026-11-10 10:12:30",false,"---\nname: trello-setup\ndescription: Connect Trello to Amp for visual Kanban task sync\nmanifest:\n  id: trello\n  auth: api_key_token\n  category: task_sync\n  mcp_server: mcp-server-trello\n  runtime: bun\n---\n\n# Trello Setup\n\nConnect your Trello boards to Amp so your tasks, projects, and daily plans stay in sync with your Trello Kanban boards.\n\n## What This Enables\n\nOnce connected, Amp can:\n- **Task Sync:** Cards created in Amp appear on your Trello board; cards moved to Done in Trello mark tasks complete in Amp\n- **Project Health:** See live board status -- cards by list, blocked items, stale cards\n- **Daily Plan:** Surface Trello cards assigned to you, including overdue items\n- **Meeting Prep:** Know which board has blocked cards to discuss with attendees\n\n## Privacy\n\n- Card titles and status sync. No attachments or comments are read unless you ask.\n- Your API key and token stay local on your machine and are gitignored\n- Sync is on-demand (during daily plan or task creation) -- no background polling\n- Only boards you explicitly configure are accessed\n\n## When to Run\n\n- User types `\u002Ftrello-setup`\n- User asks about connecting Trello\n- User wants Kanban board context in daily plans or project health\n- During `\u002Fintegrate-mcp` if Trello 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 `trello:` section with `enabled: true`\n2. If found, skip to **Step 6** (Configure Board Mapping)\n3. If not found, continue to Step 2\n\n### Step 2: Explain What We're Setting Up\n\nSay:\n\n```\n**Let's connect Trello to Amp.**\n\nThis links your Trello boards so tasks sync between Amp and Trello.\nCards move between lists = status updates in Amp. Simple Kanban sync.\n\n**What you'll need:**\n- A Trello account with at least one board\n- Your Trello API key and token (I'll walk you through getting these)\n- About 3 minutes\n\n**Ready to go?**\n```\n\nWait for confirmation.\n\n### Step 3: Get API Credentials\n\nWalk the user through getting their Trello API key and token:\n\n```\n**Step 1: Get your API Key**\n\n1. Go to https:\u002F\u002Ftrello.com\u002Fpower-ups\u002Fadmin\n2. Click \"New\" to create a new Power-Up (or use an existing one)\n3. Copy your **API Key** from the Power-Up settings\n\n**Step 2: Generate a Token**\n\n1. On the same page, click the link to generate a **Token**\n2. Authorize the app when prompted\n3. Copy the token that appears\n\n**Paste your API key and token when ready.**\n```\n\n> **Security note:** Credentials are stored locally in `System\u002Fintegrations\u002Fconfig.yaml` (gitignored). Ensure `.mcp.json` is also in your `.gitignore`. Never paste tokens directly in terminal commands as they persist in shell history.\n\nWait for the user to provide both values.\n\n### Step 4: Add the MCP Server\n\nCheck the user's MCP configuration. If `mcp-server-trello` is not listed:\n\n1. Explain what we're adding:\n\n```\nI'll add the Trello connector to your Amp configuration.\nThis uses mcp-server-trello which runs on Bun for fast performance.\n```\n\n2. Add to the user's `.mcp.json`:\n\n```json\n{\n  \"mcp-server-trello\": {\n    \"command\": \"bunx\",\n    \"args\": [\"-y\", \"mcp-server-trello\"],\n    \"env\": {\n      \"TRELLO_API_KEY\": \"\u003Cuser's api key>\",\n      \"TRELLO_TOKEN\": \"\u003Cuser's token>\"\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\nRun a quick test to confirm everything works:\n\n1. List the user's boards via the Trello MCP\n2. Show a brief summary:\n\n```\n**Connection test:**\n- Found [N] boards: [Board Name 1], [Board Name 2], ...\n- API access confirmed\n\nEverything looks good!\n```\n\nIf it fails, troubleshoot:\n\n```\nThat didn't work. A few things to check:\n\n1. **API Key correct?** Should be a 32-character string\n2. **Token correct?** Should be a longer string (64+ characters)\n3. **Account access?** Make sure the token has read\u002Fwrite permissions\n\nWant to re-enter your credentials?\n```\n\nRetry up to 2 times, then offer to skip and come back later.\n\n### Step 6: Configure Board Mapping\n\nAsk the user which board to sync:\n\n```\n**Which Trello board should Amp sync with?**\n\nHere are your boards:\n1. [Board Name 1]\n2. [Board Name 2]\n3. [Board Name 3]\n\nPick a board (or say \"show all\" for the full list).\n\nYou can add more boards later by running `\u002Ftrello-setup` again.\n```\n\nAfter they choose a board:\n\n```\n**Now let's map your lists to Amp statuses.**\n\nI'll look at the lists on [Board Name]:\n- \"To Do\" -> Backlog (not started)\n- \"In Progress\" -> Started\n- \"Review\" -> (unmapped -- keep or map to Blocked?)\n- \"Done\" -> Done\n\nDoes this mapping look right? Or should I adjust?\n```\n\nLet the user confirm or customize the mapping. Default status list names:\n- Backlog \u002F To Do \u002F TODO -> status `n`\n- In Progress \u002F Doing \u002F Active -> status `s`\n- Blocked \u002F On Hold \u002F Waiting -> status `b`\n- Done \u002F Complete \u002F Finished -> status `d`\n\n### Step 7: Trust Level\n\nAsk about sync behavior:\n\n```\n**How should Amp handle Trello sync?**\n\n1. **Auto-sync** — Cards sync automatically during daily plan and task creation\n2. **Ask each time** — Amp shows you what changed and asks before syncing\n\nWhich do you prefer? (Most people choose auto-sync)\n```\n\n### Step 8: Save Configuration\n\nWrite to `System\u002Fintegrations\u002Fconfig.yaml` -- update the trello section:\n\n```yaml\ntrello:\n  enabled: true\n  task_sync: true\n  configured_at: YYYY-MM-DD\n  api_key: \u003Cuser's api key>\n  token: \u003Cuser's token>\n  default_board: \u003Cboard id>\n  board_name: \u003Cboard name>\n  trust_level: auto | ask\n  list_mapping:\n    backlog: \u003Clist id for Backlog>\n    in_progress: \u003Clist id for In Progress>\n    blocked: \u003Clist id for Blocked>\n    done: \u003Clist id for Done>\n  features:\n    task_sync: true\n    project_health: true\n    daily_plan: true\n    meeting_prep: true\n```\n\nIf the file already exists, only update the `trello:` section. Preserve other integration configs.\n\n### Step 9: Confirm\n\n```\n**Trello is connected!**\n\nHere's what changes now:\n\n- **Task Sync** — New Amp tasks appear on your [Board Name] board. Cards completed in Trello mark tasks done in Amp.\n- **Project Health** (`\u002Fproject-health`) shows live board status -- cards by list, blocked items\n- **Daily Plan** (`\u002Fdaily-plan`) includes your assigned Trello cards and overdue items\n- **Meeting Prep** (`\u002Fmeeting-prep`) surfaces blocked cards relevant to attendees\n\n**Capability cascade:** These skills now have Trello awareness built in.\n\nYou can adjust settings anytime by running `\u002Ftrello-setup` again.\n```\n\n---\n\n## Troubleshooting\n\n### Token Expired\n\nTrello tokens can be set to expire. If you see auth errors:\n\n1. Go to https:\u002F\u002Ftrello.com\u002Fpower-ups\u002Fadmin\n2. Generate a new token\n3. Update `System\u002Fintegrations\u002Fconfig.yaml` with the new token\n4. Restart MCP server\n\n### Board Not Found\n\nIf the configured board was deleted or renamed:\n\n1. Run `\u002Ftrello-setup` to reconfigure\n2. Select the new board\n3. Remap lists if needed\n\n### Rate Limiting\n\nTrello allows 100 requests per 10 seconds. This is generous -- you'd only hit it during bulk sync. If you see rate limit errors, wait 10 seconds and retry.\n\n### Cards Not Syncing\n\nCheck:\n- Is the board ID correct in config.yaml?\n- Does the token have write access?\n- Are the list names matching? (List mapping is case-insensitive but names must partially match)\n\n---\n\n## Reconfiguration\n\nIf the user runs `\u002Ftrello-setup` when already configured:\n\n1. Show current config from `System\u002Fintegrations\u002Fconfig.yaml`\n2. Offer options:\n   - Change synced board\n   - Update list mapping\n   - Change trust level (auto\u002Fask)\n   - Re-authenticate (new API key\u002Ftoken)\n   - Add additional boards\n   - Disconnect Trello\n\n### Disconnect Flow\n\nIf user wants to disconnect:\n\n1. Update `System\u002Fintegrations\u002Fconfig.yaml`:\n   ```yaml\n   trello:\n     enabled: false\n   ```\n2. Confirm: \"Trello is disconnected. Your daily plans and project health will no longer include Trello context. Run `\u002Ftrello-setup` anytime to reconnect.\"\n","# Trello Setup\n\nConnect your Trello boards to Amp so your tasks, projects, and daily plans stay in sync with your Trello Kanban boards.\n\n## What This Enables\n\nOnce connected, Amp can:\n- **Task Sync:** Cards created in Amp appear on your Trello board; cards moved to Done in Trello mark tasks complete in Amp\n- **Project Health:** See live board status -- cards by list, blocked items, stale cards\n- **Daily Plan:** Surface Trello cards assigned to you, including overdue items\n- **Meeting Prep:** Know which board has blocked cards to discuss with attendees\n\n## Privacy\n\n- Card titles and status sync. No attachments or comments are read unless you ask.\n- Your API key and token stay local on your machine and are gitignored\n- Sync is on-demand (during daily plan or task creation) -- no background polling\n- Only boards you explicitly configure are accessed\n\n## When to Run\n\n- User types `\u002Ftrello-setup`\n- User asks about connecting Trello\n- User wants Kanban board context in daily plans or project health\n- During `\u002Fintegrate-mcp` if Trello 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 `trello:` section with `enabled: true`\n2. If found, skip to **Step 6** (Configure Board Mapping)\n3. If not found, continue to Step 2\n\n### Step 2: Explain What We're Setting Up\n\nSay:\n\n```\n**Let's connect Trello to Amp.**\n\nThis links your Trello boards so tasks sync between Amp and Trello.\nCards move between lists = status updates in Amp. Simple Kanban sync.\n\n**What you'll need:**\n- A Trello account with at least one board\n- Your Trello API key and token (I'll walk you through getting these)\n- About 3 minutes\n\n**Ready to go?**\n```\n\nWait for confirmation.\n\n### Step 3: Get API Credentials\n\nWalk the user through getting their Trello API key and token:\n\n```\n**Step 1: Get your API Key**\n\n1. Go to https:\u002F\u002Ftrello.com\u002Fpower-ups\u002Fadmin\n2. Click \"New\" to create a new Power-Up (or use an existing one)\n3. Copy your **API Key** from the Power-Up settings\n\n**Step 2: Generate a Token**\n\n1. On the same page, click the link to generate a **Token**\n2. Authorize the app when prompted\n3. Copy the token that appears\n\n**Paste your API key and token when ready.**\n```\n\n> **Security note:** Credentials are stored locally in `System\u002Fintegrations\u002Fconfig.yaml` (gitignored). Ensure `.mcp.json` is also in your `.gitignore`. Never paste tokens directly in terminal commands as they persist in shell history.\n\nWait for the user to provide both values.\n\n### Step 4: Add the MCP Server\n\nCheck the user's MCP configuration. If `mcp-server-trello` is not listed:\n\n1. Explain what we're adding:\n\n```\nI'll add the Trello connector to your Amp configuration.\nThis uses mcp-server-trello which runs on Bun for fast performance.\n```\n\n2. Add to the user's `.mcp.json`:\n\n```json\n{\n  \"mcp-server-trello\": {\n    \"command\": \"bunx\",\n    \"args\": [\"-y\", \"mcp-server-trello\"],\n    \"env\": {\n      \"TRELLO_API_KEY\": \"\u003Cuser's api key>\",\n      \"TRELLO_TOKEN\": \"\u003Cuser's token>\"\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\nRun a quick test to confirm everything works:\n\n1. List the user's boards via the Trello MCP\n2. Show a brief summary:\n\n```\n**Connection test:**\n- Found [N] boards: [Board Name 1], [Board Name 2], ...\n- API access confirmed\n\nEverything looks good!\n```\n\nIf it fails, troubleshoot:\n\n```\nThat didn't work. A few things to check:\n\n1. **API Key correct?** Should be a 32-character string\n2. **Token correct?** Should be a longer string (64+ characters)\n3. **Account access?** Make sure the token has read\u002Fwrite permissions\n\nWant to re-enter your credentials?\n```\n\nRetry up to 2 times, then offer to skip and come back later.\n\n### Step 6: Configure Board Mapping\n\nAsk the user which board to sync:\n\n```\n**Which Trello board should Amp sync with?**\n\nHere are your boards:\n1. [Board Name 1]\n2. [Board Name 2]\n3. [Board Name 3]\n\nPick a board (or say \"show all\" for the full list).\n\nYou can add more boards later by running `\u002Ftrello-setup` again.\n```\n\nAfter they choose a board:\n\n```\n**Now let's map your lists to Amp statuses.**\n\nI'll look at the lists on [Board Name]:\n- \"To Do\" -> Backlog (not started)\n- \"In Progress\" -> Started\n- \"Review\" -> (unmapped -- keep or map to Blocked?)\n- \"Done\" -> Done\n\nDoes this mapping look right? Or should I adjust?\n```\n\nLet the user confirm or customize the mapping. Default status list names:\n- Backlog \u002F To Do \u002F TODO -> status `n`\n- In Progress \u002F Doing \u002F Active -> status `s`\n- Blocked \u002F On Hold \u002F Waiting -> status `b`\n- Done \u002F Complete \u002F Finished -> status `d`\n\n### Step 7: Trust Level\n\nAsk about sync behavior:\n\n```\n**How should Amp handle Trello sync?**\n\n1. **Auto-sync** — Cards sync automatically during daily plan and task creation\n2. **Ask each time** — Amp shows you what changed and asks before syncing\n\nWhich do you prefer? (Most people choose auto-sync)\n```\n\n### Step 8: Save Configuration\n\nWrite to `System\u002Fintegrations\u002Fconfig.yaml` -- update the trello section:\n\n```yaml\ntrello:\n  enabled: true\n  task_sync: true\n  configured_at: YYYY-MM-DD\n  api_key: \u003Cuser's api key>\n  token: \u003Cuser's token>\n  default_board: \u003Cboard id>\n  board_name: \u003Cboard name>\n  trust_level: auto | ask\n  list_mapping:\n    backlog: \u003Clist id for Backlog>\n    in_progress: \u003Clist id for In Progress>\n    blocked: \u003Clist id for Blocked>\n    done: \u003Clist id for Done>\n  features:\n    task_sync: true\n    project_health: true\n    daily_plan: true\n    meeting_prep: true\n```\n\nIf the file already exists, only update the `trello:` section. Preserve other integration configs.\n\n### Step 9: Confirm\n\n```\n**Trello is connected!**\n\nHere's what changes now:\n\n- **Task Sync** — New Amp tasks appear on your [Board Name] board. Cards completed in Trello mark tasks done in Amp.\n- **Project Health** (`\u002Fproject-health`) shows live board status -- cards by list, blocked items\n- **Daily Plan** (`\u002Fdaily-plan`) includes your assigned Trello cards and overdue items\n- **Meeting Prep** (`\u002Fmeeting-prep`) surfaces blocked cards relevant to attendees\n\n**Capability cascade:** These skills now have Trello awareness built in.\n\nYou can adjust settings anytime by running `\u002Ftrello-setup` again.\n```\n\n---\n\n## Troubleshooting\n\n### Token Expired\n\nTrello tokens can be set to expire. If you see auth errors:\n\n1. Go to https:\u002F\u002Ftrello.com\u002Fpower-ups\u002Fadmin\n2. Generate a new token\n3. Update `System\u002Fintegrations\u002Fconfig.yaml` with the new token\n4. Restart MCP server\n\n### Board Not Found\n\nIf the configured board was deleted or renamed:\n\n1. Run `\u002Ftrello-setup` to reconfigure\n2. Select the new board\n3. Remap lists if needed\n\n### Rate Limiting\n\nTrello allows 100 requests per 10 seconds. This is generous -- you'd only hit it during bulk sync. If you see rate limit errors, wait 10 seconds and retry.\n\n### Cards Not Syncing\n\nCheck:\n- Is the board ID correct in config.yaml?\n- Does the token have write access?\n- Are the list names matching? (List mapping is case-insensitive but names must partially match)\n\n---\n\n## Reconfiguration\n\nIf the user runs `\u002Ftrello-setup` when already configured:\n\n1. Show current config from `System\u002Fintegrations\u002Fconfig.yaml`\n2. Offer options:\n   - Change synced board\n   - Update list mapping\n   - Change trust level (auto\u002Fask)\n   - Re-authenticate (new API key\u002Ftoken)\n   - Add additional boards\n   - Disconnect Trello\n\n### Disconnect Flow\n\nIf user wants to disconnect:\n\n1. Update `System\u002Fintegrations\u002Fconfig.yaml`:\n   ```yaml\n   trello:\n     enabled: false\n   ```\n2. Confirm: \"Trello is disconnected. Your daily plans and project health will no longer include Trello context. Run `\u002Ftrello-setup` anytime to reconnect.\"\n",{"name":5,"manifest":45,"description":7},{"id":27,"auth":46,"runtime":35,"category":47,"mcp_server":48},"api_key_token","task_sync","mcp-server-trello","main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Ftrello-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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill trello-setup",{"tool":64,"command":65},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill trello-setup",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill trello-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftrello-setup\u002FSKILL.md",true,[],[73,103,112,126,140,152],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":85,"publishedAt":40},"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",[79,80],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[86,28,30,87,32,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"zoom setup","review","transcript","search","stats","oauth2","schedule","confirmation","context","meetings","process","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":40},"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",[],[105,110,111],"learn","just",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":40},"01M6D3DN7BZQDY6143A2QSDP9A","week-review","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",[118],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[120,87,121,122,123,124,125],"week review","pattern","goal","tracking","detection","pattern detection",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":40},"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",[],[133,134,135,136,137,138,139,37],"plan","week plan","priorities","SET","shape","calendar","goals",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":40},"01M6D3DF90D7RC8ZJE4AW2P9VC","triage","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",[],[142,147,148,149,150,151],"tasks","fast","extract","files","route",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":160,"publishedAt":40},"01M6D3D8S2YSHSB0BN73W9HA0W","todoist-setup","Connect Todoist to Amp for two-way task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftodoist-setup\u002FSKILL.md",[158,159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,28,163,87,142,31,147,32,164,90,34,133,165,96,166,37,167,168,30],"todoist setup","todoist","creation","inbox","system","daily","systems","daily plan"]