---
name: nexusdock
description: "Use when users ask which devices are online or want to use their own computer, another device, a remote server, local files, terminal, desktop apps or authenticated browser through NexusDock. Examples: 哪些设备在线, 使用本机, 操作其他设备, 连接远程电脑. Skip general questions and assistant-sandbox tasks."
---

# NexusDock

This Skill helps the AI recognize real-device tasks and use the NexusDock remote MCP connection already available in the current client. It is an instruction guide, not a tool, credential store, or connection installer.

## When to use

Load when a user requests an inventory of connected or online devices, wants to operate a specific computer/phone/server, or asks to use their real local or remote environment (files, commands, browser, installed applications).

For theoretical explanations and work fully confined to the assistant's sandbox, do not invoke NexusDock. If the word "local" is ambiguous and the distinction matters, clarify whether the user means their own computer or the current AI runtime.

## Prerequisite

NexusDock must already be registered as a native remote MCP connection in the AI client and authorized through OAuth. Its endpoint is https://mcp.nexusdock.co/mcp. Installing this Skill alone does not register or authenticate MCP.

If NexusDock tools are missing, report that the client is not connected. Do not claim success based on a script, curl, direct HTTP request or local proxy. For supported clients, the official setup instructions are at https://www.nexusdock.co/docs/ai-connect/.

## Device workflow

1. Call the *registered NexusDock MCP tool* `agentdock_context` and inspect current devices, online status, capabilities, and IDs.
2. If the user only asked what is online, answer from that context without operating a device.
3. Use the device explicitly selected by the user; otherwise select only when the intended device is unambiguous. Never reuse stale IDs or silently switch devices if a target is offline.
4. For repository or workspace tasks, call `workspace_context` for the selected `node_id` before changing files.
5. Invoke actual, available NexusDock tools with the returned `node_id`. Follow each tool's permissions and supported arguments.
6. Check actual state before changes, verify after changes, and explain any failure precisely.

## Safety

Do not expose access tokens, passwords, pairing codes or cookies in messages or files. Respect the user's requested device and the client's approval requirements. Never infer that an unavailable tool exists.

## Documentation

- Native setup: https://www.nexusdock.co/docs/ai-connect/
- Client connections: https://www.nexusdock.co/docs/connect-ai/
- Troubleshooting: https://www.nexusdock.co/docs/troubleshooting/