[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3BX1SGRWH2R82N5BYSMAJ":3,"skill-same:01M6D3BX1SGRWH2R82N5BYSMAJ":79},{"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":23,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6D3BX1SGRWH2R82N5BYSMAJ","meeting-prep",null,"Prepare for meetings by gathering attendee context and related topics","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\u002Fmeeting-prep\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27],"meeting prep","prepare","context","meetings","2026-11-10 10:12:30",false,"---\nname: meeting-prep\ndescription: Prepare for meetings by gathering attendee context and related topics\ncontext: fork\n---\n\nPrepare for an upcoming meeting by gathering context on attendees and related topics.\n\n## Tone Calibration\n\nBefore executing this command, read `System\u002Fuser-profile.yaml` → `communication` section and adapt:\n\n**Career Level Adaptations:**\n- **Junior:** Provide more context about attendees, suggest preparation tips\n- **Mid:** Balance context with action, suggest talking points\n- **Senior\u002FLeadership:** Strategic framing, influence opportunities, key decisions\n- **C-Suite:** High-level strategic context, organizational implications, key stakeholders\n\n**Directness:**\n- **Very direct:** Bullet points, key facts only\n- **Balanced:** Context + talking points (default)\n- **Supportive:** Detailed prep, conversation strategies\n\n**Detail Level:**\n- **Concise:** Names, roles, top 3 talking points\n- **Balanced:** Standard prep format\n- **Comprehensive:** Full context, relationship dynamics, strategic considerations\n\nSee CLAUDE.md → \"Communication Adaptation\" for full guidelines.\n\n---\n\n## Arguments\n\n**Optional:** $MEETING, $ATTENDEES\n\nIf not provided, prompt the user for:\n1. Meeting topic or title\n2. List of attendees (comma-separated names)\n\n**Examples:**\n- `\u002Fmeeting-prep \"Q1 Planning\" \"Sarah Chen, Mike Rodriguez\"`\n- `\u002Fmeeting-prep` (then prompt for details)\n\n## What This Does\n\n1. Looks up each attendee in `People\u002F` folder\n2. Surfaces recent interactions and open action items\n3. Checks for related projects\n4. Suggests talking points based on context\n\n## Process\n\n### Step 0: Gather Context (if needed)\n\n**If $MEETING or $ATTENDEES are not provided:**\n\nAsk: \"Which meeting are you prepping for?\"\n- Get meeting topic\u002Ftitle\n\nAsk: \"Who's attending? (comma-separated names or just list them)\"\n- Accept formats: \"Sarah Chen, Mike Rodriguez\" or \"Sarah, Mike\" or natural list\n- Parse into individual attendee names\n\n### Step 1: Attendee Lookup\n\nFor each attendee in $ATTENDEES:\n\n1. Search `05-Areas\u002FPeople\u002FInternal\u002F` and `05-Areas\u002FPeople\u002FExternal\u002F` for matching names\n2. If found, extract:\n   - Role and company\n   - Last interaction date\n   - Open action items involving them\n   - Key context or notes\n\n3. If not found, note: \"No person page for [Name] - consider creating one after the meeting\"\n\n#### Context Enrichment Note\n\nAfter completing attendee lookup, if any attendees are missing person pages or have sparse pages (no role, no recent interactions, no notes), add this hint to the prep output:\n\n> ? I don't have much context on [attendee name(s)]. After the meeting, run `\u002Fprocess-meetings` to build their profile, or create a person page at `05-Areas\u002FPeople\u002F`.\n\nOnly show this for attendees WITHOUT existing person pages or with very sparse pages. Don't show for attendees who already have rich person pages. This hint is informational and does not block meeting prep.\n\n### Step 2: Related Projects\n\nSearch `04-Projects\u002F` for any projects that:\n- Mention the attendees\n- Relate to the meeting topic ($MEETING)\n\nExtract:\n- Project name and status\n- Relevant milestones or blockers\n- Recent updates\n\n### Step 3: Recent Context\n\nSearch `00-Inbox\u002FMeetings\u002F` for recent meetings with these attendees:\n- What was discussed?\n- What was decided?\n- What follow-ups were committed?\n\n### Step 3a: Semantic Context Enrichment (if QMD available)\n\n**This step runs automatically when QMD is installed.** It enriches meeting prep with semantically related vault content that keyword search would miss.\n\nCheck if QMD MCP tools are available by calling `qmd_status`. **If available:**\n\n1. **Semantic search for meeting topic:**\n   ```\n   qmd_search(query=\"$MEETING\", limit=5)\n   ```\n   Look for: related past discussions, relevant decisions, thematic connections — content that shares meaning with the meeting topic but uses different words.\n\n2. **Semantic search for each attendee (beyond their person page):**\n   ```\n   qmd_search(query=\"$ATTENDEE_NAME context discussions decisions\", limit=3)\n   ```\n   Look for: contextual references where this person is mentioned by role\u002Ftitle\u002Fteam (e.g., \"the VP of Sales asked about...\"), not just by name.\n\n3. **Cross-reference results** with what Steps 1-3 already found. **Only surface NEW insights** — content that the keyword-based person page lookup and meeting folder grep in earlier steps missed.\n\n**Add to the prep brief under a \"Semantic Connections\" heading:**\n- Past discussions thematically related to this meeting (even if different keywords were used)\n- Decisions made in adjacent contexts that are relevant here\n- Commitments or open items discovered through semantic matching\n- Related projects or goals that connect by meaning\n\n**If QMD is not available:** Skip this step silently. Steps 1-3 provide the standard keyword-based context.\n\n---\n\n### Step 3b: Integration Context (if available)\n\nCheck `System\u002Fintegrations\u002Fconfig.yaml` to see which integrations are enabled.\n\n**Notion Integration:**\nIf `enabled.notion: true` AND Notion MCP is available:\n```\nSearch Notion for pages related to:\n- Meeting topic ($MEETING)\n- Attendee names\n\nInclude in prep:\n- Relevant Notion docs (title + summary)\n- Shared pages with attendees\n```\n\n**Slack Integration:**\nIf `enabled.slack: true` AND Slack MCP is available:\n```\nSearch Slack for recent conversations:\n- With\u002Fabout each attendee\n- Mentioning the meeting topic\n\nInclude in prep:\n- Recent Slack context (last 7 days)\n- Key threads or decisions\n- Any commitments made\n```\n\n**Teams Integration:**\nIf `teams.enabled: true` AND Teams MCP available:\n```\nSearch Teams chats with attendees:\n- Recent 1:1 and group chats involving each attendee\n- Mentioning the meeting topic\n\nCheck Teams channels related to meeting topic:\n- Project channels, department channels\n- Recent posts and replies\n\nSurface recent decisions from Teams threads:\n- Key decisions made in channel conversations\n- Any commitments or follow-ups from Teams chats\n\nInclude in prep:\n- Recent Teams context (last 7 days)\n- Key threads or decisions from channels\n- Any commitments made in Teams chats\n```\n\n**When BOTH Slack and Teams are enabled:**\n- Check both sources for each attendee\n- Label context by source: \"**From Slack:**\" \u002F \"**From Teams:**\"\n- Deduplicate if the same person appears in both (merge context, label the source)\n- Present in separate sub-sections under Integration Context\n\n**Google Workspace Integration:**\nIf `google-workspace.enabled: true` AND Google Workspace MCP is available:\n```\nSearch Gmail for recent threads with each attendee (last 7 days):\n- Email exchanges and their topics\n- Shared Google Docs mentioned in threads\n- Outstanding email requests (sent but no reply)\n\nSearch for Google Docs related to:\n- Meeting topic ($MEETING)\n- Shared documents with attendees\n\nInclude in prep:\n- Recent email exchanges (last 7 days) — key threads summarized\n- Shared documents — Google Docs, Sheets, or Slides linked in emails\n- Outstanding requests\u002Ffollow-ups — emails waiting > 48h for reply\n```\n\n**Graceful Degradation:**\nIf an integration is enabled but the MCP isn't responding:\n- Skip silently\n- Don't show error to user\n- Continue with vault-only context\n\n### Step 4: Compile Prep Brief\n\n## Output Format\n\n```markdown\n# Meeting Prep: $MEETING\n\n**Date:** [Today's date]\n**Attendees:** $ATTENDEES\n\n---\n\n---\n\n## Demo Mode Check\n\nBefore executing, check if demo mode is active:\n\n1. Read `System\u002Fuser-profile.yaml` and check `demo_mode`\n2. **If `demo_mode: true`:**\n   - Display: \"Demo Mode Active — Using sample data\"\n   - Use `System\u002FDemo\u002F` paths instead of root paths\n   - Write any output to `System\u002FDemo\u002F` subdirectories\n3. **If `demo_mode: false`:** Use normal vault paths\n\n\n## People Context\n\n### [Attendee Name]\n- **Role:** [Role at Company]\n- **Last Interaction:** [Date] - [Topic]\n- **Open Items:**\n  - [ ] [Action item]\n- **Notes:** [Key context about this person]\n\n### [Next Attendee]\n...\n\n---\n\n## Related Projects\n\n| Project | Status | Relevance |\n|---------|--------|-----------|\n| [Name]  | [Status] | [Why it relates] |\n\n---\n\n## Recent History\n\nPrevious meetings with these attendees:\n\n| Date | Topic | Key Outcomes |\n|------|-------|--------------|\n| [Date] | [Topic] | [What was decided\u002Fdiscussed] |\n\n---\n\n## Integration Context (if available)\n\n*This section appears when productivity integrations are enabled.*\n\n### From Slack\n> Recent conversation context with attendees (last 7 days)\n\n### From Teams\n> Recent Teams chats and channel threads with attendees (last 7 days)\n\n### From Notion\n> Related Notion docs: [Doc title](link)\n\n### From Gmail\n> Email threads with [Attendee]: [Summary of outstanding requests]\n\n---\n\n## Suggested Talking Points\n\nBased on the context above:\n\n1. **Follow up on:** [Open item from last meeting]\n2. **Discuss:** [Project-related topic]\n3. **Ask about:** [Something from their context]\n\n---\n\n## Questions to Consider\n\n- What's your main goal for this meeting?\n- What do you need from these attendees?\n- What decisions need to be made?\n\n---\n\n## Post-Meeting\n\nAfter the meeting:\n1. Add notes to `00-Inbox\u002FMeetings\u002FYYYY-MM-DD - [Topic].md`\n2. Update person pages with new context\n3. Create tasks for any action items\n```\n\n---\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark meeting prep as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `meeting_prep_completed` and properties:\n- `attendees_count`: number of attendees\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## When to Use\n\n- Before any meeting with multiple attendees\n- When meeting someone you haven't seen in a while\n- Before important meetings where you want full context\n\n## Tips\n\n- Run this 15-30 minutes before the meeting\n- Create person pages for new contacts after meetings\n- Update this context regularly for accurate prep\n","Prepare for an upcoming meeting by gathering context on attendees and related topics.\n\n## Tone Calibration\n\nBefore executing this command, read `System\u002Fuser-profile.yaml` → `communication` section and adapt:\n\n**Career Level Adaptations:**\n- **Junior:** Provide more context about attendees, suggest preparation tips\n- **Mid:** Balance context with action, suggest talking points\n- **Senior\u002FLeadership:** Strategic framing, influence opportunities, key decisions\n- **C-Suite:** High-level strategic context, organizational implications, key stakeholders\n\n**Directness:**\n- **Very direct:** Bullet points, key facts only\n- **Balanced:** Context + talking points (default)\n- **Supportive:** Detailed prep, conversation strategies\n\n**Detail Level:**\n- **Concise:** Names, roles, top 3 talking points\n- **Balanced:** Standard prep format\n- **Comprehensive:** Full context, relationship dynamics, strategic considerations\n\nSee CLAUDE.md → \"Communication Adaptation\" for full guidelines.\n\n---\n\n## Arguments\n\n**Optional:** $MEETING, $ATTENDEES\n\nIf not provided, prompt the user for:\n1. Meeting topic or title\n2. List of attendees (comma-separated names)\n\n**Examples:**\n- `\u002Fmeeting-prep \"Q1 Planning\" \"Sarah Chen, Mike Rodriguez\"`\n- `\u002Fmeeting-prep` (then prompt for details)\n\n## What This Does\n\n1. Looks up each attendee in `People\u002F` folder\n2. Surfaces recent interactions and open action items\n3. Checks for related projects\n4. Suggests talking points based on context\n\n## Process\n\n### Step 0: Gather Context (if needed)\n\n**If $MEETING or $ATTENDEES are not provided:**\n\nAsk: \"Which meeting are you prepping for?\"\n- Get meeting topic\u002Ftitle\n\nAsk: \"Who's attending? (comma-separated names or just list them)\"\n- Accept formats: \"Sarah Chen, Mike Rodriguez\" or \"Sarah, Mike\" or natural list\n- Parse into individual attendee names\n\n### Step 1: Attendee Lookup\n\nFor each attendee in $ATTENDEES:\n\n1. Search `05-Areas\u002FPeople\u002FInternal\u002F` and `05-Areas\u002FPeople\u002FExternal\u002F` for matching names\n2. If found, extract:\n   - Role and company\n   - Last interaction date\n   - Open action items involving them\n   - Key context or notes\n\n3. If not found, note: \"No person page for [Name] - consider creating one after the meeting\"\n\n#### Context Enrichment Note\n\nAfter completing attendee lookup, if any attendees are missing person pages or have sparse pages (no role, no recent interactions, no notes), add this hint to the prep output:\n\n> ? I don't have much context on [attendee name(s)]. After the meeting, run `\u002Fprocess-meetings` to build their profile, or create a person page at `05-Areas\u002FPeople\u002F`.\n\nOnly show this for attendees WITHOUT existing person pages or with very sparse pages. Don't show for attendees who already have rich person pages. This hint is informational and does not block meeting prep.\n\n### Step 2: Related Projects\n\nSearch `04-Projects\u002F` for any projects that:\n- Mention the attendees\n- Relate to the meeting topic ($MEETING)\n\nExtract:\n- Project name and status\n- Relevant milestones or blockers\n- Recent updates\n\n### Step 3: Recent Context\n\nSearch `00-Inbox\u002FMeetings\u002F` for recent meetings with these attendees:\n- What was discussed?\n- What was decided?\n- What follow-ups were committed?\n\n### Step 3a: Semantic Context Enrichment (if QMD available)\n\n**This step runs automatically when QMD is installed.** It enriches meeting prep with semantically related vault content that keyword search would miss.\n\nCheck if QMD MCP tools are available by calling `qmd_status`. **If available:**\n\n1. **Semantic search for meeting topic:**\n   ```\n   qmd_search(query=\"$MEETING\", limit=5)\n   ```\n   Look for: related past discussions, relevant decisions, thematic connections — content that shares meaning with the meeting topic but uses different words.\n\n2. **Semantic search for each attendee (beyond their person page):**\n   ```\n   qmd_search(query=\"$ATTENDEE_NAME context discussions decisions\", limit=3)\n   ```\n   Look for: contextual references where this person is mentioned by role\u002Ftitle\u002Fteam (e.g., \"the VP of Sales asked about...\"), not just by name.\n\n3. **Cross-reference results** with what Steps 1-3 already found. **Only surface NEW insights** — content that the keyword-based person page lookup and meeting folder grep in earlier steps missed.\n\n**Add to the prep brief under a \"Semantic Connections\" heading:**\n- Past discussions thematically related to this meeting (even if different keywords were used)\n- Decisions made in adjacent contexts that are relevant here\n- Commitments or open items discovered through semantic matching\n- Related projects or goals that connect by meaning\n\n**If QMD is not available:** Skip this step silently. Steps 1-3 provide the standard keyword-based context.\n\n---\n\n### Step 3b: Integration Context (if available)\n\nCheck `System\u002Fintegrations\u002Fconfig.yaml` to see which integrations are enabled.\n\n**Notion Integration:**\nIf `enabled.notion: true` AND Notion MCP is available:\n```\nSearch Notion for pages related to:\n- Meeting topic ($MEETING)\n- Attendee names\n\nInclude in prep:\n- Relevant Notion docs (title + summary)\n- Shared pages with attendees\n```\n\n**Slack Integration:**\nIf `enabled.slack: true` AND Slack MCP is available:\n```\nSearch Slack for recent conversations:\n- With\u002Fabout each attendee\n- Mentioning the meeting topic\n\nInclude in prep:\n- Recent Slack context (last 7 days)\n- Key threads or decisions\n- Any commitments made\n```\n\n**Teams Integration:**\nIf `teams.enabled: true` AND Teams MCP available:\n```\nSearch Teams chats with attendees:\n- Recent 1:1 and group chats involving each attendee\n- Mentioning the meeting topic\n\nCheck Teams channels related to meeting topic:\n- Project channels, department channels\n- Recent posts and replies\n\nSurface recent decisions from Teams threads:\n- Key decisions made in channel conversations\n- Any commitments or follow-ups from Teams chats\n\nInclude in prep:\n- Recent Teams context (last 7 days)\n- Key threads or decisions from channels\n- Any commitments made in Teams chats\n```\n\n**When BOTH Slack and Teams are enabled:**\n- Check both sources for each attendee\n- Label context by source: \"**From Slack:**\" \u002F \"**From Teams:**\"\n- Deduplicate if the same person appears in both (merge context, label the source)\n- Present in separate sub-sections under Integration Context\n\n**Google Workspace Integration:**\nIf `google-workspace.enabled: true` AND Google Workspace MCP is available:\n```\nSearch Gmail for recent threads with each attendee (last 7 days):\n- Email exchanges and their topics\n- Shared Google Docs mentioned in threads\n- Outstanding email requests (sent but no reply)\n\nSearch for Google Docs related to:\n- Meeting topic ($MEETING)\n- Shared documents with attendees\n\nInclude in prep:\n- Recent email exchanges (last 7 days) — key threads summarized\n- Shared documents — Google Docs, Sheets, or Slides linked in emails\n- Outstanding requests\u002Ffollow-ups — emails waiting > 48h for reply\n```\n\n**Graceful Degradation:**\nIf an integration is enabled but the MCP isn't responding:\n- Skip silently\n- Don't show error to user\n- Continue with vault-only context\n\n### Step 4: Compile Prep Brief\n\n## Output Format\n\n```markdown\n# Meeting Prep: $MEETING\n\n**Date:** [Today's date]\n**Attendees:** $ATTENDEES\n\n---\n\n---\n\n## Demo Mode Check\n\nBefore executing, check if demo mode is active:\n\n1. Read `System\u002Fuser-profile.yaml` and check `demo_mode`\n2. **If `demo_mode: true`:**\n   - Display: \"Demo Mode Active — Using sample data\"\n   - Use `System\u002FDemo\u002F` paths instead of root paths\n   - Write any output to `System\u002FDemo\u002F` subdirectories\n3. **If `demo_mode: false`:** Use normal vault paths\n\n\n## People Context\n\n### [Attendee Name]\n- **Role:** [Role at Company]\n- **Last Interaction:** [Date] - [Topic]\n- **Open Items:**\n  - [ ] [Action item]\n- **Notes:** [Key context about this person]\n\n### [Next Attendee]\n...\n\n---\n\n## Related Projects\n\n| Project | Status | Relevance |\n|---------|--------|-----------|\n| [Name]  | [Status] | [Why it relates] |\n\n---\n\n## Recent History\n\nPrevious meetings with these attendees:\n\n| Date | Topic | Key Outcomes |\n|------|-------|--------------|\n| [Date] | [Topic] | [What was decided\u002Fdiscussed] |\n\n---\n\n## Integration Context (if available)\n\n*This section appears when productivity integrations are enabled.*\n\n### From Slack\n> Recent conversation context with attendees (last 7 days)\n\n### From Teams\n> Recent Teams chats and channel threads with attendees (last 7 days)\n\n### From Notion\n> Related Notion docs: [Doc title](link)\n\n### From Gmail\n> Email threads with [Attendee]: [Summary of outstanding requests]\n\n---\n\n## Suggested Talking Points\n\nBased on the context above:\n\n1. **Follow up on:** [Open item from last meeting]\n2. **Discuss:** [Project-related topic]\n3. **Ask about:** [Something from their context]\n\n---\n\n## Questions to Consider\n\n- What's your main goal for this meeting?\n- What do you need from these attendees?\n- What decisions need to be made?\n\n---\n\n## Post-Meeting\n\nAfter the meeting:\n1. Add notes to `00-Inbox\u002FMeetings\u002FYYYY-MM-DD - [Topic].md`\n2. Update person pages with new context\n3. Create tasks for any action items\n```\n\n---\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark meeting prep as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `meeting_prep_completed` and properties:\n- `attendees_count`: number of attendees\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## When to Use\n\n- Before any meeting with multiple attendees\n- When meeting someone you haven't seen in a while\n- Before important meetings where you want full context\n\n## Tips\n\n- Run this 15-30 minutes before the meeting\n- Create person pages for new contacts after meetings\n- Update this context regularly for accurate prep\n",{"name":5,"context":33,"description":7},"fork","main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Fmeeting-prep",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill meeting-prep",{"tool":49,"command":50},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill meeting-prep",{"tool":52,"command":53},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill meeting-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmeeting-prep\u002FSKILL.md",true,[57,63,67,71,75],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fimaging-migration.md","REFERENCE","参考文档",11017,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FPowerToys\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwpf-to-winui3-migration\u002Freferences\u002Fimaging-migration.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fnamespace-api-mapping.md",15868,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FPowerToys\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwpf-to-winui3-migration\u002Freferences\u002Fnamespace-api-mapping.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fpowertoys-patterns.md",17947,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FPowerToys\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwpf-to-winui3-migration\u002Freferences\u002Fpowertoys-patterns.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fthreading-and-windowing.md",11923,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FPowerToys\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwpf-to-winui3-migration\u002Freferences\u002Fthreading-and-windowing.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fxaml-migration.md",27373,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FPowerToys\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwpf-to-winui3-migration\u002Freferences\u002Fxaml-migration.md",[80,111,120,134,149,161],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":92,"publishedAt":28},"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",[86,91],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95,96,97,98,99,100,101,102,103,26,27,104,105,106,107,108,109,110],"zoom setup","setup","schedule","MCP","review","connect","transcript","search","stats","oauth2","confirmation","process","recordings","surfaces","scheduling","granola","time","distribution",{"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":28},"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",[],[113,118,119],"learn","just",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":28},"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",[126],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[128,97,129,130,131,132,133],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":28},"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",[],[141,142,143,144,145,146,147,148],"week plan","plan","calendar","SET","shape","goals","task","priorities",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":28},"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",[],[151,156,157,158,159,160],"tasks","fast","extract","files","route",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":171,"publishedAt":28},"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",[167,170],{"categoryNo":168,"categoryName":169,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[172,173,94,174,98,96,175,147,176,177,178,179,180],"trello","trello setup","sync","token","kanban","bun","visual","api","server"]