Diagnose Windows App (Microsoft Remote Desktop / Azure Virtual Desktop / W365) connection quality issues on macOS. Analyze transport protocol selection (UDP Shortpath vs WebSocket), detect VPN/proxy interference with STUN/TURN 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.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/claude-code-skills --skill windows-remote-desktop-connection-doctor93
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms covering both product names and user-facing symptoms, explicit 'when to use' guidance, and targets a highly specific technical niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Diagnose connection quality issues', 'Analyze transport protocol selection (UDP Shortpath vs WebSocket)', 'detect VPN/proxy interference with STUN/TURN negotiation', and 'parse Windows App logs for Shortpath failures'. | 3 / 3 |
Completeness | Clearly answers both what (diagnose connection issues, analyze protocols, detect interference, parse logs) AND when with explicit triggers ('when VDI connections are slow, when transport shows WebSocket instead of UDP, when RDP Shortpath fails to establish, or when RTT is unexpectedly high'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Windows App', 'Microsoft Remote Desktop', 'Azure Virtual Desktop', 'W365', 'VDI connections', 'UDP', 'WebSocket', 'RDP Shortpath', 'RTT', 'slow', 'macOS'. Includes both product names and technical symptoms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting a specific platform (macOS), specific applications (Windows App/Remote Desktop/AVD/W365), and specific technical domain (transport protocol diagnostics). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality diagnostic skill with excellent actionability and workflow clarity. The step-by-step process with evidence-based root cause categories and verification steps is well-designed. Minor verbosity in the background section and some explanatory content could be trimmed to improve token efficiency.
Suggestions
Trim the Background section - Claude understands transport protocol priorities; a single line stating 'UDP Shortpath preferred, WebSocket fallback adds latency' suffices
Remove explanatory phrases like 'This is the most critical step' and 'valuable even when Tailscale is not the problem' - let the structure speak for itself
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but includes some explanatory content Claude likely knows (e.g., explaining what UDP Shortpath provides, basic transport priority). The Background section could be trimmed. | 2 / 3 |
Actionability | Excellent executable guidance throughout with copy-paste ready bash commands, specific log paths, grep patterns, and even a Python STUN test script. Each diagnostic step has concrete commands to run. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation checkpoints (Step 5: Verify Fix), decision points based on evidence categories (A-D), and feedback loops (compare working vs broken logs, verify after fix). The 'If X, proceed to Step Y' structure is well-defined. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview in main file and appropriate references to detailed materials (windows_app_log_analysis.md, avd_transport_protocols.md). References are one level deep and clearly signaled with descriptive text. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.