Check that the CAD plugin can start after it is installed or updated: verify uv is installed with `uv --version`, direct the user to uv's official installation guide if it is not, and instruct them to restart the app so the CAD viewer appears in the sidebar and in thread tabs. Includes diagnosis for cases where the viewer did not start.
Tasks
Run `uv --version` to check whether uv is installed after the CAD plugin is installed or updated
If uv is missing, tell the user CAD needs it and point them to uv's official installation guide at https://docs.astral.sh/uv/getting-started/installation/
Tell the user to quit and reopen the app so the CAD viewer appears in the sidebar and as a tab in each thread
When the viewer did not start, diagnose common causes: uv not on the login shell's PATH, no network on first start after install or update, or the app not yet restarted after a plugin update
Inputs
Installed local skill files used as the runtime source of truth
The plugin's MCP config, which contains the `uvx` command and pinned runtime version
Outputs
Result of the `uv --version` check
Guidance for the user on installing uv, restarting the app, and resolving viewer startup failures
Limitations and checks
The skill only checks and explains; it installs nothing, downloads nothing, and changes nothing in the user's projects
Threads started before a plugin update keep the old pinned runtime until the app is restarted
The first start after an update can take a few minutes on a slow connection
Confirm `uv --version` runs successfully, ideally in a new login shell, since the app reads the login shell's PATH
Verify the app has been quit and reopened after install or update so the CAD entry appears in the sidebar and as a thread tab
Confirm a network connection was available on the first start after install or update so the pinned runtime could be fetched
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control