[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3AFG4RM2MPM91J83NS3KS":3,"skill-same:01M6D3AFG4RM2MPM91J83NS3KS":77},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6D3AFG4RM2MPM91J83NS3KS","google-workspace-setup",null,"Connect Google Workspace (Gmail, Calendar, Docs) to Amp for email-aware planning and meeting prep","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\u002Fgoogle-workspace-setup\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"google workspace setup","google","workspace setup","google workspace","setup","workspace","communication","calendar","Google-Workspace","oauth2","email","meeting prep","MCP","planning","connect","docs","gmail","2026-11-10 10:12:30",false,"---\nname: google-workspace-setup\ndescription: Connect Google Workspace (Gmail, Calendar, Docs) to Amp for email-aware planning and meeting prep\nintegration:\n  id: google-workspace\n  name: Google Workspace\n  auth: oauth2\n  mcp_server: google-workspace-mcp\n  category: communication\n  sync_direction: bidirectional\n---\n\n# Google Workspace Setup\n\nConnect your Google Workspace to Amp so your daily plans, meeting prep, and weekly reviews get richer context from email, Google Calendar, and Docs.\n\n## What This Enables\n\nOnce connected, Amp can:\n\n**Read:**\n- Search emails by sender, subject, or keyword\n- Surface unread emails from priority senders\n- Pull email threads for meeting attendees\n- Access Google Calendar events (if not using Apple Calendar)\n- Search Google Docs and Sheets\n\n**Write (always with your confirmation):**\n- Send emails (Amp will always show you the draft and ask before sending)\n- Create calendar events\n- Create or update Google Docs\n\n**Skill Enhancements:**\n- **Daily Plan** (`\u002Fdaily-plan`) gets an email digest -- unread count, threads needing reply, emails from today's meeting contacts\n- **Meeting Prep** (`\u002Fmeeting-prep`) shows recent email threads with each attendee\n- **Week Review** (`\u002Fweek-review`) includes email stats -- sent\u002Freceived, response time, top correspondents\n- **Draft Messages** (if configured) can send via Gmail with confirmation\n\n**New Capabilities:**\n- **Email Follow-Up Detection:** During `\u002Fdaily-plan`, Amp checks for emails awaiting replies for more than 48 hours and surfaces them: \"Sarah hasn't replied to your pricing email from 3 days ago. Draft a nudge?\"\n\n## Privacy\n\nAmp reads your email **on demand** -- nothing is stored permanently. Emails are fetched, summarized, and discarded after the session. Only YOUR account is accessible (scoped to your OAuth login). The OAuth token stays local on your machine and is gitignored.\n\n## When to Run\n\n- User types `\u002Fgoogle-workspace-setup`\n- User asks about connecting Gmail or Google Workspace\n- User wants email context in daily plans or meeting prep\n- During `\u002Fintegrate-mcp` if Gmail or Google Workspace is mentioned\n\n---\n\n## Setup Flow\n\n### Step 1: Check if Already Connected\n\n1. Check `System\u002Fintegrations\u002Fconfig.yaml` for `google-workspace.enabled: true`\n2. If enabled, try a test query via Google Workspace MCP (e.g., search for a recent email)\n3. If healthy and responding, skip to **Step 5** (Configure Labels)\n4. If the tool is not available or errors, continue to Step 2\n\n### Step 2: Explain What We're Setting Up\n\nSay:\n\n```\n**Let's connect Google Workspace to Amp.**\n\nThis uses an open-source MCP bridge that connects to your Google account via OAuth.\nYou'll authorize Amp once, and it remembers your login locally.\n\n**What you'll need:**\n- A Google account (Gmail, Workspace, or personal)\n- About 3 minutes for the OAuth flow\n\n**What Amp will be able to do:**\n- Read your emails (search, unread, threads)\n- Read Google Calendar, Docs, and Sheets\n- Send emails and create events (always with your confirmation first)\n\n**Ready to go?**\n```\n\nWait for confirmation.\n\n### Step 3: Add the Google Workspace MCP Server\n\nCheck the user's MCP configuration. If `google-workspace-mcp` is not listed:\n\n1. Explain what we're adding:\n\n```\nI need to add the Google Workspace connector to your Amp configuration.\n\nThis is an open-source bridge (github.com\u002Ftaylorwilsdon\u002Fgoogle_workspace_mcp)\nthat connects to Google's APIs via OAuth. Your credentials stay on your machine.\n```\n\n2. Add to the user's `.mcp.json` (use the `\u002Famp-add-mcp` skill or manual edit):\n\n```json\n{\n  \"google-workspace-mcp\": {\n    \"command\": \"npx\",\n    \"args\": [\"-y\", \"google-workspace-mcp\"],\n    \"env\": {}\n  }\n}\n```\n\n3. Tell the user the MCP server needs to restart for changes to take effect.\n\n### Step 4: Authenticate via OAuth\n\n1. Run `npx google-workspace-mcp` -- this starts the OAuth flow\n2. A browser window opens for Google sign-in\n3. The user authorizes the requested scopes (Gmail read\u002Fsend, Calendar, Docs)\n4. The token is saved locally to `System\u002F.gmail-oauth-token.json`\n\n**If OAuth succeeds:**\n```\nConnected! I can see your Google Workspace account.\n```\n\n**If it fails:**\n```\nThe OAuth flow didn't complete. A few things to check:\n\n1. **Did the browser open?** If not, try copying the URL from the terminal output\n2. **Did you approve all permissions?** Amp needs Gmail, Calendar, and Docs access\n3. **Firewall or proxy?** Corporate networks sometimes block OAuth redirects\n\nWant to retry?\n```\n\nRetry up to 2 times, then offer to skip and come back later.\n\n### Step 5: Configure Labels and Write Preferences\n\nOnce connected, ask:\n\n```\n**Which Gmail labels matter most for your work?**\n\nI'll prioritize these when building your email digest.\n\nCommon choices:\n- INBOX (always included)\n- IMPORTANT\n- STARRED\n- Custom labels (e.g., \"Deals\", \"Follow-Up\")\n\n**Which labels should I watch?** (Just list names, or say \"show me what's available\")\n```\n\nThen ask about write operations:\n\n```\n**For sending emails and creating events:**\n\nWould you prefer:\n1. **Auto-draft** -- I'll compose messages and show them for your approval before sending\n2. **Ask each time** -- I'll ask before even drafting anything\n\n(You can change this anytime by re-running \u002Fgoogle-workspace-setup)\n```\n\nSave their preference. Map choice 1 to `draft_and_send: true`, choice 2 to `draft_and_send: false`.\n\n### Step 6: Test the Connection\n\nRun a quick test to confirm everything works:\n\n1. Search for a recent email (e.g., from the last 24 hours)\n2. Verify calendar access (list today's events)\n\nShow a brief summary:\n\n```\n**Quick test results:**\n- Email search: Working (found [N] recent emails)\n- Calendar: Working (found [N] events today)\n\nEverything looks good!\n```\n\nIf either fails, troubleshoot before proceeding.\n\n### Step 7: Save Configuration\n\nWrite to `System\u002Fintegrations\u002Fconfig.yaml` -- update the google-workspace section:\n\n```yaml\ngoogle-workspace:\n  enabled: true\n  configured_at: YYYY-MM-DD\n  mcp_server: google-workspace-mcp\n  auth_type: oauth2\n  account: user@example.com\n  labels:\n    - INBOX\n    - IMPORTANT\n  features:\n    email_digest: true\n    email_followup: true\n    draft_and_send: true   # or false based on user preference\n```\n\nIf the file already exists, only update the `google-workspace:` section. Preserve other integration configs.\n\n### Step 8: Confirm with Capability Cascade\n\n```\n**Google Workspace is connected!**\n\nHere's what just got enhanced:\n\n- **Daily Plan** (`\u002Fdaily-plan`) now includes an email digest:\n  - Unread count from priority senders\n  - Threads needing reply (> 24h)\n  - Emails from today's meeting attendees\n  - Follow-up detection (\"Sarah hasn't replied in 3 days\")\n\n- **Meeting Prep** (`\u002Fmeeting-prep`) now shows email context:\n  - Recent email threads with each attendee\n  - Last email date and topic\n  - Unanswered emails to flag\n\n- **Week Review** (`\u002Fweek-review`) now includes email stats:\n  - Emails sent\u002Freceived this week\n  - Average response time\n  - Top senders and recipients\n\nYou can adjust settings anytime by running `\u002Fgoogle-workspace-setup` again.\n```\n\n---\n\n## New Capabilities\n\n### Email Follow-Up Detection\n\nDuring `\u002Fdaily-plan`, Amp checks for stale email threads:\n\n1. Search for sent emails from the last 7 days\n2. For each sent email, check if there's a reply\n3. If no reply after 48 hours, surface it:\n\n```\n**Emails awaiting reply:**\n- Sarah Chen hasn't replied to your pricing email (sent 3 days ago). Draft a nudge?\n- Mike Ross hasn't replied to the proposal follow-up (sent 2 days ago).\n```\n\n**Rules:**\n- Only check emails YOU sent (not inbound)\n- 48-hour threshold (skip weekends in the count)\n- Limit to 5 items max (don't overwhelm)\n- Only runs if `google-workspace.features.email_followup: true` in config\n- Surfaces during the email digest step of `\u002Fdaily-plan`\n\n---\n\n## Troubleshooting\n\n### OAuth Token Expired\n\nGoogle OAuth tokens typically last 1 hour, but refresh tokens are longer-lived. If you see auth errors:\n\n1. Run `\u002Fgoogle-workspace-setup` to trigger a token refresh\n2. If the refresh token is also expired, you'll need to re-authorize through the browser\n3. This is rare -- usually happens after 6+ months or if you revoked access in Google settings\n\n### \"Google Workspace MCP not found\"\n\nThe server might not be in your configuration. Re-run `\u002Fgoogle-workspace-setup` and it will detect and fix this.\n\n### Permission Errors\n\nIf certain features don't work (e.g., can't send emails):\n\n1. The OAuth scopes might be incomplete\n2. Run `\u002Fgoogle-workspace-setup` to re-authorize with full scopes\n3. Make sure you approved ALL permissions in the Google consent screen\n\n### Rate Limiting\n\nGoogle APIs have generous limits for personal use. If you see rate errors:\n\n1. Wait 60 seconds and retry\n2. If persistent, you may be hitting a Workspace admin quota\n3. Contact your IT team if you're on a managed Workspace account\n\n### Corporate Workspace Restrictions\n\nSome organizations restrict OAuth access for third-party apps:\n\n1. Check with your IT admin if OAuth is allowed\n2. They may need to whitelist the google-workspace-mcp client ID\n3. Alternative: Use a personal Gmail account for now\n\n---\n\n## Reconfiguration\n\nIf the user runs `\u002Fgoogle-workspace-setup` when already configured:\n\n1. Check current status via a test query\n2. Show current config from `System\u002Fintegrations\u002Fconfig.yaml`\n3. Offer options:\n   - Update watched labels\n   - Change write preferences (auto-draft vs ask each time)\n   - Re-authenticate (if token expired)\n   - Disconnect Gmail\n\n### Disconnect Flow\n\nIf user wants to disconnect:\n\n1. Update `System\u002Fintegrations\u002Fconfig.yaml`:\n   ```yaml\n   google-workspace:\n     enabled: false\n   ```\n2. Confirm: \"Google Workspace is disconnected. Your daily plans, meeting prep, and reviews will no longer include email context. Run `\u002Fgoogle-workspace-setup` anytime to reconnect.\"\n","# Google Workspace Setup\n\nConnect your Google Workspace to Amp so your daily plans, meeting prep, and weekly reviews get richer context from email, Google Calendar, and Docs.\n\n## What This Enables\n\nOnce connected, Amp can:\n\n**Read:**\n- Search emails by sender, subject, or keyword\n- Surface unread emails from priority senders\n- Pull email threads for meeting attendees\n- Access Google Calendar events (if not using Apple Calendar)\n- Search Google Docs and Sheets\n\n**Write (always with your confirmation):**\n- Send emails (Amp will always show you the draft and ask before sending)\n- Create calendar events\n- Create or update Google Docs\n\n**Skill Enhancements:**\n- **Daily Plan** (`\u002Fdaily-plan`) gets an email digest -- unread count, threads needing reply, emails from today's meeting contacts\n- **Meeting Prep** (`\u002Fmeeting-prep`) shows recent email threads with each attendee\n- **Week Review** (`\u002Fweek-review`) includes email stats -- sent\u002Freceived, response time, top correspondents\n- **Draft Messages** (if configured) can send via Gmail with confirmation\n\n**New Capabilities:**\n- **Email Follow-Up Detection:** During `\u002Fdaily-plan`, Amp checks for emails awaiting replies for more than 48 hours and surfaces them: \"Sarah hasn't replied to your pricing email from 3 days ago. Draft a nudge?\"\n\n## Privacy\n\nAmp reads your email **on demand** -- nothing is stored permanently. Emails are fetched, summarized, and discarded after the session. Only YOUR account is accessible (scoped to your OAuth login). The OAuth token stays local on your machine and is gitignored.\n\n## When to Run\n\n- User types `\u002Fgoogle-workspace-setup`\n- User asks about connecting Gmail or Google Workspace\n- User wants email context in daily plans or meeting prep\n- During `\u002Fintegrate-mcp` if Gmail or Google Workspace is mentioned\n\n---\n\n## Setup Flow\n\n### Step 1: Check if Already Connected\n\n1. Check `System\u002Fintegrations\u002Fconfig.yaml` for `google-workspace.enabled: true`\n2. If enabled, try a test query via Google Workspace MCP (e.g., search for a recent email)\n3. If healthy and responding, skip to **Step 5** (Configure Labels)\n4. If the tool is not available or errors, continue to Step 2\n\n### Step 2: Explain What We're Setting Up\n\nSay:\n\n```\n**Let's connect Google Workspace to Amp.**\n\nThis uses an open-source MCP bridge that connects to your Google account via OAuth.\nYou'll authorize Amp once, and it remembers your login locally.\n\n**What you'll need:**\n- A Google account (Gmail, Workspace, or personal)\n- About 3 minutes for the OAuth flow\n\n**What Amp will be able to do:**\n- Read your emails (search, unread, threads)\n- Read Google Calendar, Docs, and Sheets\n- Send emails and create events (always with your confirmation first)\n\n**Ready to go?**\n```\n\nWait for confirmation.\n\n### Step 3: Add the Google Workspace MCP Server\n\nCheck the user's MCP configuration. If `google-workspace-mcp` is not listed:\n\n1. Explain what we're adding:\n\n```\nI need to add the Google Workspace connector to your Amp configuration.\n\nThis is an open-source bridge (github.com\u002Ftaylorwilsdon\u002Fgoogle_workspace_mcp)\nthat connects to Google's APIs via OAuth. Your credentials stay on your machine.\n```\n\n2. Add to the user's `.mcp.json` (use the `\u002Famp-add-mcp` skill or manual edit):\n\n```json\n{\n  \"google-workspace-mcp\": {\n    \"command\": \"npx\",\n    \"args\": [\"-y\", \"google-workspace-mcp\"],\n    \"env\": {}\n  }\n}\n```\n\n3. Tell the user the MCP server needs to restart for changes to take effect.\n\n### Step 4: Authenticate via OAuth\n\n1. Run `npx google-workspace-mcp` -- this starts the OAuth flow\n2. A browser window opens for Google sign-in\n3. The user authorizes the requested scopes (Gmail read\u002Fsend, Calendar, Docs)\n4. The token is saved locally to `System\u002F.gmail-oauth-token.json`\n\n**If OAuth succeeds:**\n```\nConnected! I can see your Google Workspace account.\n```\n\n**If it fails:**\n```\nThe OAuth flow didn't complete. A few things to check:\n\n1. **Did the browser open?** If not, try copying the URL from the terminal output\n2. **Did you approve all permissions?** Amp needs Gmail, Calendar, and Docs access\n3. **Firewall or proxy?** Corporate networks sometimes block OAuth redirects\n\nWant to retry?\n```\n\nRetry up to 2 times, then offer to skip and come back later.\n\n### Step 5: Configure Labels and Write Preferences\n\nOnce connected, ask:\n\n```\n**Which Gmail labels matter most for your work?**\n\nI'll prioritize these when building your email digest.\n\nCommon choices:\n- INBOX (always included)\n- IMPORTANT\n- STARRED\n- Custom labels (e.g., \"Deals\", \"Follow-Up\")\n\n**Which labels should I watch?** (Just list names, or say \"show me what's available\")\n```\n\nThen ask about write operations:\n\n```\n**For sending emails and creating events:**\n\nWould you prefer:\n1. **Auto-draft** -- I'll compose messages and show them for your approval before sending\n2. **Ask each time** -- I'll ask before even drafting anything\n\n(You can change this anytime by re-running \u002Fgoogle-workspace-setup)\n```\n\nSave their preference. Map choice 1 to `draft_and_send: true`, choice 2 to `draft_and_send: false`.\n\n### Step 6: Test the Connection\n\nRun a quick test to confirm everything works:\n\n1. Search for a recent email (e.g., from the last 24 hours)\n2. Verify calendar access (list today's events)\n\nShow a brief summary:\n\n```\n**Quick test results:**\n- Email search: Working (found [N] recent emails)\n- Calendar: Working (found [N] events today)\n\nEverything looks good!\n```\n\nIf either fails, troubleshoot before proceeding.\n\n### Step 7: Save Configuration\n\nWrite to `System\u002Fintegrations\u002Fconfig.yaml` -- update the google-workspace section:\n\n```yaml\ngoogle-workspace:\n  enabled: true\n  configured_at: YYYY-MM-DD\n  mcp_server: google-workspace-mcp\n  auth_type: oauth2\n  account: user@example.com\n  labels:\n    - INBOX\n    - IMPORTANT\n  features:\n    email_digest: true\n    email_followup: true\n    draft_and_send: true   # or false based on user preference\n```\n\nIf the file already exists, only update the `google-workspace:` section. Preserve other integration configs.\n\n### Step 8: Confirm with Capability Cascade\n\n```\n**Google Workspace is connected!**\n\nHere's what just got enhanced:\n\n- **Daily Plan** (`\u002Fdaily-plan`) now includes an email digest:\n  - Unread count from priority senders\n  - Threads needing reply (> 24h)\n  - Emails from today's meeting attendees\n  - Follow-up detection (\"Sarah hasn't replied in 3 days\")\n\n- **Meeting Prep** (`\u002Fmeeting-prep`) now shows email context:\n  - Recent email threads with each attendee\n  - Last email date and topic\n  - Unanswered emails to flag\n\n- **Week Review** (`\u002Fweek-review`) now includes email stats:\n  - Emails sent\u002Freceived this week\n  - Average response time\n  - Top senders and recipients\n\nYou can adjust settings anytime by running `\u002Fgoogle-workspace-setup` again.\n```\n\n---\n\n## New Capabilities\n\n### Email Follow-Up Detection\n\nDuring `\u002Fdaily-plan`, Amp checks for stale email threads:\n\n1. Search for sent emails from the last 7 days\n2. For each sent email, check if there's a reply\n3. If no reply after 48 hours, surface it:\n\n```\n**Emails awaiting reply:**\n- Sarah Chen hasn't replied to your pricing email (sent 3 days ago). Draft a nudge?\n- Mike Ross hasn't replied to the proposal follow-up (sent 2 days ago).\n```\n\n**Rules:**\n- Only check emails YOU sent (not inbound)\n- 48-hour threshold (skip weekends in the count)\n- Limit to 5 items max (don't overwhelm)\n- Only runs if `google-workspace.features.email_followup: true` in config\n- Surfaces during the email digest step of `\u002Fdaily-plan`\n\n---\n\n## Troubleshooting\n\n### OAuth Token Expired\n\nGoogle OAuth tokens typically last 1 hour, but refresh tokens are longer-lived. If you see auth errors:\n\n1. Run `\u002Fgoogle-workspace-setup` to trigger a token refresh\n2. If the refresh token is also expired, you'll need to re-authorize through the browser\n3. This is rare -- usually happens after 6+ months or if you revoked access in Google settings\n\n### \"Google Workspace MCP not found\"\n\nThe server might not be in your configuration. Re-run `\u002Fgoogle-workspace-setup` and it will detect and fix this.\n\n### Permission Errors\n\nIf certain features don't work (e.g., can't send emails):\n\n1. The OAuth scopes might be incomplete\n2. Run `\u002Fgoogle-workspace-setup` to re-authorize with full scopes\n3. Make sure you approved ALL permissions in the Google consent screen\n\n### Rate Limiting\n\nGoogle APIs have generous limits for personal use. If you see rate errors:\n\n1. Wait 60 seconds and retry\n2. If persistent, you may be hitting a Workspace admin quota\n3. Contact your IT team if you're on a managed Workspace account\n\n### Corporate Workspace Restrictions\n\nSome organizations restrict OAuth access for third-party apps:\n\n1. Check with your IT admin if OAuth is allowed\n2. They may need to whitelist the google-workspace-mcp client ID\n3. Alternative: Use a personal Gmail account for now\n\n---\n\n## Reconfiguration\n\nIf the user runs `\u002Fgoogle-workspace-setup` when already configured:\n\n1. Check current status via a test query\n2. Show current config from `System\u002Fintegrations\u002Fconfig.yaml`\n3. Offer options:\n   - Update watched labels\n   - Change write preferences (auto-draft vs ask each time)\n   - Re-authenticate (if token expired)\n   - Disconnect Gmail\n\n### Disconnect Flow\n\nIf user wants to disconnect:\n\n1. Update `System\u002Fintegrations\u002Fconfig.yaml`:\n   ```yaml\n   google-workspace:\n     enabled: false\n   ```\n2. Confirm: \"Google Workspace is disconnected. Your daily plans, meeting prep, and reviews will no longer include email context. Run `\u002Fgoogle-workspace-setup` anytime to reconnect.\"\n",{"name":5,"description":7,"integration":49},{"id":50,"auth":36,"name":51,"category":33,"mcp_server":52,"sync_direction":53},"google-workspace","Google Workspace","google-workspace-mcp","bidirectional","main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Fgoogle-workspace-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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill google-workspace-setup",{"tool":69,"command":70},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill google-workspace-setup",{"tool":72,"command":73},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill google-workspace-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgoogle-workspace-setup\u002FSKILL.md",true,[],[78,107,116,130,144,156],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":90,"publishedAt":44},"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",[84,85],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[91,31,92,39,93,41,94,95,96,36,97,98,99,100,101,102,103,104,105,106],"zoom setup","schedule","review","transcript","search","stats","confirmation","context","meetings","process","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":44},"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",[],[109,114,115],"learn","just",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":44},"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",[122],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[124,93,125,126,127,128,129],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":44},"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",[],[137,138,34,139,140,141,142,143],"week plan","plan","SET","shape","goals","task","priorities",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":44},"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",[],[146,151,152,153,154,155],"tasks","fast","extract","files","route",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":166,"publishedAt":44},"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",[162,165],{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[167,168,31,169,41,39,170,142,171,172,173,174,175],"trello","trello setup","sync","token","kanban","bun","visual","api","server"]