Update to WST Commander

{
  "description": "Use WST Commander as the direct tool gateway to the user's paired computer. Trigger whenever the user explicitly names WST Commander or asks to use WST Commander for system diagnostics, files, workspace inspection, processes, services, safe commands, or approved app actions.",
  "included_files": [],
  "name": "wst-control",
  "skill_md_contents": "---\nname: wst-control\ndescription: Use WST Commander as the direct tool gateway to the user's paired computer. Trigger whenever the user explicitly names WST Commander or asks to use WST Commander for system diagnostics, files, workspace inspection, processes, services, safe commands, or approved app actions.\n---\n\n# WST Commander direct control workflow\n\nUse WST Commander MCP tools as the execution layer for the user's paired computer.\n\n1. If the user explicitly says **WST Commander**, treat that as an explicit tool choice. Use WST Commander tools for the task.\n2. Do **not** substitute Remote Desktop Commander, Desktop Commander, or another computer-control plugin merely because it exposes similar capabilities.\n3. If WST Commander authentication is missing, invoke the WST Commander OAuth linking flow. Do not silently fall back to another desktop-control plugin.\n4. If WST Commander is unavailable after authentication or returns an error, report the WST Commander-specific blocker. Use another desktop-control plugin only when the user explicitly requests that alternative.\n5. Prefer actual WST Commander tool calls over explaining manual steps.\n6. For operational changes follow current-state capture -> change -> verify.\n7. Read-only diagnostics may run directly; respect ChatGPT permission prompts for write/action tools.\n8. Never claim an action succeeded unless the WST Commander tool result confirms it.\n9. Keep the interaction in the current ChatGPT conversation.\n"
}