Update to Proxyman

{
  "description": "Download, install, launch, and prepare Proxyman on macOS, Windows, or Linux. Use when Proxyman is absent or the user asks to install, download, start, or prepare Proxyman before MCP configuration.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 244
    }
  ],
  "name": "proxyman-download-setup",
  "skill_md_contents": "---\nname: \"proxyman-download-setup\"\ndescription: \"Download, install, launch, and prepare Proxyman on macOS, Windows, or Linux. Use when Proxyman is absent or the user asks to install, download, start, or prepare Proxyman before MCP configuration.\"\n---\n\n# Proxyman Download & Setup\n\nGuide the user through installing and launching Proxyman. This skill is shell-first because Proxyman and its MCP tools may not be available yet.\n\n## Operating Rules\n\n1. Do not use Proxyman MCP tools until Proxyman is installed, launched, and MCP is configured.\n2. Do not hardcode app versions. Use Proxyman's latest release redirects.\n3. On Windows, prefer PowerShell. If the active shell is not PowerShell, wrap PowerShell snippets with `powershell.exe -Command '...'`.\n4. Only install the macOS Helper Tool when system proxy automation is needed or the user asks for it.\n5. Only install a root certificate when the user needs HTTPS decryption. Basic HTTP capture and app installation do not require certificate installation.\n6. On Windows and Linux, launch Proxyman at least once before MCP setup so the app can expose or prepare the bundled MCP bridge.\n\n## Phase 1: Check Existing Installation\n\n### macOS\n\n```bash\nif [ -d \"/Applications/Proxyman.app\" ]; then\n  VERSION=$(/usr/libexec/PlistBuddy -c \"Print CFBundleShortVersionString\" \"/Applications/Proxyman.app/Contents/Info.plist\" 2>/dev/null)\n  echo \"INSTALLED: ${VERSION:-unknown}\"\nelif mdfind 'kMDItemCFBundleIdentifier == \"com.proxyman.NSProxy\"' | grep -q \"Proxyman.app\"; then\n  echo \"INSTALLED: found via Spotlight\"\nelse\n  echo \"NOT_INSTALLED\"\nfi\n```\n\n### Windows (PowerShell)\n\n```powershell\n$installed = Get-ItemProperty `\n  \"HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\*\",\n  \"HKCU:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\*\",\n  \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\*\" `\n  -ErrorAction SilentlyContinue |\n  Where-Object { $_.DisplayName -like \"*Proxyman*\" }\n\nif ($installed) {\n  Write-Host \"INSTALLED: $($installed.DisplayVersion)\"\n} else {\n  Write-Host \"NOT_INSTALLED\"\n}\n```\n\n### Linux\n\n```bash\nif command -v proxyman >/dev/null 2>&1; then\n  echo \"INSTALLED: $(command -v proxyman)\"\nelif ls \"$HOME\"/Downloads/Proxyman*.AppImage \"$HOME\"/Downloads/proxyman*.AppImage >/dev/null 2>&1; then\n  echo \"INSTALLED: AppImage in Downloads\"\nelse\n  echo \"NOT_INSTALLED\"\nfi\n```\n\nIf Proxyman is already installed, launch it and continue to preparation. If the user needs the latest build, download using the platform redirect below.\n\n## Phase 2: Download And Install\n\n### macOS: Homebrew Preferred\n\nIf Homebrew is installed, use the cask:\n\n```bash\nbrew install --cask proxyman\n```\n\nIf Homebrew is unavailable or the user prefers a direct download, use the latest DMG redirect:\n\n```bash\ncurl -L \"https://proxyman.com/release/osx/Proxyman_latest.dmg\" -o \"$HOME/Downloads/Proxyman.dmg\"\nhdiutil attach \"$HOME/Downloads/Proxyman.dmg\" -nobrowse\ncp -R \"/Volumes/Proxyman/Proxyman.app\" /Applications/\nhdiutil detach \"/Volumes/Proxyman\"\n```\n\nIf the volume name differs, list attached volumes and copy from the mounted Proxyman volume:\n\n```bash\nls /Volumes\n```\n\n### Windows\n\nThe Windows endpoint name ends in `.dmg` for legacy reasons, but it redirects to the latest Windows installer.\nThe installer is an NSIS one-click installer and normally launches Proxyman after completion.\n\n```powershell\n$installer = \"$env:USERPROFILE\\Downloads\\ProxymanSetup.exe\"\nInvoke-WebRequest \"https://proxyman.com/release/windows/Proxyman_latest.dmg\" -OutFile $installer -MaximumRedirection 5\nStart-Process $installer -ArgumentList \"/S\" -Wait\n```\n\nIf silent installation fails, run the installer interactively:\n\n```powershell\nStart-Process $installer -Wait\n```\n\n### Linux\n\nDownload the latest AppImage redirect, make it executable, and launch it:\n\n```bash\ncurl -L \"https://proxyman.com/release/linux/proxyman_latest\" -o \"$HOME/Downloads/Proxyman.AppImage\"\nchmod +x \"$HOME/Downloads/Proxyman.AppImage\"\nnohup \"$HOME/Downloads/Proxyman.AppImage\" >/dev/null 2>&1 &\n```\n\nThe packaged Linux app prepares its MCP bridge on first launch. After Proxyman has opened, the stable bridge path should be:\n\n```bash\nBRIDGE_PATH=\"${XDG_CONFIG_HOME:-$HOME/.config}/Proxyman/bin/mcp-server\"\ntest -x \"$BRIDGE_PATH\" && echo \"MCP_BRIDGE: $BRIDGE_PATH\"\n```\n\n## Phase 3: Launch Proxyman\n\n### macOS\n\n```bash\nopen -a \"Proxyman\"\nsleep 10\n```\n\n### Windows (PowerShell)\n\n```powershell\n$candidates = @(\n  \"$env:LOCALAPPDATA\\Programs\\Proxyman\\Proxyman.exe\",\n  \"C:\\Program Files\\Proxyman\\Proxyman.exe\",\n  \"C:\\Program Files (x86)\\Proxyman\\Proxyman.exe\"\n)\n$proxymanExe = $candidates | Where-Object { Test-Path $_ } | Select-Object -First 1\nif ($proxymanExe) {\n  Start-Process $proxymanExe\n  Start-Sleep 10\n} else {\n  Write-Host \"Proxyman executable not found. Launch Proxyman from the Start menu, then continue.\"\n}\n```\n\nAfter launch, the bundled MCP bridge should live next to the app executable. For the default per-user install:\n\n```powershell\n$bridge = \"$env:LOCALAPPDATA\\Programs\\Proxyman\\mcp-server.exe\"\nif (Test-Path $bridge) { Write-Host \"MCP_BRIDGE: $bridge\" }\n```\n\n### Linux\n\n```bash\nif command -v proxyman >/dev/null 2>&1; then\n  nohup proxyman >/dev/null 2>&1 &\nelse\n  nohup \"$HOME/Downloads/Proxyman.AppImage\" >/dev/null 2>&1 &\nfi\nsleep 10\n```\n\nIf the Linux MCP bridge path is missing after launch, ask the user to open Settings > MCP and enable MCP Server, then relaunch Proxyman so the AppImage can copy and `chmod` the bridge into the config folder.\n\n## Windows And Linux MCP Bridge Notes\n\nWindows and Linux Proxyman builds use the same MCP model as macOS: an AI agent launches a bundled `mcp-server` process over stdio, and that bridge talks to the running local Proxyman app through an authenticated localhost handshake.\n\nUse these bridge paths when moving on to `proxyman-mcp-setup`:\n\n| Platform | Bridge path |\n|----------|-------------|\n| Windows default install | `%LOCALAPPDATA%\\Programs\\Proxyman\\mcp-server.exe` |\n| Windows custom install | `mcp-server.exe` in the same folder as `Proxyman.exe` |\n| Linux AppImage | `${XDG_CONFIG_HOME:-$HOME/.config}/Proxyman/bin/mcp-server` |\n\nDo not configure agents to use `Proxyman.exe` or the `.AppImage` as the MCP command. The command must be the stdio bridge executable.\n\n## Phase 4: Prepare Proxy Capture\n\nProxyman can capture different targets in different ways. Ask what the user wants to capture before changing system state.\n\n- Desktop apps and browsers often use the system proxy.\n- CLI runtimes such as Node.js, Python, Ruby, and Go may need Proxyman Automatic Setup or Manual Setup.\n- Localhost traffic may need Reverse Proxy because many clients bypass the system proxy for localhost.\n- iOS apps behind VPNs may need Atlantis instead of classic proxy capture.\n\nUse `proxyman-https-capture` for the target-specific routing, certificate, SSL Proxying, verification, and rollback workflow. Installation alone does not configure every target.\n\n## macOS Helper Tool\n\nThe Helper Tool is macOS-only. Install it when the user wants Proxyman to override system proxy settings reliably across network interfaces, or when system proxy automation fails because privileged network settings are required.\n\nTell the user that macOS may show a visible password or approval dialog, then run:\n\n```bash\nopen -a \"Proxyman\" --args --install-privileged-components\n```\n\nIf macOS shows an approval prompt in System Settings, ask the user to approve Proxyman's Helper Tool and retry the system proxy action.\n\n## Root Certificate\n\nRoot certificate setup is required for HTTPS decryption, not for merely installing Proxyman.\n\nPreferred sequence:\n\n1. Finish app installation.\n2. Configure MCP with `proxyman-mcp-setup` if the user wants agent automation.\n3. Use `get_certificate_status`.\n4. If HTTPS decryption is needed and the certificate is missing or untrusted, use `install_certificate` through MCP or Proxyman's Certificate menu.\n\nWithout MCP, guide the user to Proxyman's in-app Certificate menu and choose the setup path for the target platform. Use `proxyman-https-capture` rather than applying a desktop root certificate to every target indiscriminately.\n\nOn Windows, automatic certificate installation may show a UAC prompt and can use an elevated `certutil` flow. On Linux, automatic trust-store installation is designed for Ubuntu/Debian, Fedora/RHEL, openSUSE/SUSE, and Arch-family systems; unsupported distros may require manual trust-store commands from the Proxyman UI.\n\nSome Proxyman builds expose `proxyman-cli`. Use it only after confirming it exists with `command -v proxyman-cli` or `Get-Command proxyman-cli`. For custom root certificates only, a CLI build that supports root import can use:\n\n```bash\nproxyman-cli install-root-cert /path/to/custom-root.p12 --password \"password\" --trust\n```\n\nDo not use the custom root certificate CLI command for the default Proxyman-generated root CA.\n\n## Phase 5: Suggest MCP Setup\n\nAfter Proxyman is installed and running, offer to configure MCP:\n\n```text\nProxyman is installed and running. The next step is to connect your AI agent to Proxyman MCP so it can inspect traffic, manage rules, install certificates when needed, and use Proxyman setup guidance. Use the proxyman-mcp-setup skill next.\n```\n\nIf the user's next goal is activation, use `proxyman-license-management`. Do not ask them to paste a license key into chat.\n\n## Troubleshooting\n\n| Issue | Action |\n|-------|--------|\n| macOS DMG volume name is different | Run `ls /Volumes`, find the Proxyman volume, and copy `Proxyman.app` from it. |\n| macOS app will not open | Run `xattr -cr \"/Applications/Proxyman.app\"` and launch again. |\n| Windows SmartScreen blocks installer | Ask the user to approve the installer from the visible Windows prompt. |\n| Linux AppImage does not run | Ensure it is executable and that required AppImage/FUSE dependencies are installed. |\n| System proxy cannot be enabled on macOS | Install or approve the Helper Tool, then retry. |\n| HTTPS traffic is still opaque | Install and trust the root certificate, then enable SSL Proxying for the target host. |\n"
}