- name
Configures a language server so editor/agent tooling (diagnostics, go-to-definition, references, rename) works. Use when a project needs an LSP installed or wired, or a 'no LSP server configured' erro
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add code-yeongyu/oh-my-openagent --skill lsp-setup -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add code-yeongyu/oh-my-openagent --skill lsp-setup -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add code-yeongyu/oh-my-openagent --skill lsp-setup -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add code-yeongyu/oh-my-openagent --skill lsp-setup -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/code-yeongyu/oh-my-openagent/tree/HEAD/packages/shared-skills/skills/lsp-setupFrom the publisher
Configure the right Language Server for a project so the lsp MCP tools
(diagnostics, goto_definition, find_references, symbols, rename)
actually work. This skill is an index: detect what a project needs, install the
server, write the config, then verify with a real roundtrip.
The list of servers we ship as builtin is the source of truth in
packages/lsp-tools-mcp/src/lsp/server-definitions.ts (BUILTIN_SERVERS +
LSP_INSTALL_HINTS). The per-language references below mirror it.
Identify the language from the file extension, then read the matching reference before installing or configuring anything.
Scan the project to see which languages are present and whether each server is installed and configured:
bun scripts/detect-lsp.ts <projectDir> # human report (default: cwd)
bun scripts/detect-lsp.ts <projectDir> --json
For each detected language it prints the builtin server id, the executable it
needs on PATH, whether that executable is installed, an install hint, and
whether a project config file already references it.
Open references/<language>/README.md and run the install command for your OS.
Then confirm the executable resolves:
command -v <server-executable> # e.g. typescript-language-server, gopls, rust-analyzer
Most builtin servers need no config — they are resolved automatically by
file extension. Write config only to: pick between competing servers, set a
priority, pass initialization options, override extensions, set env, or
disable a server.
Two project-scoped config files, identical JSON shape:
.codex/lsp-client.json (user: ~/.codex/lsp-client.json).opencode/lsp.json (also .omo/lsp.json){
"lsp": {
"<server-id>": {
"command": ["<bin>", "<args>"], // optional for builtin ids (supplied automatically)
"extensions": [".ext"], // optional override
"priority": 100, // higher wins when several servers match an extension
"initialization": { }, // server-specific initializationOptions
"env": { "KEY": "value" }, // optional
"disabled": false // set true to turn a server off
}
}
}
Rules enforced by config-loader.ts:
.codex/lsp-client.json, .opencode/lsp.json) an
entry whose id is a builtin server inherits command automatically — you
only override extensions / priority / initialization. A non-builtin id
in a project config is ignored.command, put
it in the user config (~/.codex/lsp-client.json, or the path set by
LSP_TOOLS_MCP_USER_CONFIG), where command + extensions are honored.Each language reference gives a ready-to-paste snippet.
Run a real diagnostics roundtrip against a source file. This spawns the server,
opens the file, requests diagnostics, and reports OK/FAIL:
bun scripts/verify-lsp.ts <path/to/file.ext>
bun scripts/verify-lsp.ts <file> --timeout=90000
OK = the server started and answered. FAIL: language server not installed
= go back to step 2. Other FAIL text carries the server/startup error.
SKIP = the engine source could not be located; run from inside the omo
repo/worktree, or call the lsp MCP diagnostics tool directly.
Run with Bun: curl -fsSL https://bun.sh/install | bash.
© 2026 Skills Rack.
---name: lsp-setupdescription: Configures a language server so editor/agent tooling (diagnostics, go-to-definition, references, rename)…---# packages/shared-skills/skills/lsp-setup/SKILL.mdOverview
Configures a language server so editor/agent tooling (diagnostics, go-to-definition, references, rename) works. Use when a project needs an LSP installed or wired, or a 'no LSP server configured' error appears.
FAQ
Download packages/shared-skills/skills/lsp-setup/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/code-yeongyu/oh-my-openagent.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.