← ClaudeAtlas

omk-neolisted

Entry point for Neo computer-use work in this checkout. Route browser, website, research, code-review and MCP-setup tasks to the matching Neo skill after checking actual capabilities, and explain Neo skill/MCP availability without claiming connections.
dmae97/omk · ★ 144 · AI & Automation · score 76
Install: claude install-skill dmae97/omk
# Neo router Start here for Neo tasks. This skill routes; it does not itself drive browsers, write sites, or configure servers. This checkout integrates and builds the Neo bundle locally on 2026-09-17, but it is an uncommitted working-tree state, not a published release. Verify installed behavior before recommending commands to others. ## Route by target Neo workflow skills are bundled with the installed package under `resources/neo/skills` and are discovered by skill name. Load by name, for example with `!skill:omk-browser` or `/skill:omk-browser`. | Task | Load skill | | --- | --- | | Desktop app, native GUI, or model/capability questions | `omk-computeruse` | | Website interaction, screenshots, structured extraction | `omk-browser` | | Building or validating a site in this repository | `omk-site` | | Current technical documentation lookup | `omk-research` | | Reviewing a change before handoff | `omk-code-review` | | Installing or connecting Neo MCP presets | `omk-mcp-setup` | Read only the matched skill, plus a second one when the task genuinely crosses domains (for example site work needs browser verification). Load `omk-computeruse` when the target is native desktop or you must first decide which model capabilities the task needs. If a matched name is absent from your session inventory, check `omk neo list` for packaging state instead of inventing a path; a missing name is a packaging problem, not a reason to fake a workflow. ## Check Neo state before acting 1. `o