omk-computeruselisted

# OMK Computer Use: Neo OMK remains the planner. This skill provides a workflow, not a browser driver, a permission grant, a new agent loop, or a guarantee of any model's performance. ## Start from observable capability 1. Identify the exact target: a website, a local site preview, an authenticated browser session, or a native application. Record the requested result and allowed side effects. 2. Inspect the live tool inventory. A preset, an executable on PATH, or a configured server does not prove that its tools are connected. Use `omk neo list` outside the active agent to inspect packaged skills and offered MCPs, not connection health. 3. Use a deterministic API or file operation when it is safer than UI automation. For browser tasks prefer connected Playwright accessibility/DOM tools. For native apps require an explicitly approved, connected host driver. 4. Read `../omk-browser/SKILL.md` for browser interaction or `../omk-site/SKILL.md` for site implementation. Read `../omk-mcp-setup/SKILL.md` only when setup is actually requested. ## Capability-based modes - A model with working tool calls and text understanding can use DOM/accessibility observations. No image support is needed for this route. - Use screenshots only when the selected model's declared input capabilities include images and the provider accepts the image payload. Never claim to have inspected pixels from a filename or unavailable attachment. - Native desktop actions require the correct target host, permi