[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D34GSAKN9GJMYD7SYPXSWW":3,"skill-same:01M6D34GSAKN9GJMYD7SYPXSWW":50},{"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":18,"publishedAt":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M6D34GSAKN9GJMYD7SYPXSWW","amp-rollback",null,"Undo the last Amp update if something went wrong","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\u002Famp-rollback\u002FSKILL.md",[],[19,20,21],"rollback","amp rollback","update","2026-11-10 10:12:30",false,"---\nname: amp-rollback\ndescription: Undo the last Amp update if something went wrong\n---\n\n## What This Command Does\n\n**Restores Amp to the version before your last update.** Use this if something broke after updating.\n\n**When to use:**\n- Feature you relied on stopped working\n- Data looks wrong after update\n- System feels unstable\n- Want to go back for any reason\n\n**Safe to use:** Your notes, tasks, and projects are never at risk.\n\n---\n\n## Process\n\n### Step 1: Check if Rollback is Possible\n\n**A. Verify Git repository**\n\nRun: `git --version`\n\nIf Git not found:\n```\n❌ Git not detected\n\nRollback requires Git. Your data is safe, but automated rollback isn't available.\n\n**To manually restore:**\n1. If you have a backup folder, copy your data back\n2. Or re-download Amp and copy your folders (00-07, System\u002F)\n\n[Show manual restore guide]\n```\n\n**B. Check for backup tag**\n\nRun: `git tag | grep backup-before`\n\nIf no backup found:\n```\n❌ No backup found\n\nLooks like you haven't updated recently, or the backup wasn't created.\n\nYour current version: v1.3.0\n\nOptions:\n[Download previous version manually]\n[Cancel]\n```\n\n**C. Identify what version to restore to**\n\nRun: `git tag | grep backup-before | tail -1`\n\nExample: `backup-before-v1.3.0` means restore to before v1.3.0 update.\n\n---\n\n### Step 2: Confirm Rollback\n\n```\n? Rollback Amp Update\n\nYou're about to restore Amp to the version before your last update.\n\nCurrent version: v1.3.0\nWill restore to: v1.2.0 (last backup)\n\n**What happens:**\n✓ Amp features restored to v1.2.0\n✓ Your notes, tasks, projects stay as they are\n✓ Any new skills from v1.3.0 will be removed\n\n**This is safe:**\n• Your data folders (00-07) are not affected\n• Your configuration (user-profile, pillars) stays\n• You can update again later if you want\n\n[Confirm rollback]\n[Cancel]\n```\n\n---\n\n### Step 3: Save Current State\n\nBefore rolling back, save any uncommitted changes:\n\n```\n? Saving current state...\n```\n\nRun:\n```bash\ngit add .\ngit commit -m \"Auto-save before rollback to v1.2.0\" || true\n```\n\nCreate a \"before rollback\" tag in case they want to undo the rollback:\n\n```bash\ngit tag before-rollback-$(date +%Y%m%d-%H%M%S)\n```\n\n```\n✓ Current state saved\n```\n\n---\n\n### Step 4: Perform Rollback\n\n```\n? Rolling back to v1.2.0...\n```\n\nRun:\n```bash\ngit reset --hard backup-before-v1.3.0\n```\n\nThis restores all Amp files to the state before update.\n\n**Note:** User data folders (00-07) remain untouched because:\n1. They're gitignored (not tracked)\n2. `git reset` only affects tracked files\n\n---\n\n### Step 5: Cleanup\n\n**A. Remove dependencies from newer version**\n\n```\n? Cleaning up...\n```\n\nRun:\n```bash\nnpm install\npip3 install -r requirements.txt\n```\n\nThis ensures dependencies match the older version.\n\n**B. Remove migration markers (if exist)**\n\n```bash\nrm -f .migration-v*-complete\nrm -f .migration-version\n```\n\n---\n\n### Step 6: Verification\n\n```\n✓ Rollback complete! Now testing...\n```\n\n**Quick checks:**\n\n1. Verify version in package.json:\n   ```bash\n   cat package.json | grep version\n   ```\n\n2. Check key files:\n   - `03-Tasks\u002FTasks.md`\n   - `System\u002Fuser-profile.yaml`\n   - `.claude\u002Fskills\u002Fdaily-plan\u002FSKILL.md`\n\n3. Test user profile loads:\n   ```\n   Read System\u002Fuser-profile.yaml\n   ```\n\n**If all pass:**\n```\n✅ Rollback successful!\n```\n\n**If issues:**\n```\n⚠️ Rollback completed but found an issue\n\n[Details]\n\nYour data is safe. You may want to:\n[Report this issue]\n[Try rolling back again]\n[Continue anyway]\n```\n\n---\n\n### Step 7: Summary\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n✅ Rolled Back: v1.3.0 → v1.2.0\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nAmp restored to: v1.2.0\nYour data: All preserved (notes, tasks, projects)\n\nYou're back to the version from before your last update.\n\n**What now?**\n• Everything should work as before\n• You can try updating again later with \u002Famp-update\n• If issues persist, try \u002Fsetup to verify configuration\n\n**Want to report what went wrong?**\n[Open issue on GitHub] — Help improve future updates\n```\n\n---\n\n## Undo Rollback (Advanced)\n\nIf user rolled back by mistake and wants to go forward again:\n\n```\nDid you roll back by mistake?\n\nWe saved your state before rollback. You can restore it:\n\n[Restore to v1.3.0] — Undo this rollback\n[Stay on v1.2.0] — Keep rollback\n```\n\nIf user chooses restore:\n\n```bash\nRESTORE_TAG=$(git tag | grep before-rollback | tail -1)\ngit reset --hard $RESTORE_TAG\n```\n\n---\n\n## Manual Rollback (No Git)\n\nIf Git not available or no backup tags:\n\n```\n? Manual Rollback Method\n\nTo restore an older version without Git:\n\n1. **Download your desired version:**\n   \n   For v1.2.0:\n   https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Freleases\u002Ftag\u002Fv1.2.0\n   \n   Click \"Source code (zip)\"\n\n2. **Copy your data:**\n   \n   From CURRENT Amp, copy to DOWNLOADED Amp:\n   \n   ✓ System\u002Fuser-profile.yaml\n   ✓ System\u002Fpillars.yaml\n   ✓ 00-Inbox\u002F\n   ✓ 01-Quarter_Goals\u002F\n   ✓ 02-Week_Priorities\u002F\n   ✓ 03-Tasks\u002F\n   ✓ 04-Projects\u002F\n   ✓ 05-Areas\u002F\n   ✓ 07-Archives\u002F\n   ✓ .env (if exists)\n\n3. **Replace folders:**\n   \n   • Move current Amp folder to trash (or rename to amp-old)\n   • Rename downloaded folder to 'amp'\n   • Open in Cursor\n\n4. **Verify:**\n   \n   Run \u002Fsetup to check everything works\n\n[See version history] — All Amp releases\n[Copy instructions]\n```\n\n---\n\n## Rollback Limitations\n\n**What rollback restores:**\n- ✓ Amp skills\n- ✓ MCP servers\n- ✓ Core features\n- ✓ Documentation\n\n**What rollback preserves (doesn't touch):**\n- ✓ Your notes (00-Inbox, 04-Projects, 05-Areas)\n- ✓ Your tasks (03-Tasks\u002F)\n- ✓ Your configuration (user-profile, pillars)\n- ✓ Your API keys (.env)\n\n**What you might lose:**\n- ⚠️ New features added since v1.2.0\n- ⚠️ Bug fixes introduced in v1.3.0\n- ⚠️ New skills that came with update\n\n---\n\n## Troubleshooting\n\n### \"Rollback completed but \u002Fdaily-plan doesn't work\"\n\nLikely MCP servers need restart:\n\n1. Close Cursor completely\n2. Reopen your Amp folder\n3. Try \u002Fdaily-plan again\n\n### \"My tasks look different after rollback\"\n\nYour task data is unchanged. What might look different:\n- Task display format (if update changed rendering)\n- Task sorting (if update changed logic)\n\n**Your actual tasks are safe.** Check `03-Tasks\u002FTasks.md` directly - everything is there.\n\n### \"Can I rollback multiple versions?\"\n\nYes, if backups exist:\n\n```bash\ngit tag | grep backup-before\n```\n\nShows all available backups:\n```\nbackup-before-v1.1.0\nbackup-before-v1.2.0\nbackup-before-v1.3.0\n```\n\nTo rollback to specific version:\n```bash\ngit reset --hard backup-before-v1.1.0\n```\n\nBut easier: tell `\u002Famp-rollback` which version you want, and it handles it.\n\n---\n\n## Prevention Better Than Cure\n\n**To avoid needing rollback:**\n\n1. **Read release notes before updating**\n   - Run `\u002Famp-whats-new` first\n   - Check for breaking changes warning\n   - Understand what's changing\n\n2. **Update during low-stakes time**\n   - Not right before important meeting\n   - Not during crunch deadline\n   - Give yourself time to test\n\n3. **Test after updating**\n   - Run `\u002Fdaily-plan`\n   - Open a person page\n   - Check key workflows\n\n4. **Keep regular backups**\n   - Use Time Machine (Mac) or File History (Windows)\n   - Or manually copy Amp folder weekly\n\n---\n\n## Related Commands\n\n- `\u002Famp-update` - Update to latest version\n- `\u002Famp-whats-new` - Check what's available\n- `\u002Fsetup` - Verify Amp configuration\n\n---\n\n## Philosophy\n\n**Rollback should be:**\n- One command away\n- Always available\n- Completely safe\n- No data loss ever\n\n**User confidence:**\n\"I can try updates knowing I can undo them instantly\"\n\n**No shame in rolling back:**\nUpdates should improve things. If they don't for you, rolling back is the right choice. Help us by reporting what went wrong.\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark Amp rollback as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `amp_rollback_completed` and properties:\n- `restored_version`\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n","## What This Command Does\n\n**Restores Amp to the version before your last update.** Use this if something broke after updating.\n\n**When to use:**\n- Feature you relied on stopped working\n- Data looks wrong after update\n- System feels unstable\n- Want to go back for any reason\n\n**Safe to use:** Your notes, tasks, and projects are never at risk.\n\n---\n\n## Process\n\n### Step 1: Check if Rollback is Possible\n\n**A. Verify Git repository**\n\nRun: `git --version`\n\nIf Git not found:\n```\n❌ Git not detected\n\nRollback requires Git. Your data is safe, but automated rollback isn't available.\n\n**To manually restore:**\n1. If you have a backup folder, copy your data back\n2. Or re-download Amp and copy your folders (00-07, System\u002F)\n\n[Show manual restore guide]\n```\n\n**B. Check for backup tag**\n\nRun: `git tag | grep backup-before`\n\nIf no backup found:\n```\n❌ No backup found\n\nLooks like you haven't updated recently, or the backup wasn't created.\n\nYour current version: v1.3.0\n\nOptions:\n[Download previous version manually]\n[Cancel]\n```\n\n**C. Identify what version to restore to**\n\nRun: `git tag | grep backup-before | tail -1`\n\nExample: `backup-before-v1.3.0` means restore to before v1.3.0 update.\n\n---\n\n### Step 2: Confirm Rollback\n\n```\n? Rollback Amp Update\n\nYou're about to restore Amp to the version before your last update.\n\nCurrent version: v1.3.0\nWill restore to: v1.2.0 (last backup)\n\n**What happens:**\n✓ Amp features restored to v1.2.0\n✓ Your notes, tasks, projects stay as they are\n✓ Any new skills from v1.3.0 will be removed\n\n**This is safe:**\n• Your data folders (00-07) are not affected\n• Your configuration (user-profile, pillars) stays\n• You can update again later if you want\n\n[Confirm rollback]\n[Cancel]\n```\n\n---\n\n### Step 3: Save Current State\n\nBefore rolling back, save any uncommitted changes:\n\n```\n? Saving current state...\n```\n\nRun:\n```bash\ngit add .\ngit commit -m \"Auto-save before rollback to v1.2.0\" || true\n```\n\nCreate a \"before rollback\" tag in case they want to undo the rollback:\n\n```bash\ngit tag before-rollback-$(date +%Y%m%d-%H%M%S)\n```\n\n```\n✓ Current state saved\n```\n\n---\n\n### Step 4: Perform Rollback\n\n```\n? Rolling back to v1.2.0...\n```\n\nRun:\n```bash\ngit reset --hard backup-before-v1.3.0\n```\n\nThis restores all Amp files to the state before update.\n\n**Note:** User data folders (00-07) remain untouched because:\n1. They're gitignored (not tracked)\n2. `git reset` only affects tracked files\n\n---\n\n### Step 5: Cleanup\n\n**A. Remove dependencies from newer version**\n\n```\n? Cleaning up...\n```\n\nRun:\n```bash\nnpm install\npip3 install -r requirements.txt\n```\n\nThis ensures dependencies match the older version.\n\n**B. Remove migration markers (if exist)**\n\n```bash\nrm -f .migration-v*-complete\nrm -f .migration-version\n```\n\n---\n\n### Step 6: Verification\n\n```\n✓ Rollback complete! Now testing...\n```\n\n**Quick checks:**\n\n1. Verify version in package.json:\n   ```bash\n   cat package.json | grep version\n   ```\n\n2. Check key files:\n   - `03-Tasks\u002FTasks.md`\n   - `System\u002Fuser-profile.yaml`\n   - `.claude\u002Fskills\u002Fdaily-plan\u002FSKILL.md`\n\n3. Test user profile loads:\n   ```\n   Read System\u002Fuser-profile.yaml\n   ```\n\n**If all pass:**\n```\n✅ Rollback successful!\n```\n\n**If issues:**\n```\n⚠️ Rollback completed but found an issue\n\n[Details]\n\nYour data is safe. You may want to:\n[Report this issue]\n[Try rolling back again]\n[Continue anyway]\n```\n\n---\n\n### Step 7: Summary\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n✅ Rolled Back: v1.3.0 → v1.2.0\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nAmp restored to: v1.2.0\nYour data: All preserved (notes, tasks, projects)\n\nYou're back to the version from before your last update.\n\n**What now?**\n• Everything should work as before\n• You can try updating again later with \u002Famp-update\n• If issues persist, try \u002Fsetup to verify configuration\n\n**Want to report what went wrong?**\n[Open issue on GitHub] — Help improve future updates\n```\n\n---\n\n## Undo Rollback (Advanced)\n\nIf user rolled back by mistake and wants to go forward again:\n\n```\nDid you roll back by mistake?\n\nWe saved your state before rollback. You can restore it:\n\n[Restore to v1.3.0] — Undo this rollback\n[Stay on v1.2.0] — Keep rollback\n```\n\nIf user chooses restore:\n\n```bash\nRESTORE_TAG=$(git tag | grep before-rollback | tail -1)\ngit reset --hard $RESTORE_TAG\n```\n\n---\n\n## Manual Rollback (No Git)\n\nIf Git not available or no backup tags:\n\n```\n? Manual Rollback Method\n\nTo restore an older version without Git:\n\n1. **Download your desired version:**\n   \n   For v1.2.0:\n   https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Freleases\u002Ftag\u002Fv1.2.0\n   \n   Click \"Source code (zip)\"\n\n2. **Copy your data:**\n   \n   From CURRENT Amp, copy to DOWNLOADED Amp:\n   \n   ✓ System\u002Fuser-profile.yaml\n   ✓ System\u002Fpillars.yaml\n   ✓ 00-Inbox\u002F\n   ✓ 01-Quarter_Goals\u002F\n   ✓ 02-Week_Priorities\u002F\n   ✓ 03-Tasks\u002F\n   ✓ 04-Projects\u002F\n   ✓ 05-Areas\u002F\n   ✓ 07-Archives\u002F\n   ✓ .env (if exists)\n\n3. **Replace folders:**\n   \n   • Move current Amp folder to trash (or rename to amp-old)\n   • Rename downloaded folder to 'amp'\n   • Open in Cursor\n\n4. **Verify:**\n   \n   Run \u002Fsetup to check everything works\n\n[See version history] — All Amp releases\n[Copy instructions]\n```\n\n---\n\n## Rollback Limitations\n\n**What rollback restores:**\n- ✓ Amp skills\n- ✓ MCP servers\n- ✓ Core features\n- ✓ Documentation\n\n**What rollback preserves (doesn't touch):**\n- ✓ Your notes (00-Inbox, 04-Projects, 05-Areas)\n- ✓ Your tasks (03-Tasks\u002F)\n- ✓ Your configuration (user-profile, pillars)\n- ✓ Your API keys (.env)\n\n**What you might lose:**\n- ⚠️ New features added since v1.2.0\n- ⚠️ Bug fixes introduced in v1.3.0\n- ⚠️ New skills that came with update\n\n---\n\n## Troubleshooting\n\n### \"Rollback completed but \u002Fdaily-plan doesn't work\"\n\nLikely MCP servers need restart:\n\n1. Close Cursor completely\n2. Reopen your Amp folder\n3. Try \u002Fdaily-plan again\n\n### \"My tasks look different after rollback\"\n\nYour task data is unchanged. What might look different:\n- Task display format (if update changed rendering)\n- Task sorting (if update changed logic)\n\n**Your actual tasks are safe.** Check `03-Tasks\u002FTasks.md` directly - everything is there.\n\n### \"Can I rollback multiple versions?\"\n\nYes, if backups exist:\n\n```bash\ngit tag | grep backup-before\n```\n\nShows all available backups:\n```\nbackup-before-v1.1.0\nbackup-before-v1.2.0\nbackup-before-v1.3.0\n```\n\nTo rollback to specific version:\n```bash\ngit reset --hard backup-before-v1.1.0\n```\n\nBut easier: tell `\u002Famp-rollback` which version you want, and it handles it.\n\n---\n\n## Prevention Better Than Cure\n\n**To avoid needing rollback:**\n\n1. **Read release notes before updating**\n   - Run `\u002Famp-whats-new` first\n   - Check for breaking changes warning\n   - Understand what's changing\n\n2. **Update during low-stakes time**\n   - Not right before important meeting\n   - Not during crunch deadline\n   - Give yourself time to test\n\n3. **Test after updating**\n   - Run `\u002Fdaily-plan`\n   - Open a person page\n   - Check key workflows\n\n4. **Keep regular backups**\n   - Use Time Machine (Mac) or File History (Windows)\n   - Or manually copy Amp folder weekly\n\n---\n\n## Related Commands\n\n- `\u002Famp-update` - Update to latest version\n- `\u002Famp-whats-new` - Check what's available\n- `\u002Fsetup` - Verify Amp configuration\n\n---\n\n## Philosophy\n\n**Rollback should be:**\n- One command away\n- Always available\n- Completely safe\n- No data loss ever\n\n**User confidence:**\n\"I can try updates knowing I can undo them instantly\"\n\n**No shame in rolling back:**\nUpdates should improve things. If they don't for you, rolling back is the right choice. Help us by reporting what went wrong.\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark Amp rollback as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `amp_rollback_completed` and properties:\n- `restored_version`\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n",{"name":5,"description":7},"main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Famp-rollback",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill amp-rollback",{"tool":42,"command":43},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill amp-rollback",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill amp-rollback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Famp-rollback\u002FSKILL.md",true,[],[51,88,97,111,126,138],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":67,"publishedAt":22},"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",[57,62],{"categoryNo":58,"categoryName":59,"taxonomyType":60,"taxonomyTypeDesc":61},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87],"zoom setup","setup","schedule","MCP","review","connect","transcript","search","stats","oauth2","confirmation","context","meetings","process","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":22},"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",[],[90,95,96],"learn","just",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":22},"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",[103],{"categoryNo":58,"categoryName":59,"taxonomyType":60,"taxonomyTypeDesc":61},[105,72,106,107,108,109,110],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":22},"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",[],[118,119,120,121,122,123,124,125],"week plan","plan","calendar","SET","shape","goals","task","priorities",{"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":22},"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",[],[128,133,134,135,136,137],"tasks","fast","extract","files","route",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":148,"publishedAt":22},"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",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":60,"taxonomyTypeDesc":61},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":58,"categoryName":59,"taxonomyType":60,"taxonomyTypeDesc":61},[149,150,69,151,73,71,152,124,153,154,155,156,157],"trello","trello setup","sync","token","kanban","bun","visual","api","server"]