← ClaudeAtlas

omk-mcp-setuplisted

Inspect Neo bundled skills and curated stdio MCP presets, explain permissions and network effects, and configure only explicitly selected servers without overwriting existing user configuration or claiming untested connectivity.
dmae97/omk · ★ 144 · AI & Automation · score 76
Install: claude install-skill dmae97/omk
# Neo skills and MCP setup Skills are task instructions. MCP servers are executable integrations. Bundled skills, offered presets, installed executables, configured entries, active connections and discovered tools are different quantities. Never make the MCP count nonzero by calling a catalog entry connected. ## Inspect first Run `omk neo list` to inspect the six public bundled skills and two offered MCP presets. This command neither installs nor connects anything. `connected: null` means unprobed, not zero failures. Use the running session's MCP status and live tool inventory to confirm connections after setup. Supported setup presets are `playwright` and `context7`. They use pinned stdio commands because this OMK runtime does not load a bare HTTP MCP URL. Native desktop drivers, Chrome attachment, cloud Browserbase, Stagehand and account-connected GitHub integrations are not enabled by this bundle. They require separately reviewed setup and capability checks. ## Preview the exact change In the intended project directory run: ```bash omk neo setup playwright context7 ``` For user-global configuration add `--global`. The dry run shows target, package pins, network notices and a disabled configuration. It does not read existing credential values, install packages, connect servers or write configuration. After the user has approved the exact target and server execution/network effects: ```bash omk neo setup playwright context7 --apply ``` This creates `<project>/.omk