[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F3REP90QR70CBWN8Q8S8S4":3,"skill-same:01M6F3REP90QR70CBWN8Q8S8S4":73},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6F3REP90QR70CBWN8Q8S8S4","windows-remote-desktop-connection-doctor",null,"Diagnose Windows App (Microsoft Remote Desktop \u002F Azure Virtual Desktop \u002F W365) connection quality issues on macOS. Analyze transport protocol selection (UDP Shortpath vs WebSocket), detect VPN\u002Fproxy interference with STUN\u002FTURN negotiation, and parse Windows App logs for Shortpath failures. This skill should be used when VDI connections are slow, when transport shows WebSocket instead of UDP, when RDP Shortpath fails to establish, or when RTT is unexpectedly high.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fdaymade\u002Fclaude-code-skills\u002Fwindows-remote-desktop-connection-doctor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"windows","connection","remote","windows remote desktop connection doctor","doctor","desktop","issues","proxy","logs","rdp","websocket","Bash","analyze","virtual","read","selection","vpn","app","diagnose","macos","2026-11-10 10:12:30",false,"---\nname: windows-remote-desktop-connection-doctor\ndescription: Diagnose Windows App (Microsoft Remote Desktop \u002F Azure Virtual Desktop \u002F W365) connection quality issues on macOS. Analyze transport protocol selection (UDP Shortpath vs WebSocket), detect VPN\u002Fproxy interference with STUN\u002FTURN negotiation, and parse Windows App logs for Shortpath failures. This skill should be used when VDI connections are slow, when transport shows WebSocket instead of UDP, when RDP Shortpath fails to establish, or when RTT is unexpectedly high.\nallowed-tools: Read, Grep, Bash\n---\n\n# Windows Remote Desktop Connection Doctor\n\nDiagnose and fix Windows App (AVD\u002FWVD\u002FW365) connection quality issues on macOS, with focus on transport protocol optimization.\n\n## Background\n\nAzure Virtual Desktop transport priority: **UDP Shortpath > TCP > WebSocket**. UDP Shortpath provides the best experience (lowest latency, supports UDP Multicast). When it fails, the client falls back to WebSocket over TCP 443 through the gateway, adding significant latency overhead.\n\n## Diagnostic Workflow\n\n### Step 1: Collect Connection Info\n\nAsk the user to provide the Connection Info from Windows App (click the signal icon in the toolbar). Key fields to extract:\n\n| Field | What It Tells |\n|-------|--------------|\n| Transport Protocol | Current transport: `UDP`, `UDP Multicast`, `WebSocket`, or `TCP` |\n| Round-Trip Time (RTT) | End-to-end latency in ms |\n| Available Bandwidth | Current bandwidth in Mbps |\n| Gateway | The AVD gateway hostname and port |\n| Service Region | Azure region code (e.g., SEAS = South East Asia) |\n\nIf Transport Protocol is `UDP` or `UDP Multicast`, the connection is optimal — no further diagnosis needed.\n\nIf Transport Protocol is `WebSocket` or `TCP`, proceed to Step 2.\n\n### Step 2: Collect Network Evidence\n\nGather evidence in parallel — do NOT make assumptions. Run the following checks simultaneously:\n\n#### 2A: Network Interfaces and Routing\n\n```bash\nifconfig | grep -E \"^[a-z]|inet |utun\"\nnetstat -rn | head -40\nscutil --proxy\n```\n\nLook for:\n- **utun interfaces**: Identify VPN\u002Fproxy TUN tunnels (ShadowRocket, Clash, Tailscale)\n- **Default route priority**: Which interface handles default traffic\n- **Split routing**: `0\u002F1 + 128.0\u002F1 → utun` pattern means a VPN captures all traffic\n- **System proxy**: HTTP\u002FHTTPS proxy enabled on localhost ports\n\n#### 2B: RDP Client Process and Connections\n\n```bash\n# Find the Windows App process (NOT \"msrdc\" — the new client uses \"Windows\" as process name)\nps aux | grep -i -E 'msrdc|Windows' | grep -v grep\n# Check its network connections\nlsof -i -n -P 2>\u002Fdev\u002Fnull | grep -i \"Windows\" | head -20\n# Check for UDP connections\nlsof -i UDP -n -P 2>\u002Fdev\u002Fnull | head -30\n```\n\nKey evidence to look for:\n- **Source IP `198.18.0.x`**: Traffic is being routed through ShadowRocket\u002Fproxy TUN tunnel\n- **No UDP connections from Windows process**: Shortpath not established\n- **Only TCP 443**: Fallback to gateway WebSocket transport\n\n#### 2C: VPN\u002FProxy State\n\n```bash\n# Environment proxy variables\nenv | grep -i proxy\n# System proxy via scutil\nscutil --proxy\n# ShadowRocket config API (if accessible on local network)\nNO_PROXY=\"\u003Clocal-ip>\" curl -s --connect-timeout 5 \"http:\u002F\u002F\u003Clocal-ip>:8080\u002Fapi\u002Fread\"\n```\n\n#### 2D: Tailscale State (if running)\n\n```bash\ntailscale status\ntailscale netcheck\n```\n\nThe `netcheck` output reveals NAT type (`MappingVariesByDestIP`), UDP support, and public IP — valuable even when Tailscale is not the problem.\n\n### Step 3: Analyze Windows App Logs\n\nThis is the most critical step. Windows App logs contain transport negotiation details that no network-level test can reveal.\n\n**Log location on macOS:**\n```\n~\u002FLibrary\u002FContainers\u002Fcom.microsoft.rdc.macos\u002FData\u002FLibrary\u002FLogs\u002FWindows App\u002F\n```\n\nFiles are named: `com.microsoft.rdc.macos_v\u003Cversion>_\u003Cdate>_\u003Ctime>.log`\n\nSee [references\u002Fwindows_app_log_analysis.md](references\u002Fwindows_app_log_analysis.md) for detailed log parsing guidance.\n\n#### Quick Log Search\n\n```bash\nLOG_DIR=~\u002FLibrary\u002FContainers\u002Fcom.microsoft.rdc.macos\u002FData\u002FLibrary\u002FLogs\u002FWindows\\ App\n# Find the most recent log\nLATEST_LOG=$(ls -t \"$LOG_DIR\"\u002F*.log 2>\u002Fdev\u002Fnull | head -1)\n\n# Search for transport-critical entries (filter out noise)\ngrep -i -E \"STUN|TURN|VPN|Routed|Shortpath|FetchClient|clientoption|GATEWAY.*ERR|Certificate.*valid|InternetConnectivity|Passed URL\" \"$LATEST_LOG\" | grep -v \"BasicStateManagement\\|DynVC\\|dynvcstat\\|asynctransport\"\n```\n\n#### Key Log Patterns\n\n| Log Pattern | Meaning |\n|-------------|---------|\n| `Passed: InternetConnectivity` | Health check completed successfully |\n| `TCP\u002FIP Traffic Routed Through VPN: No\u002FYes` | Client detected VPN routing for TCP |\n| `STUN\u002FTURN Traffic Routed Through VPN: Yes` | Client detected VPN routing for STUN\u002FTURN |\n| `Passed URL: https:\u002F\u002F...wvd.microsoft.com\u002F Response Time: Nms` | Gateway reachability confirmed |\n| `FetchClientOptions exception: Request timed out` | **Critical**: Client cannot get transport options from gateway |\n| `Certificate validation failed` | TLS interception or DNS poisoning detected |\n| `OnRDWebRTCRedirectorRpc rtcSession not handled` | WebRTC session setup not handled by client |\n\n#### Compare Working vs Broken Logs\n\nWhen possible, compare a log from when the connection worked (UDP) with the current log:\n\n```bash\n# Compare startup health check blocks\nfor f in \"$LOG_DIR\"\u002F*.log; do\n  echo \"=== $(basename \"$f\") ===\"\n  grep -E \"InternetConnectivity|Routed Through VPN|Passed URL|FetchClient\" \"$f\" | head -10\n  echo \"\"\ndone\n```\n\nA working log will contain the full health check block (InternetConnectivity, VPN routing detection, gateway URL tests). A broken log may show these entries missing entirely, or show certificate\u002Ftimeout errors instead.\n\n### Step 4: Determine Root Cause\n\nBased on collected evidence, identify the root cause category:\n\n#### Category A: VPN\u002FProxy Interference\n\n**Evidence**: Windows App source IP is `198.18.0.x`, STUN\u002FTURN routed through VPN, no UDP connections.\n\n**Fix**: Add DIRECT rules for AVD traffic in the proxy tool:\n```\nDOMAIN-SUFFIX,wvd.microsoft.com,DIRECT\nDOMAIN-SUFFIX,microsoft.com,DIRECT\nIP-CIDR,13.104.0.0\u002F14,DIRECT\n```\n\n**Verify**: Temporarily disable VPN\u002Fproxy, reconnect VDI, check if transport changes to UDP.\n\n#### Category B: ISP\u002FNetwork UDP Restriction\n\n**Evidence**: Even with all VPNs off, still WebSocket. No UDP connections. `FetchClientOptions` timeout.\n\n**Verify**:\n```bash\n# Test STUN connectivity to a known server\npython3 -c \"\nimport socket, struct, os\nheader = struct.pack('!HHI', 0x0001, 0, 0x2112A442) + os.urandom(12)\nfor srv in [('stun.l.google.com', 19302), ('stun1.l.google.com', 19302)]:\n    try:\n        s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)\n        s.settimeout(3)\n        s.sendto(header, srv)\n        data, addr = s.recvfrom(1024)\n        print(f'STUN from {srv[0]}: OK')\n        s.close(); break\n    except: print(f'STUN from {srv[0]}: FAILED'); s.close()\n\"\n```\n\n**Fix options**:\n- Try mobile hotspot (isolate home network from ISP)\n- Check router NAT type (Full Cone NAT preferred)\n- Enable UPnP on router\n- Try IPv6 if available\n- Contact ISP about UDP restrictions\n\n#### Category C: Client Health Check Failure\n\n**Evidence**: Log shows certificate validation errors at startup, health check block (InternetConnectivity, STUN\u002FTURN detection) missing from log, `FetchClientOptions` timeout.\n\nThis means the client cannot complete its diagnostic\u002Fcapability discovery, preventing Shortpath negotiation.\n\n**Possible causes**:\n- ISP HTTPS interception\u002FMITM (especially in China)\n- DNS poisoning returning incorrect IPs for Microsoft diagnostic endpoints\n- Firewall blocking Microsoft telemetry endpoints\n\n**Fix options**:\n- Change DNS to 8.8.8.8 or 1.1.1.1 (bypass ISP DNS)\n- Route Microsoft traffic through a clean proxy\n- Check if ISP injects certificates\n\n#### Category D: Server-Side Shortpath Not Enabled\n\n**Evidence**: Log shows no STUN\u002FTURN or Shortpath related entries at all (not even detection), but health checks pass and no errors.\n\nThis means the AVD host pool does not have RDP Shortpath enabled. This requires admin action on the Azure portal.\n\n### Step 5: Verify Fix\n\nAfter applying a fix, reconnect the VDI session and verify:\n\n1. Check Connection Info — Transport Protocol should show `UDP` or `UDP Multicast`\n2. RTT should drop significantly (e.g., from 165ms to 40-60ms)\n3. Verify with lsof:\n```bash\nlsof -i UDP -n -P 2>\u002Fdev\u002Fnull | grep -i \"Windows\"\n# Should show UDP connections if Shortpath is active\n```\n\n## References\n\n- [references\u002Fwindows_app_log_analysis.md](references\u002Fwindows_app_log_analysis.md) — Detailed log parsing patterns, error signatures, and comparison methodology\n- [references\u002Favd_transport_protocols.md](references\u002Favd_transport_protocols.md) — How AVD transport selection works, STUN\u002FTURN\u002FICE overview, Shortpath architecture\n\n","# Windows Remote Desktop Connection Doctor\n\nDiagnose and fix Windows App (AVD\u002FWVD\u002FW365) connection quality issues on macOS, with focus on transport protocol optimization.\n\n## Background\n\nAzure Virtual Desktop transport priority: **UDP Shortpath > TCP > WebSocket**. UDP Shortpath provides the best experience (lowest latency, supports UDP Multicast). When it fails, the client falls back to WebSocket over TCP 443 through the gateway, adding significant latency overhead.\n\n## Diagnostic Workflow\n\n### Step 1: Collect Connection Info\n\nAsk the user to provide the Connection Info from Windows App (click the signal icon in the toolbar). Key fields to extract:\n\n| Field | What It Tells |\n|-------|--------------|\n| Transport Protocol | Current transport: `UDP`, `UDP Multicast`, `WebSocket`, or `TCP` |\n| Round-Trip Time (RTT) | End-to-end latency in ms |\n| Available Bandwidth | Current bandwidth in Mbps |\n| Gateway | The AVD gateway hostname and port |\n| Service Region | Azure region code (e.g., SEAS = South East Asia) |\n\nIf Transport Protocol is `UDP` or `UDP Multicast`, the connection is optimal — no further diagnosis needed.\n\nIf Transport Protocol is `WebSocket` or `TCP`, proceed to Step 2.\n\n### Step 2: Collect Network Evidence\n\nGather evidence in parallel — do NOT make assumptions. Run the following checks simultaneously:\n\n#### 2A: Network Interfaces and Routing\n\n```bash\nifconfig | grep -E \"^[a-z]|inet |utun\"\nnetstat -rn | head -40\nscutil --proxy\n```\n\nLook for:\n- **utun interfaces**: Identify VPN\u002Fproxy TUN tunnels (ShadowRocket, Clash, Tailscale)\n- **Default route priority**: Which interface handles default traffic\n- **Split routing**: `0\u002F1 + 128.0\u002F1 → utun` pattern means a VPN captures all traffic\n- **System proxy**: HTTP\u002FHTTPS proxy enabled on localhost ports\n\n#### 2B: RDP Client Process and Connections\n\n```bash\n# Find the Windows App process (NOT \"msrdc\" — the new client uses \"Windows\" as process name)\nps aux | grep -i -E 'msrdc|Windows' | grep -v grep\n# Check its network connections\nlsof -i -n -P 2>\u002Fdev\u002Fnull | grep -i \"Windows\" | head -20\n# Check for UDP connections\nlsof -i UDP -n -P 2>\u002Fdev\u002Fnull | head -30\n```\n\nKey evidence to look for:\n- **Source IP `198.18.0.x`**: Traffic is being routed through ShadowRocket\u002Fproxy TUN tunnel\n- **No UDP connections from Windows process**: Shortpath not established\n- **Only TCP 443**: Fallback to gateway WebSocket transport\n\n#### 2C: VPN\u002FProxy State\n\n```bash\n# Environment proxy variables\nenv | grep -i proxy\n# System proxy via scutil\nscutil --proxy\n# ShadowRocket config API (if accessible on local network)\nNO_PROXY=\"\u003Clocal-ip>\" curl -s --connect-timeout 5 \"http:\u002F\u002F\u003Clocal-ip>:8080\u002Fapi\u002Fread\"\n```\n\n#### 2D: Tailscale State (if running)\n\n```bash\ntailscale status\ntailscale netcheck\n```\n\nThe `netcheck` output reveals NAT type (`MappingVariesByDestIP`), UDP support, and public IP — valuable even when Tailscale is not the problem.\n\n### Step 3: Analyze Windows App Logs\n\nThis is the most critical step. Windows App logs contain transport negotiation details that no network-level test can reveal.\n\n**Log location on macOS:**\n```\n~\u002FLibrary\u002FContainers\u002Fcom.microsoft.rdc.macos\u002FData\u002FLibrary\u002FLogs\u002FWindows App\u002F\n```\n\nFiles are named: `com.microsoft.rdc.macos_v\u003Cversion>_\u003Cdate>_\u003Ctime>.log`\n\nSee [references\u002Fwindows_app_log_analysis.md](references\u002Fwindows_app_log_analysis.md) for detailed log parsing guidance.\n\n#### Quick Log Search\n\n```bash\nLOG_DIR=~\u002FLibrary\u002FContainers\u002Fcom.microsoft.rdc.macos\u002FData\u002FLibrary\u002FLogs\u002FWindows\\ App\n# Find the most recent log\nLATEST_LOG=$(ls -t \"$LOG_DIR\"\u002F*.log 2>\u002Fdev\u002Fnull | head -1)\n\n# Search for transport-critical entries (filter out noise)\ngrep -i -E \"STUN|TURN|VPN|Routed|Shortpath|FetchClient|clientoption|GATEWAY.*ERR|Certificate.*valid|InternetConnectivity|Passed URL\" \"$LATEST_LOG\" | grep -v \"BasicStateManagement\\|DynVC\\|dynvcstat\\|asynctransport\"\n```\n\n#### Key Log Patterns\n\n| Log Pattern | Meaning |\n|-------------|---------|\n| `Passed: InternetConnectivity` | Health check completed successfully |\n| `TCP\u002FIP Traffic Routed Through VPN: No\u002FYes` | Client detected VPN routing for TCP |\n| `STUN\u002FTURN Traffic Routed Through VPN: Yes` | Client detected VPN routing for STUN\u002FTURN |\n| `Passed URL: https:\u002F\u002F...wvd.microsoft.com\u002F Response Time: Nms` | Gateway reachability confirmed |\n| `FetchClientOptions exception: Request timed out` | **Critical**: Client cannot get transport options from gateway |\n| `Certificate validation failed` | TLS interception or DNS poisoning detected |\n| `OnRDWebRTCRedirectorRpc rtcSession not handled` | WebRTC session setup not handled by client |\n\n#### Compare Working vs Broken Logs\n\nWhen possible, compare a log from when the connection worked (UDP) with the current log:\n\n```bash\n# Compare startup health check blocks\nfor f in \"$LOG_DIR\"\u002F*.log; do\n  echo \"=== $(basename \"$f\") ===\"\n  grep -E \"InternetConnectivity|Routed Through VPN|Passed URL|FetchClient\" \"$f\" | head -10\n  echo \"\"\ndone\n```\n\nA working log will contain the full health check block (InternetConnectivity, VPN routing detection, gateway URL tests). A broken log may show these entries missing entirely, or show certificate\u002Ftimeout errors instead.\n\n### Step 4: Determine Root Cause\n\nBased on collected evidence, identify the root cause category:\n\n#### Category A: VPN\u002FProxy Interference\n\n**Evidence**: Windows App source IP is `198.18.0.x`, STUN\u002FTURN routed through VPN, no UDP connections.\n\n**Fix**: Add DIRECT rules for AVD traffic in the proxy tool:\n```\nDOMAIN-SUFFIX,wvd.microsoft.com,DIRECT\nDOMAIN-SUFFIX,microsoft.com,DIRECT\nIP-CIDR,13.104.0.0\u002F14,DIRECT\n```\n\n**Verify**: Temporarily disable VPN\u002Fproxy, reconnect VDI, check if transport changes to UDP.\n\n#### Category B: ISP\u002FNetwork UDP Restriction\n\n**Evidence**: Even with all VPNs off, still WebSocket. No UDP connections. `FetchClientOptions` timeout.\n\n**Verify**:\n```bash\n# Test STUN connectivity to a known server\npython3 -c \"\nimport socket, struct, os\nheader = struct.pack('!HHI', 0x0001, 0, 0x2112A442) + os.urandom(12)\nfor srv in [('stun.l.google.com', 19302), ('stun1.l.google.com', 19302)]:\n    try:\n        s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)\n        s.settimeout(3)\n        s.sendto(header, srv)\n        data, addr = s.recvfrom(1024)\n        print(f'STUN from {srv[0]}: OK')\n        s.close(); break\n    except: print(f'STUN from {srv[0]}: FAILED'); s.close()\n\"\n```\n\n**Fix options**:\n- Try mobile hotspot (isolate home network from ISP)\n- Check router NAT type (Full Cone NAT preferred)\n- Enable UPnP on router\n- Try IPv6 if available\n- Contact ISP about UDP restrictions\n\n#### Category C: Client Health Check Failure\n\n**Evidence**: Log shows certificate validation errors at startup, health check block (InternetConnectivity, STUN\u002FTURN detection) missing from log, `FetchClientOptions` timeout.\n\nThis means the client cannot complete its diagnostic\u002Fcapability discovery, preventing Shortpath negotiation.\n\n**Possible causes**:\n- ISP HTTPS interception\u002FMITM (especially in China)\n- DNS poisoning returning incorrect IPs for Microsoft diagnostic endpoints\n- Firewall blocking Microsoft telemetry endpoints\n\n**Fix options**:\n- Change DNS to 8.8.8.8 or 1.1.1.1 (bypass ISP DNS)\n- Route Microsoft traffic through a clean proxy\n- Check if ISP injects certificates\n\n#### Category D: Server-Side Shortpath Not Enabled\n\n**Evidence**: Log shows no STUN\u002FTURN or Shortpath related entries at all (not even detection), but health checks pass and no errors.\n\nThis means the AVD host pool does not have RDP Shortpath enabled. This requires admin action on the Azure portal.\n\n### Step 5: Verify Fix\n\nAfter applying a fix, reconnect the VDI session and verify:\n\n1. Check Connection Info — Transport Protocol should show `UDP` or `UDP Multicast`\n2. RTT should drop significantly (e.g., from 165ms to 40-60ms)\n3. Verify with lsof:\n```bash\nlsof -i UDP -n -P 2>\u002Fdev\u002Fnull | grep -i \"Windows\"\n# Should show UDP connections if Shortpath is active\n```\n\n## References\n\n- [references\u002Fwindows_app_log_analysis.md](references\u002Fwindows_app_log_analysis.md) — Detailed log parsing patterns, error signatures, and comparison methodology\n- [references\u002Favd_transport_protocols.md](references\u002Favd_transport_protocols.md) — How AVD transport selection works, STUN\u002FTURN\u002FICE overview, Shortpath architecture\n\n",{"name":5,"description":7,"allowed-tools":49},"Read, Grep, Bash","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fdaymade\u002Fclaude-code-skills\u002Fwindows-remote-desktop-connection-doctor",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill windows-remote-desktop-connection-doctor",{"tool":65,"command":66},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill windows-remote-desktop-connection-doctor",{"tool":68,"command":69},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill windows-remote-desktop-connection-doctor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fdaymade\u002Fclaude-code-skills\u002Fwindows-remote-desktop-connection-doctor\u002FSKILL.md",true,[],[74,84,94,103,108,115],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":80,"publishedAt":44},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[79],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[81,82,83],"model","model hierarchy","model hierarchy skill",{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":90,"publishedAt":44},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[89],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[91,92,93],"MCP","zoom","zoom mcp",{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":44},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[100,101,102,92],"sdk","zoom apps sdk","apps",{"skillNo":104,"name":24,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":44},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[24],{"skillNo":109,"name":110,"nameZh":6,"description":6,"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":114,"publishedAt":44},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[113],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[110],{"skillNo":116,"name":117,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":44},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[117]]