skills.rest
UniClipboard
UniClipboardOFFICIAL
Explore all skills by this author →
GitHub

cross-device-diagnose

Diagnose cross-device sync and transfer issues through structured hypothesis testing and falsification.

1.6k|73|Updated Mar 13, 2025
Search Tags:#cross-device#ssh#Debugging#hypothesis-testing#clipboard#network-diagnosis#Sync
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill cross-device-diagnose
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-device-diagnose
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.agents/skills/cross-device-diagnose
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill cross-device-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-device debugging often wastes time chasing code bugs when the real cause is environmental (proxies, VPNs, relay paths), and debug context gets lost between sessions. This Skill enforces a disciplined diagnostic loop that collects environment fingerprints from both machines first, matches against known issue patterns, and forces falsification before declaring a root cause.

Core Features & Use Cases

  • Dual-Machine Environment Fingerprinting: Collects network interfaces, proxy/VPN status (Clash TUN, Tailscale), and daemon state from both Mac and Windows (via SSH) before any log analysis.
  • Hypothesis Management with Forced Falsification: Registers all plausible hypotheses ranked by prior probability, records evidence in a ledger, and requires at least one attempt to disprove a hypothesis before confirming it.
  • Memory Pattern Matching & Session Persistence: Checks a memory index for known issue patterns (e.g., TUN proxy breaking LAN sync) and persists debug state via $wrap so the next session resumes instead of restarting.
  • Use Case: A user reports "Mac sent but Windows didn't receive" or slow LAN sync. The Skill fingerprints both machines, detects Clash TUN active on both sides, matches the known TUN-proxy memory pattern, and confirms the root cause by having the user disable Clash and retest.

Quick Start

Ask the agent to run /cross-device-diagnose to investigate why clipboard sync between your Mac and Windows machine is slow or failing.

Frequently Asked Questions about cross-device-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose clipboard sync issues between two devices?▼

Start by collecting environment fingerprints from both machines, including network interfaces, proxy or VPN processes, and daemon status, before reading any logs. Then register ranked hypotheses, gather log evidence, and attempt to falsify the leading hypothesis before declaring a root cause.

Why is LAN sync slow when both devices are on the same network?▼

A common cause is a TUN-mode proxy such as Clash hijacking UDP traffic, which breaks direct peer-to-peer connections and forces traffic onto relay or Tailscale paths. Check for a 198.18.0.1 gateway or 100.x addresses in connection logs to confirm.

How do I collect logs from a Windows machine during debugging?▼

Use SSH to run commands on the Windows host, remembering the default shell is cmd.exe, so use findstr instead of grep and tasklist instead of ps. Ask for the SSH password only once per session and never store it in any state file.

When should I not use cross-device diagnosis?▼

Do not use it for single-machine issues, build or compilation errors, or CI failures; those belong to local log debugging or error-fix workflows. It is designed only for problems where the fault could be on either of two devices.

What happens if the diagnosis cannot find a root cause?▼

After three rounds without conclusive evidence the loop escalates with suggested next steps such as adding diagnostic tracing or running a minimal reproduction. At a maximum of five rounds it stops, reports all findings and ruled-out hypotheses, and clears its state file.

Related Skills

Explore More Software Engineering Skills→
Khamel83Khamel83

remote-exec

Execute remote commands over SSH for git sync, file transfer, and tmux jobs.

Community
Advanced
kbrgnjkbrgnj
14

kotlin-spring-proxy-compatibility

Diagnose Spring AOP interception failures caused by Kotlin final defaults, missing compiler plugins, or self-invocation.

Community
Intermediate
matthewdeavesmatthewdeaves

fetch-logs

Fetch PT_Log files from Classic Mac test machines via FTP.

Community
Advanced
ESO-ToolkitESO-Toolkit
2

github-actions-logs

Parse GitHub Actions workflow logs to diagnose CI/CD failures.

Official
Intermediate