[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76VYMFN1R0CTWJMCGD6WGPJ":3,"skill-same:01M76VYMFN1R0CTWJMCGD6WGPJ":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M76VYMFN1R0CTWJMCGD6WGPJ","amp-show-changes",null,"Preview what will change between your installed Amp and latest production without applying updates","hemory\u002Famp","hemory","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21179881?v=4","01M6D31HFJ391DN8N0JP8AQGFE","Hemory Phifer","01M758Z6KK3NGD8654Y5CT668C",0,"MIT","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Famp-show-changes\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: amp-show-changes\ndescription: Preview what will change between your installed Amp and latest production without applying updates\n---\n\n## Purpose\n\nShow a read-only preview of the changes available before running `\u002Famp-update`. This command helps users understand what is new, what may be removed or renamed, what customizations will be protected, and whether any breaking-change warning is available.\n\n**When to use:**\n- Before `\u002Famp-update` when you want a plain-English preview.\n- When `\u002Famp-whats-new` says an update is available and you want file-level detail.\n- When you have custom skills, MCP entries, or protected user instructions and want to confirm they are visible before updating.\n\n**Read-only guarantee:** This workflow does not merge, reset, checkout, stash, commit, or apply updates. It only reads local files and, when Git is available, runs `git fetch` so the remote comparison point is current.\n\n---\n\n## Inputs\n\n`$ARGUMENTS` is optional.\n\nSupported modes:\n- No argument: compare current `HEAD` with the latest production `main`.\n- `--no-fetch`: skip network fetch and compare against the currently cached remote-tracking branch.\n- `--full`: include raw commit subjects and a longer changed-file summary.\n\n---\n\n## Step 1: Detect Git and Remote\n\nCheck whether the current Amp install is a Git repository:\n\n```bash\ngit rev-parse --is-inside-work-tree\n```\n\nIf Git is unavailable or the command fails, continue with a limited local-only preview:\n\n```text\n⚠️ Git preview unavailable\n\nI could not compare your install with production because this folder is not a Git checkout or Git is not installed.\n\nWhat I can still show:\n- Protected customizations I can detect locally\n- Manual update guidance\n\nTo enable full previews, install Amp from the Git repository instead of a ZIP download.\n```\n\nWhen Git is available, detect the production remote. Prefer `upstream`, fall back to `origin`:\n\n```bash\nif git remote | grep -qx 'upstream'; then\n  AMP_REMOTE='upstream'\nelif git remote | grep -qx 'origin'; then\n  AMP_REMOTE='origin'\nelse\n  AMP_REMOTE=''\nfi\n```\n\nIf no remote exists, explain that remote comparison is unavailable and continue with the protected customizations inventory.\n\n---\n\n## Step 2: Refresh Production Main Without Applying Updates\n\nUnless `--no-fetch` is present, fetch the production branch only:\n\n```bash\ngit fetch \"$AMP_REMOTE\" main:refs\u002Fremotes\u002F$AMP_REMOTE\u002Fmain --prune\n```\n\nSet the comparison target:\n\n```bash\nAMP_TARGET=\"$AMP_REMOTE\u002Fmain\"\n```\n\nValidate the target exists:\n\n```bash\ngit rev-parse --verify \"$AMP_TARGET\"\n```\n\nIf fetch fails, use the cached remote-tracking branch if available. If no target is available, report the failure and continue with local inventory only.\n\n---\n\n## Step 3: Look for an Update Manifest, Then Fall Back to Git Diff\n\nA production update manifest may be available. If one exists locally or in the fetched target, use it to enrich the preview. Check likely manifest paths without assuming one is present:\n\n```bash\nfor path in \\\n  System\u002Fupdate-manifest.json \\\n  System\u002Fupdate-manifest.yaml \\\n  System\u002Fupdate-manifest.yml \\\n  .amp\u002Fupdate-manifest.json \\\n  amp-update-manifest.json \\\n  release-manifest.json; do\n  if [ -f \"$path\" ]; then\n    echo \"local:$path\"\n    break\n  fi\n  if git cat-file -e \"$AMP_TARGET:$path\" 2>\u002Fdev\u002Fnull; then\n    echo \"remote:$path\"\n    break\n  fi\ndone\n```\n\nIf a local manifest is found, read it from the working tree. If a remote manifest is found, read it from the target tree with `git show \"$AMP_TARGET:$path\"`. Use any available fields for:\n- Version or release name\n- Summary\n- Added features\n- Removed features\n- Renamed features\n- Breaking changes\n- Migrations\n- Protected paths or customization rules\n\nIf no manifest is found, say so plainly and generate the preview from Git diff data:\n\n```text\nNo update manifest found on production main yet, so this preview is based on Git commits and changed files.\n```\n\n---\n\n## Step 4: Compare Commits and Files\n\nCollect the commit range and changed files:\n\n```bash\ngit log --oneline --decorate --no-merges HEAD..\"$AMP_TARGET\"\ngit diff --name-status HEAD..\"$AMP_TARGET\"\ngit diff --stat HEAD..\"$AMP_TARGET\"\n```\n\nIf there are no commits in `HEAD..$AMP_TARGET`, report:\n\n```text\n✅ You're already aligned with production main.\n\nNo update is waiting. I still checked protected customizations below.\n```\n\nFor normal output, summarize:\n- Number of commits ahead on production.\n- Top commit subjects, grouped when possible by prefix or area.\n- Changed file counts by area: skills, MCP\u002Fcore, scripts, docs, templates, tests.\n- File status counts: added, modified, deleted, renamed.\n\n---\n\n## Step 5: Identify Added, Removed, and Renamed Features\n\nUse manifest data first when available. Otherwise infer cautiously from file paths.\n\nFeature path patterns:\n- Skills: `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`\n- MCP servers: `core\u002Fmcp\u002F*_server.py`\n- User docs: `docs\u002F*.md`, `README.md`, `CLAUDE.md.template`, `AGENTS.md`\n- Templates: `System\u002FTemplates\u002F*`, `06-Resources\u002FTemplates\u002F*`\n- Scripts: `scripts\u002F*`, `.scripts\u002F*`\n\nFrom `git diff --name-status`:\n- `A .claude\u002Fskills\u002Ffoo\u002FSKILL.md` means added skill `\u002Ffoo`.\n- `D .claude\u002Fskills\u002Ffoo\u002FSKILL.md` means removed skill `\u002Ffoo`.\n- `R... old new` under `.claude\u002Fskills\u002F` means renamed skill.\n- Apply the same pattern to MCP servers, docs, and templates when names clearly map to user-visible features.\n\nDo not overstate inferred changes. Use labels:\n- **From manifest** when the manifest says it directly.\n- **Inferred from file paths** when derived from Git diff.\n- **Needs review** when the file changed but the user impact is not obvious.\n\n---\n\n## Step 6: Breaking-Change Warnings\n\nUse manifest breaking-change fields first. If the manifest contains `breaking_changes`, `breakingChanges`, `warnings`, `migrations`, or `requires_action`, surface them exactly and prominently.\n\nIf there is no manifest, scan commit subjects and changed file paths for likely warning terms:\n\n```bash\ngit log --format='%s' HEAD..\"$AMP_TARGET\" | grep -Ei 'breaking|migration|required|remove|rename|deprecat|manual' || true\ngit diff --name-status HEAD..\"$AMP_TARGET\" | grep -Ei 'migration|template|CLAUDE|AGENTS|requirements|package-lock|install|setup' || true\n```\n\nOutput one of:\n\n```text\n⚠️ Breaking-change warnings\n- [Manifest-provided warning or cautious inferred warning]\n```\n\nor:\n\n```text\n✓ No breaking-change warning found in the manifest or commit\u002Ffile scan.\n```\n\nWhen warnings are inferred, say they are inferred and recommend reading the related commits before updating.\n\n---\n\n## Step 7: Protected Customizations Inventory\n\nInventory local customizations that `\u002Famp-update` should preserve. Do not print private content. Report counts and names only when names are safe and useful.\n\nCheck:\n\n```bash\n# Protected user instruction block\nif [ -f CLAUDE.md ] && grep -q 'USER_EXTENSIONS_START' CLAUDE.md && grep -q 'USER_EXTENSIONS_END' CLAUDE.md; then\n  echo 'user_extensions_block=present'\nelse\n  echo 'user_extensions_block=not_found'\nfi\n\n# Custom skills\nfind .claude\u002Fskills -maxdepth 1 -type d -name '*-custom' -print 2>\u002Fdev\u002Fnull | sed 's#^.claude\u002Fskills\u002F##'\n\n# Custom MCP servers by name only\npython3 - \u003C\u003C'PY'\nimport json\nfrom pathlib import Path\npath = Path('.mcp.json')\nif not path.exists():\n    print('custom_mcp=[]')\nelse:\n    data = json.loads(path.read_text())\n    names = sorted(k for k in data.get('mcpServers', {}) if k.startswith('custom-'))\n    print('custom_mcp=' + repr(names))\nPY\n\n# Locally modified tracked files\ngit status --short\n```\n\nReport:\n\n```text\n🛡️ Protected customizations inventory\n\n- User extension block: present\u002Fnot found\n- Custom skills: N found\n- Custom MCP servers: N found\n- Local uncommitted changes: N files\n\nI did not print private instruction text, MCP command values, environment values, notes, tasks, projects, people pages, or meeting notes.\n```\n\nIf custom items are missing, avoid implying data loss. Say only that none were detected.\n\n---\n\n## Step 8: Produce the Preview\n\nUse this structure:\n\n```text\n# Amp update preview\n\nCompared: current HEAD → \u003Cremote>\u002Fmain\nRemote: \u003Cremote>\nMode: manifest-enriched | git-diff only | local inventory only\n\n## Summary\n- \u003CN> commits available\n- \u003CN> files changed: \u003CA> added, \u003CM> modified, \u003CD> deleted, \u003CR> renamed\n- Biggest areas: skills, docs, core, templates, tests\n\n## Added features\n- \u002Fskill-name, from manifest or inferred from file path\n\n## Removed features\n- None found, or list items\n\n## Renamed features\n- None found, or old → new\n\n## Breaking-change warnings\n- None found, or list warnings\n\n## Protected customizations inventory\n- User extension block: present\u002Fnot found\n- Custom skills: count\n- Custom MCP servers: count\n- Local modified tracked files: count\n\n## What this means for you\nPlain-English explanation of likely impact:\n- What new capability they get\n- Whether any behavior may change\n- Whether anything needs review before `\u002Famp-update`\n- Whether it looks safe to proceed\n\n## Next step\n- If comfortable: run `\u002Famp-update`\n- If cautious: run `\u002Famp-update-preflight`\n- If warnings appeared: read the listed commits or release notes first\n```\n\nKeep the final recommendation grounded in evidence. Do not claim an update is safe if breaking warnings exist, the diff could not be fetched, or there are uncommitted local changes that may need review.\n","## Purpose\n\nShow a read-only preview of the changes available before running `\u002Famp-update`. This command helps users understand what is new, what may be removed or renamed, what customizations will be protected, and whether any breaking-change warning is available.\n\n**When to use:**\n- Before `\u002Famp-update` when you want a plain-English preview.\n- When `\u002Famp-whats-new` says an update is available and you want file-level detail.\n- When you have custom skills, MCP entries, or protected user instructions and want to confirm they are visible before updating.\n\n**Read-only guarantee:** This workflow does not merge, reset, checkout, stash, commit, or apply updates. It only reads local files and, when Git is available, runs `git fetch` so the remote comparison point is current.\n\n---\n\n## Inputs\n\n`$ARGUMENTS` is optional.\n\nSupported modes:\n- No argument: compare current `HEAD` with the latest production `main`.\n- `--no-fetch`: skip network fetch and compare against the currently cached remote-tracking branch.\n- `--full`: include raw commit subjects and a longer changed-file summary.\n\n---\n\n## Step 1: Detect Git and Remote\n\nCheck whether the current Amp install is a Git repository:\n\n```bash\ngit rev-parse --is-inside-work-tree\n```\n\nIf Git is unavailable or the command fails, continue with a limited local-only preview:\n\n```text\n⚠️ Git preview unavailable\n\nI could not compare your install with production because this folder is not a Git checkout or Git is not installed.\n\nWhat I can still show:\n- Protected customizations I can detect locally\n- Manual update guidance\n\nTo enable full previews, install Amp from the Git repository instead of a ZIP download.\n```\n\nWhen Git is available, detect the production remote. Prefer `upstream`, fall back to `origin`:\n\n```bash\nif git remote | grep -qx 'upstream'; then\n  AMP_REMOTE='upstream'\nelif git remote | grep -qx 'origin'; then\n  AMP_REMOTE='origin'\nelse\n  AMP_REMOTE=''\nfi\n```\n\nIf no remote exists, explain that remote comparison is unavailable and continue with the protected customizations inventory.\n\n---\n\n## Step 2: Refresh Production Main Without Applying Updates\n\nUnless `--no-fetch` is present, fetch the production branch only:\n\n```bash\ngit fetch \"$AMP_REMOTE\" main:refs\u002Fremotes\u002F$AMP_REMOTE\u002Fmain --prune\n```\n\nSet the comparison target:\n\n```bash\nAMP_TARGET=\"$AMP_REMOTE\u002Fmain\"\n```\n\nValidate the target exists:\n\n```bash\ngit rev-parse --verify \"$AMP_TARGET\"\n```\n\nIf fetch fails, use the cached remote-tracking branch if available. If no target is available, report the failure and continue with local inventory only.\n\n---\n\n## Step 3: Look for an Update Manifest, Then Fall Back to Git Diff\n\nA production update manifest may be available. If one exists locally or in the fetched target, use it to enrich the preview. Check likely manifest paths without assuming one is present:\n\n```bash\nfor path in \\\n  System\u002Fupdate-manifest.json \\\n  System\u002Fupdate-manifest.yaml \\\n  System\u002Fupdate-manifest.yml \\\n  .amp\u002Fupdate-manifest.json \\\n  amp-update-manifest.json \\\n  release-manifest.json; do\n  if [ -f \"$path\" ]; then\n    echo \"local:$path\"\n    break\n  fi\n  if git cat-file -e \"$AMP_TARGET:$path\" 2>\u002Fdev\u002Fnull; then\n    echo \"remote:$path\"\n    break\n  fi\ndone\n```\n\nIf a local manifest is found, read it from the working tree. If a remote manifest is found, read it from the target tree with `git show \"$AMP_TARGET:$path\"`. Use any available fields for:\n- Version or release name\n- Summary\n- Added features\n- Removed features\n- Renamed features\n- Breaking changes\n- Migrations\n- Protected paths or customization rules\n\nIf no manifest is found, say so plainly and generate the preview from Git diff data:\n\n```text\nNo update manifest found on production main yet, so this preview is based on Git commits and changed files.\n```\n\n---\n\n## Step 4: Compare Commits and Files\n\nCollect the commit range and changed files:\n\n```bash\ngit log --oneline --decorate --no-merges HEAD..\"$AMP_TARGET\"\ngit diff --name-status HEAD..\"$AMP_TARGET\"\ngit diff --stat HEAD..\"$AMP_TARGET\"\n```\n\nIf there are no commits in `HEAD..$AMP_TARGET`, report:\n\n```text\n✅ You're already aligned with production main.\n\nNo update is waiting. I still checked protected customizations below.\n```\n\nFor normal output, summarize:\n- Number of commits ahead on production.\n- Top commit subjects, grouped when possible by prefix or area.\n- Changed file counts by area: skills, MCP\u002Fcore, scripts, docs, templates, tests.\n- File status counts: added, modified, deleted, renamed.\n\n---\n\n## Step 5: Identify Added, Removed, and Renamed Features\n\nUse manifest data first when available. Otherwise infer cautiously from file paths.\n\nFeature path patterns:\n- Skills: `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`\n- MCP servers: `core\u002Fmcp\u002F*_server.py`\n- User docs: `docs\u002F*.md`, `README.md`, `CLAUDE.md.template`, `AGENTS.md`\n- Templates: `System\u002FTemplates\u002F*`, `06-Resources\u002FTemplates\u002F*`\n- Scripts: `scripts\u002F*`, `.scripts\u002F*`\n\nFrom `git diff --name-status`:\n- `A .claude\u002Fskills\u002Ffoo\u002FSKILL.md` means added skill `\u002Ffoo`.\n- `D .claude\u002Fskills\u002Ffoo\u002FSKILL.md` means removed skill `\u002Ffoo`.\n- `R... old new` under `.claude\u002Fskills\u002F` means renamed skill.\n- Apply the same pattern to MCP servers, docs, and templates when names clearly map to user-visible features.\n\nDo not overstate inferred changes. Use labels:\n- **From manifest** when the manifest says it directly.\n- **Inferred from file paths** when derived from Git diff.\n- **Needs review** when the file changed but the user impact is not obvious.\n\n---\n\n## Step 6: Breaking-Change Warnings\n\nUse manifest breaking-change fields first. If the manifest contains `breaking_changes`, `breakingChanges`, `warnings`, `migrations`, or `requires_action`, surface them exactly and prominently.\n\nIf there is no manifest, scan commit subjects and changed file paths for likely warning terms:\n\n```bash\ngit log --format='%s' HEAD..\"$AMP_TARGET\" | grep -Ei 'breaking|migration|required|remove|rename|deprecat|manual' || true\ngit diff --name-status HEAD..\"$AMP_TARGET\" | grep -Ei 'migration|template|CLAUDE|AGENTS|requirements|package-lock|install|setup' || true\n```\n\nOutput one of:\n\n```text\n⚠️ Breaking-change warnings\n- [Manifest-provided warning or cautious inferred warning]\n```\n\nor:\n\n```text\n✓ No breaking-change warning found in the manifest or commit\u002Ffile scan.\n```\n\nWhen warnings are inferred, say they are inferred and recommend reading the related commits before updating.\n\n---\n\n## Step 7: Protected Customizations Inventory\n\nInventory local customizations that `\u002Famp-update` should preserve. Do not print private content. Report counts and names only when names are safe and useful.\n\nCheck:\n\n```bash\n# Protected user instruction block\nif [ -f CLAUDE.md ] && grep -q 'USER_EXTENSIONS_START' CLAUDE.md && grep -q 'USER_EXTENSIONS_END' CLAUDE.md; then\n  echo 'user_extensions_block=present'\nelse\n  echo 'user_extensions_block=not_found'\nfi\n\n# Custom skills\nfind .claude\u002Fskills -maxdepth 1 -type d -name '*-custom' -print 2>\u002Fdev\u002Fnull | sed 's#^.claude\u002Fskills\u002F##'\n\n# Custom MCP servers by name only\npython3 - \u003C\u003C'PY'\nimport json\nfrom pathlib import Path\npath = Path('.mcp.json')\nif not path.exists():\n    print('custom_mcp=[]')\nelse:\n    data = json.loads(path.read_text())\n    names = sorted(k for k in data.get('mcpServers', {}) if k.startswith('custom-'))\n    print('custom_mcp=' + repr(names))\nPY\n\n# Locally modified tracked files\ngit status --short\n```\n\nReport:\n\n```text\n🛡️ Protected customizations inventory\n\n- User extension block: present\u002Fnot found\n- Custom skills: N found\n- Custom MCP servers: N found\n- Local uncommitted changes: N files\n\nI did not print private instruction text, MCP command values, environment values, notes, tasks, projects, people pages, or meeting notes.\n```\n\nIf custom items are missing, avoid implying data loss. Say only that none were detected.\n\n---\n\n## Step 8: Produce the Preview\n\nUse this structure:\n\n```text\n# Amp update preview\n\nCompared: current HEAD → \u003Cremote>\u002Fmain\nRemote: \u003Cremote>\nMode: manifest-enriched | git-diff only | local inventory only\n\n## Summary\n- \u003CN> commits available\n- \u003CN> files changed: \u003CA> added, \u003CM> modified, \u003CD> deleted, \u003CR> renamed\n- Biggest areas: skills, docs, core, templates, tests\n\n## Added features\n- \u002Fskill-name, from manifest or inferred from file path\n\n## Removed features\n- None found, or list items\n\n## Renamed features\n- None found, or old → new\n\n## Breaking-change warnings\n- None found, or list warnings\n\n## Protected customizations inventory\n- User extension block: present\u002Fnot found\n- Custom skills: count\n- Custom MCP servers: count\n- Local modified tracked files: count\n\n## What this means for you\nPlain-English explanation of likely impact:\n- What new capability they get\n- Whether any behavior may change\n- Whether anything needs review before `\u002Famp-update`\n- Whether it looks safe to proceed\n\n## Next step\n- If comfortable: run `\u002Famp-update`\n- If cautious: run `\u002Famp-update-preflight`\n- If warnings appeared: read the listed commits or release notes first\n```\n\nKeep the final recommendation grounded in evidence. Do not claim an update is safe if breaking warnings exist, the diff could not be fetched, or there are uncommitted local changes that may need review.\n",{"name":5,"description":7},"main","6a447b9ff35eed7bda9e12399bcd373dd31e0a53",".claude\u002Fskills\u002Famp-show-changes","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp","https:\u002F\u002Fgithub.com\u002Fhemory","https:\u002F\u002Fwww.heminthehat.com\u002F","The People Developer | L&D Program Manager | Software Engineer","2026-06-09 00:20:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add hemory\u002Famp --skill amp-show-changes",{"tool":38,"command":39},"bunx","bunx skills add hemory\u002Famp --skill amp-show-changes",{"tool":41,"command":42},"pnpm","pnpm dlx skills add hemory\u002Famp --skill amp-show-changes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Famp-show-changes\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M76W5GGTP0YHZQQJ4G2ZPSZE","zoom-setup","Connect Zoom to Amp for meeting recordings, scheduling, and transcript context","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzoom-setup\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M76W5CWR8MABE0XPZVRXFMDK","xray","Understand what just happened under the hood - learn AI by seeing it in action","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxray\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M76W582J6PD3TTXZXFA2HVQJ","week-review","Review week's progress with concrete accomplishments (not fake percentages), pattern detection, and goal tracking.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-review\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M76W54EY8D8Y55DEPYPJ9YBV","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\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-plan\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M76W527EJ43YXBN0CE9SRAYT","triage","Strategically route orphaned files and extract scattered tasks","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M76W4ZYRDVHZ3SS8W5WZ53Q8","trello-setup","Connect Trello to Amp for visual Kanban task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftrello-setup\u002FSKILL.md",[],[]]