What problem does it solve? Users running Paseo often struggle to answer setup, configuration, and troubleshooting questions because the daemon topology (desktop-managed, standalone, or Docker) changes where logs, providers, and config actually live. This Skill answers Paseo product questions directly while grounding every answer in the current public documentation. ## Core Features & Use Cases - Documentation-grounded answers: Fetches the paseo.sh llms.txt index and the relevant Markdown docs page before answering, then links the source. - Topology-aware diagnosis: Identifies whether the daemon is desktop-managed, standalone, or Docker-based, and how the client connects (local, relay, LAN/VPN/Tailscale) before suggesting fixes. - Read-only diagnostics: Uses commands like paseo daemon status --json and paseo provider diagnostic <provider> --json plus known log and config paths to gather evidence without restarting or modifying anything. - Use Case: A user reports their agent provider shows "command not found" in Paseo Desktop connected to a remote server. The Skill identifies the remote daemon as the affected host, runs the provider diagnostic against it, compares the daemon PATH with a fresh login shell, and links the troubleshooting doc. ## Quick Start Ask the paseo-help skill why your Paseo provider is not detected on your remote daemon and have it walk you through the diagnosis.
