[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D33J1M4TN3ZKVVEKA8TCWK":3,"skill-same:01M6D33J1M4TN3ZKVVEKA8TCWK":62},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M6D33J1M4TN3ZKVVEKA8TCWK","pi",null,"Route tasks to Pi for comparison testing. Toggle Pi mode or run specific commands through Pi.","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\u002Freference\u002Fbeta-templates\u002Fpi\u002Fskills\u002Fpi\u002FSKILL.md",[],[5,19,20,21,22,23],"testing","tasks","run","route","commands","2026-11-10 10:12:30",false,"---\nname: pi\ndescription: Route tasks to Pi for comparison testing. Toggle Pi mode or run specific commands through Pi.\nbeta_required: pi\n---\n\n# Pi Integration\n\nRun tasks through Pi (Mario Zechner's self-extending coding agent) to compare with Claude Code.\n\n## Usage\n\n| Command | Effect |\n|---------|--------|\n| `\u002Fpi` | Open Pi in a new terminal (no preset task) |\n| `\u002Fpi on` | Enable Pi mode - prefer Pi for building tasks |\n| `\u002Fpi off` | Disable Pi mode - back to Claude Code |\n| `\u002Fpi \u002Fdaily-plan` | Run a specific skill through Pi with full context |\n| `\u002Fpi \"build me a tool that...\"` | Run a custom task through Pi |\n\n---\n\n## How It Works\n\nWhen you run `\u002Fpi \u003Ccommand>`:\n\n1. **Skill Detection:** If the command is a skill (starts with `\u002F`), read its SKILL.md\n2. **Context Gathering:** Collect user profile, pillars, today's date, vault path\n3. **Terminal Launch:** Open a new Terminal.app window with Pi\n4. **Context Injection:** Pi receives the full skill instructions + context\n\nThis ensures a **fair comparison** - Pi gets the same instructions Claude Code would get.\n\n---\n\n## Implementation\n\n### `\u002Fpi` (No Arguments)\n\nOpen Pi in a new terminal window in the vault directory.\n\n**macOS (default):**\n```bash\nosascript -e 'tell application \"Terminal\"\n    do script \"cd \\\"'$VAULT_PATH'\\\" && pi\"\n    activate\nend tell'\n```\n\n**If in tmux:**\n```bash\ntmux split-window -h \"cd \\\"$VAULT_PATH\\\" && pi\"\n```\n\n**Output to user:**\n```\n✓ Pi opened in new Terminal window\n\n  You can now interact with Pi directly.\n  When done, Cmd+Tab back here.\n```\n\n---\n\n### `\u002Fpi on`\n\nEnable Pi mode for the session.\n\n**Steps:**\n\n1. Read `System\u002Fuser-profile.yaml`\n2. Set or update `pi_mode: true` under a `beta` section:\n   ```yaml\n   beta:\n     pi_mode: true\n   ```\n3. Confirm to user:\n   ```\n   ✓ Pi mode enabled\n\n   Tasks will prefer Pi. To run something in Claude Code instead,\n   just say \"use Claude Code for this\" or run `\u002Fpi off`.\n   ```\n\n**Behavior when Pi mode is on:**\n\nWhen the user asks to build something (e.g., \"build me a tool that tracks relationships\"):\n- Suggest running it through Pi: \"Pi mode is on. I'll open Pi with this task.\"\n- Automatically invoke `\u002Fpi \"build me a tool that tracks relationships\"`\n\n---\n\n### `\u002Fpi off`\n\nDisable Pi mode.\n\n**Steps:**\n\n1. Read `System\u002Fuser-profile.yaml`\n2. Set `pi_mode: false` under `beta` section\n3. Confirm:\n   ```\n   ✓ Pi mode disabled\n\n   Back to Claude Code for all tasks.\n   ```\n\n---\n\n### `\u002Fpi \u003Cskill>` (e.g., `\u002Fpi \u002Fdaily-plan`)\n\nRun an Amp skill through Pi with full context.\n\n**Steps:**\n\n1. **Parse the skill name:**\n   - Extract skill name from command (e.g., `daily-plan` from `\u002Fdaily-plan`)\n   - Handle with or without leading `\u002F`\n\n2. **Locate skill file:**\n   - Check `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`\n   - Also check `.claude\u002Fskills\u002F\u003Cskill-name>-dave\u002FSKILL.md` (user variants)\n   - If not found, report error\n\n3. **Read skill instructions:**\n   - Read full SKILL.md content\n   - This is what Claude Code would use\n\n4. **Gather context:**\n   ```\n   VAULT_PATH: \u002Fpath\u002Fto\u002Fvault\n   DATE: 2026-02-03\n   DAY: Monday\n   USER_NAME: [from user-profile.yaml]\n   PILLARS: [from pillars.yaml]\n   ```\n\n5. **Build Pi prompt:**\n   Combine skill instructions + context into a single prompt:\n\n   ```markdown\n   # Task: [Skill Name]\n\n   You are helping a user with their personal knowledge system (Amp).\n   Execute the following skill instructions.\n\n   ## Context\n\n   - **Vault Path:** [vault path from pwd or user-profile.yaml]\n   - **Date:** [current date]\n   - **User:** [from user-profile.yaml]\n   - **Pillars:** [list from pillars.yaml]\n\n   ## Skill Instructions\n\n   [Full SKILL.md content here]\n\n   ---\n\n   Execute this skill now. You have access to the vault at the path above.\n   Read files as needed to gather context.\n   ```\n\n6. **Launch Pi with prompt:**\n\n   Write prompt to a temp file, then launch Pi:\n\n   ```bash\n   # Write prompt to temp file (handles special characters)\n   PROMPT_FILE=$(mktemp)\n   cat > \"$PROMPT_FILE\" \u003C\u003C 'PROMPT_EOF'\n   [Full prompt content]\n   PROMPT_EOF\n\n   # Launch Pi in new Terminal\n   osascript -e 'tell application \"Terminal\"\n       do script \"cd \\\"'$VAULT_PATH'\\\" && pi -p \\\"$(cat '$PROMPT_FILE')\\\" && rm '$PROMPT_FILE'\"\n       activate\n   end tell'\n   ```\n\n7. **Confirm to user:**\n   ```\n   ✓ Pi launched with \u002Fdaily-plan\n\n   Pi has received the full skill instructions and context.\n   A new Terminal window should now be active.\n\n   When done, compare the results:\n   - Pi's output: See Terminal window\n   - Claude Code: Run \u002Fdaily-plan here\n   ```\n\n---\n\n### `\u002Fpi \"custom task\"` (Quoted String)\n\nRun a custom task (not a skill) through Pi.\n\n**Steps:**\n\n1. Extract the task description from quotes\n2. Gather basic context (vault path, date, user)\n3. Build prompt:\n   ```markdown\n   # Task\n\n   [User's task description]\n\n   ## Context\n\n   - **Vault Path:** [vault path from pwd or user-profile.yaml]\n   - **Date:** [current date]\n\n   Execute this task. You have access to the vault.\n   ```\n\n4. Launch Pi with prompt (same as above)\n\n---\n\n## Error Handling\n\n### Pi Not Installed\n\nIf `pi` command not found:\n\n```\n❌ Pi is not installed\n\nInstall it with:\n  npm install -g @mariozechner\u002Fpi-coding-agent\n\nThen try again.\n```\n\n### Skill Not Found\n\nIf skill doesn't exist:\n\n```\n❌ Skill not found: \u002Funknown-skill\n\nAvailable skills:\n  \u002Fdaily-plan, \u002Fdaily-review, \u002Fweek-plan, ...\n\nOr run a custom task:\n  \u002Fpi \"build me a tool that...\"\n```\n\n### Beta Not Activated\n\nIf Pi beta not activated:\n\n```\n❌ Pi integration requires beta activation\n\nRun: \u002Fbeta-activate PILAUNCH2026\n```\n\n---\n\n## Environment Detection\n\nDetect the user's environment to choose the best terminal launch method:\n\n```bash\n# Check if in tmux\nif [ -n \"$TMUX\" ]; then\n    # Use tmux split\n    tmux split-window -h \"cd \\\"$VAULT_PATH\\\" && pi\"\nelse\n    # Check OS\n    if [[ \"$OSTYPE\" == \"darwin\"* ]]; then\n        # macOS - use Terminal.app or iTerm2\n        if [ -d \"\u002FApplications\u002FiTerm.app\" ]; then\n            osascript -e 'tell application \"iTerm\"\n                create window with default profile\n                tell current session of current window\n                    write text \"cd \\\"'$VAULT_PATH'\\\" && pi\"\n                end tell\n            end tell'\n        else\n            osascript -e 'tell application \"Terminal\"\n                do script \"cd \\\"'$VAULT_PATH'\\\" && pi\"\n                activate\n            end tell'\n        fi\n    else\n        # Linux - try common terminals\n        if command -v gnome-terminal &> \u002Fdev\u002Fnull; then\n            gnome-terminal -- bash -c \"cd \\\"$VAULT_PATH\\\" && pi; exec bash\"\n        elif command -v xterm &> \u002Fdev\u002Fnull; then\n            xterm -e \"cd \\\"$VAULT_PATH\\\" && pi\" &\n        else\n            echo \"Please open a terminal and run: cd \\\"$VAULT_PATH\\\" && pi\"\n        fi\n    fi\nfi\n```\n\n---\n\n## Comparison Workflow\n\nAfter running a task through Pi:\n\n1. **Review Pi's output** in the Terminal window\n2. **Run the same task** in Claude Code (e.g., `\u002Fdaily-plan`)\n3. **Compare:**\n   - Quality of output\n   - Time taken (subjective)\n   - Ease of iteration\n   - Integration with Amp\n\n4. **Capture learnings** (optional):\n   ```\n   \u002Fpi capture\n   ```\n   Logs the comparison to `System\u002FPi_Comparisons\u002FYYYY-MM-DD.md`\n\n---\n\n## Notes\n\n- Pi runs as a **separate process** in its own terminal\n- Pi has access to your vault files but **not** Amp MCP servers\n- For MCP access, Pi uses the MCP bridge (if configured in `.pi\u002F`)\n- Results may differ because Pi's approach is more minimal\n\n---\n\n## Related\n\n- `\u002Fpi-tools` - View synced Pi extensions\n- `\u002Fbeta-status` - Check Pi beta activation\n- `System\u002FBeta\u002Fpi\u002FREADME.md` - Pi setup documentation\n","# Pi Integration\n\nRun tasks through Pi (Mario Zechner's self-extending coding agent) to compare with Claude Code.\n\n## Usage\n\n| Command | Effect |\n|---------|--------|\n| `\u002Fpi` | Open Pi in a new terminal (no preset task) |\n| `\u002Fpi on` | Enable Pi mode - prefer Pi for building tasks |\n| `\u002Fpi off` | Disable Pi mode - back to Claude Code |\n| `\u002Fpi \u002Fdaily-plan` | Run a specific skill through Pi with full context |\n| `\u002Fpi \"build me a tool that...\"` | Run a custom task through Pi |\n\n---\n\n## How It Works\n\nWhen you run `\u002Fpi \u003Ccommand>`:\n\n1. **Skill Detection:** If the command is a skill (starts with `\u002F`), read its SKILL.md\n2. **Context Gathering:** Collect user profile, pillars, today's date, vault path\n3. **Terminal Launch:** Open a new Terminal.app window with Pi\n4. **Context Injection:** Pi receives the full skill instructions + context\n\nThis ensures a **fair comparison** - Pi gets the same instructions Claude Code would get.\n\n---\n\n## Implementation\n\n### `\u002Fpi` (No Arguments)\n\nOpen Pi in a new terminal window in the vault directory.\n\n**macOS (default):**\n```bash\nosascript -e 'tell application \"Terminal\"\n    do script \"cd \\\"'$VAULT_PATH'\\\" && pi\"\n    activate\nend tell'\n```\n\n**If in tmux:**\n```bash\ntmux split-window -h \"cd \\\"$VAULT_PATH\\\" && pi\"\n```\n\n**Output to user:**\n```\n✓ Pi opened in new Terminal window\n\n  You can now interact with Pi directly.\n  When done, Cmd+Tab back here.\n```\n\n---\n\n### `\u002Fpi on`\n\nEnable Pi mode for the session.\n\n**Steps:**\n\n1. Read `System\u002Fuser-profile.yaml`\n2. Set or update `pi_mode: true` under a `beta` section:\n   ```yaml\n   beta:\n     pi_mode: true\n   ```\n3. Confirm to user:\n   ```\n   ✓ Pi mode enabled\n\n   Tasks will prefer Pi. To run something in Claude Code instead,\n   just say \"use Claude Code for this\" or run `\u002Fpi off`.\n   ```\n\n**Behavior when Pi mode is on:**\n\nWhen the user asks to build something (e.g., \"build me a tool that tracks relationships\"):\n- Suggest running it through Pi: \"Pi mode is on. I'll open Pi with this task.\"\n- Automatically invoke `\u002Fpi \"build me a tool that tracks relationships\"`\n\n---\n\n### `\u002Fpi off`\n\nDisable Pi mode.\n\n**Steps:**\n\n1. Read `System\u002Fuser-profile.yaml`\n2. Set `pi_mode: false` under `beta` section\n3. Confirm:\n   ```\n   ✓ Pi mode disabled\n\n   Back to Claude Code for all tasks.\n   ```\n\n---\n\n### `\u002Fpi \u003Cskill>` (e.g., `\u002Fpi \u002Fdaily-plan`)\n\nRun an Amp skill through Pi with full context.\n\n**Steps:**\n\n1. **Parse the skill name:**\n   - Extract skill name from command (e.g., `daily-plan` from `\u002Fdaily-plan`)\n   - Handle with or without leading `\u002F`\n\n2. **Locate skill file:**\n   - Check `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`\n   - Also check `.claude\u002Fskills\u002F\u003Cskill-name>-dave\u002FSKILL.md` (user variants)\n   - If not found, report error\n\n3. **Read skill instructions:**\n   - Read full SKILL.md content\n   - This is what Claude Code would use\n\n4. **Gather context:**\n   ```\n   VAULT_PATH: \u002Fpath\u002Fto\u002Fvault\n   DATE: 2026-02-03\n   DAY: Monday\n   USER_NAME: [from user-profile.yaml]\n   PILLARS: [from pillars.yaml]\n   ```\n\n5. **Build Pi prompt:**\n   Combine skill instructions + context into a single prompt:\n\n   ```markdown\n   # Task: [Skill Name]\n\n   You are helping a user with their personal knowledge system (Amp).\n   Execute the following skill instructions.\n\n   ## Context\n\n   - **Vault Path:** [vault path from pwd or user-profile.yaml]\n   - **Date:** [current date]\n   - **User:** [from user-profile.yaml]\n   - **Pillars:** [list from pillars.yaml]\n\n   ## Skill Instructions\n\n   [Full SKILL.md content here]\n\n   ---\n\n   Execute this skill now. You have access to the vault at the path above.\n   Read files as needed to gather context.\n   ```\n\n6. **Launch Pi with prompt:**\n\n   Write prompt to a temp file, then launch Pi:\n\n   ```bash\n   # Write prompt to temp file (handles special characters)\n   PROMPT_FILE=$(mktemp)\n   cat > \"$PROMPT_FILE\" \u003C\u003C 'PROMPT_EOF'\n   [Full prompt content]\n   PROMPT_EOF\n\n   # Launch Pi in new Terminal\n   osascript -e 'tell application \"Terminal\"\n       do script \"cd \\\"'$VAULT_PATH'\\\" && pi -p \\\"$(cat '$PROMPT_FILE')\\\" && rm '$PROMPT_FILE'\"\n       activate\n   end tell'\n   ```\n\n7. **Confirm to user:**\n   ```\n   ✓ Pi launched with \u002Fdaily-plan\n\n   Pi has received the full skill instructions and context.\n   A new Terminal window should now be active.\n\n   When done, compare the results:\n   - Pi's output: See Terminal window\n   - Claude Code: Run \u002Fdaily-plan here\n   ```\n\n---\n\n### `\u002Fpi \"custom task\"` (Quoted String)\n\nRun a custom task (not a skill) through Pi.\n\n**Steps:**\n\n1. Extract the task description from quotes\n2. Gather basic context (vault path, date, user)\n3. Build prompt:\n   ```markdown\n   # Task\n\n   [User's task description]\n\n   ## Context\n\n   - **Vault Path:** [vault path from pwd or user-profile.yaml]\n   - **Date:** [current date]\n\n   Execute this task. You have access to the vault.\n   ```\n\n4. Launch Pi with prompt (same as above)\n\n---\n\n## Error Handling\n\n### Pi Not Installed\n\nIf `pi` command not found:\n\n```\n❌ Pi is not installed\n\nInstall it with:\n  npm install -g @mariozechner\u002Fpi-coding-agent\n\nThen try again.\n```\n\n### Skill Not Found\n\nIf skill doesn't exist:\n\n```\n❌ Skill not found: \u002Funknown-skill\n\nAvailable skills:\n  \u002Fdaily-plan, \u002Fdaily-review, \u002Fweek-plan, ...\n\nOr run a custom task:\n  \u002Fpi \"build me a tool that...\"\n```\n\n### Beta Not Activated\n\nIf Pi beta not activated:\n\n```\n❌ Pi integration requires beta activation\n\nRun: \u002Fbeta-activate PILAUNCH2026\n```\n\n---\n\n## Environment Detection\n\nDetect the user's environment to choose the best terminal launch method:\n\n```bash\n# Check if in tmux\nif [ -n \"$TMUX\" ]; then\n    # Use tmux split\n    tmux split-window -h \"cd \\\"$VAULT_PATH\\\" && pi\"\nelse\n    # Check OS\n    if [[ \"$OSTYPE\" == \"darwin\"* ]]; then\n        # macOS - use Terminal.app or iTerm2\n        if [ -d \"\u002FApplications\u002FiTerm.app\" ]; then\n            osascript -e 'tell application \"iTerm\"\n                create window with default profile\n                tell current session of current window\n                    write text \"cd \\\"'$VAULT_PATH'\\\" && pi\"\n                end tell\n            end tell'\n        else\n            osascript -e 'tell application \"Terminal\"\n                do script \"cd \\\"'$VAULT_PATH'\\\" && pi\"\n                activate\n            end tell'\n        fi\n    else\n        # Linux - try common terminals\n        if command -v gnome-terminal &> \u002Fdev\u002Fnull; then\n            gnome-terminal -- bash -c \"cd \\\"$VAULT_PATH\\\" && pi; exec bash\"\n        elif command -v xterm &> \u002Fdev\u002Fnull; then\n            xterm -e \"cd \\\"$VAULT_PATH\\\" && pi\" &\n        else\n            echo \"Please open a terminal and run: cd \\\"$VAULT_PATH\\\" && pi\"\n        fi\n    fi\nfi\n```\n\n---\n\n## Comparison Workflow\n\nAfter running a task through Pi:\n\n1. **Review Pi's output** in the Terminal window\n2. **Run the same task** in Claude Code (e.g., `\u002Fdaily-plan`)\n3. **Compare:**\n   - Quality of output\n   - Time taken (subjective)\n   - Ease of iteration\n   - Integration with Amp\n\n4. **Capture learnings** (optional):\n   ```\n   \u002Fpi capture\n   ```\n   Logs the comparison to `System\u002FPi_Comparisons\u002FYYYY-MM-DD.md`\n\n---\n\n## Notes\n\n- Pi runs as a **separate process** in its own terminal\n- Pi has access to your vault files but **not** Amp MCP servers\n- For MCP access, Pi uses the MCP bridge (if configured in `.pi\u002F`)\n- Results may differ because Pi's approach is more minimal\n\n---\n\n## Related\n\n- `\u002Fpi-tools` - View synced Pi extensions\n- `\u002Fbeta-status` - Check Pi beta activation\n- `System\u002FBeta\u002Fpi\u002FREADME.md` - Pi setup documentation\n",{"name":5,"description":7,"beta_required":5},"main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Freference\u002Fbeta-templates\u002Fpi\u002Fskills\u002Fpi",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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill pi",{"tool":44,"command":45},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill pi",{"tool":47,"command":48},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill pi","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Freference\u002Fbeta-templates\u002Fpi\u002Fskills\u002Fpi\u002FSKILL.md",true,[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fkeys.md","REFERENCE","参考文档",12085,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-sdk-typescript\u002Fskills\u002Fazure-keyvault-secrets-ts\u002Freferences\u002Fkeys.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fsecrets.md",13644,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-sdk-typescript\u002Fskills\u002Fazure-keyvault-secrets-ts\u002Freferences\u002Fsecrets.md",[63,100,109,123,138,148],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":79,"publishedAt":24},"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",[69,74],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"zoom setup","setup","schedule","MCP","review","connect","transcript","search","stats","oauth2","confirmation","context","meetings","process","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":24},"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",[],[102,107,108],"learn","just",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":24},"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",[115],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[117,84,118,119,120,121,122],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":24},"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",[],[130,131,132,133,134,135,136,137],"week plan","plan","calendar","SET","shape","goals","task","priorities",{"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":144,"publishedAt":24},"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",[],[140,20,145,146,147,22],"fast","extract","files",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":158,"publishedAt":24},"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",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[159,160,81,161,85,83,162,136,163,164,165,166,167],"trello","trello setup","sync","token","kanban","bun","visual","api","server"]