lsp-setup
Configures a language server so editor/agent tooling (diagnostics, go-to-definition, references, rename) works
Install / Use
npx skills add code-yeongyu/oh-my-openagent --skill lsp-setupInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of lsp-setup
lsp-setup scores 93/100 on our quality scale, 579th of 4,698 Development & Engineering skills we index (top 13%).
Its SKILL.md is 5.4 KB long, well organised into 8 sections with 4 code examples: a solid amount of guidance for an agent.
With 69,362 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so lsp-setup is actively maintained.
- Our last check on 2026-10-25 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (1 minor note below). An AI review judged it risky: Line 139 in the skill file instructs the agent to install Bun by running `curl -fsSL https://bun.sh/install | bash`, i.e., piping a remote script into a shell.
- noteInstalls by piping a downloaded script into a shellline 139
Run with [Bun](https://bun.sh): `curl -fsSL https://bun.sh/install | bash`.
AI review: risky
- Line 139 in the skill file instructs the agent to install Bun by running `curl -fsSL https://bun.sh/install | bash`, i.e., piping a remote script into a shell.
- Per the evaluation criteria, a skill/rules file that tells the agent itself to pipe a remote script into a shell is classified as risky.
- The rest of the file is a legitimate LSP setup workflow, so the risk is specifically the curl|bash installation instruction rather than malicious intent.
AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
lsp-setup compared with similar skills
All 4 of these similar skills score higher than lsp-setup; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| lsp-setup (this skill)by code-yeongyu | 93 | 69.4k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install lsp-setup?
- Run
npx skills add code-yeongyu/oh-my-openagent --skill lsp-setup. The install tabs above show the steps for each supported agent. - Which AI agents does lsp-setup work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is lsp-setup safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (1 minor note below). An AI review judged it risky: Line 139 in the skill file instructs the agent to install Bun by running
curl -fsSL https://bun.sh/install | bash, i.e., piping a remote script into a shell. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand. - Is lsp-setup still maintained?
- The repository was last updated about 2 months ago, so lsp-setup is actively maintained.
Skill content
View source on GitHubname: lsp-setup description: "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."
LSP Setup
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.
PHASE 0 — LANGUAGE GATE (run first)
Identify the language from the file extension, then read the matching reference before installing or configuring anything.
| Extension(s) | Reference |
|---|---|
| .ts .tsx .js .jsx .mjs .cjs .mts .cts .vue .svelte .astro | references/typescript/README.md |
| .py .pyi | references/python/README.md |
| .go | references/go/README.md |
| .rs | references/rust/README.md |
| .c .cpp .cc .cxx .h .hpp .hh .hxx | references/c-cpp/README.md |
| .java | references/java/README.md |
| .kt .kts | references/kotlin/README.md |
| .cs .razor .cshtml | references/csharp/README.md |
| .swift | references/swift/README.md |
| .rb .rake .gemspec .ru | references/ruby/README.md |
| .php | references/php/README.md |
| .dart | references/dart/README.md |
| .ex .exs | references/elixir/README.md |
| .zig .zon | references/zig/README.md |
| .lua | references/lua/README.md |
| .sh .bash .zsh .ksh | references/bash/README.md |
| .yaml .yml | references/yaml/README.md |
| .tf .tfvars | references/terraform/README.md |
| .hs .lhs | references/haskell/README.md |
| .jl | references/julia/README.md |
WORKFLOW — detect → install → configure → verify
1. Detect
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.
2. Install
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
3. Configure
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 harness →
.codex/lsp-client.json(user:~/.codex/lsp-client.json) - OpenCode/omo harness →
.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:
- In a project config (
.codex/lsp-client.json,.opencode/lsp.json) an entry whose id is a builtin server inheritscommandautomatically — you only overrideextensions/priority/initialization. A non-builtin id in a project config is ignored. - To define a fully custom (non-builtin) server with its own
command, put it in the user config (~/.codex/lsp-client.json, or the path set byLSP_TOOLS_MCP_USER_CONFIG), wherecommand+extensionsare honored. - Project entries win over user entries; both win over builtin defaults.
Each language reference gives a ready-to-paste snippet.
4. Verify
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.
Scripts
| Script | Purpose |
|---|---|
| scripts/detect-lsp.ts | Scan a directory; per detected language report server id, install status, install hint, config status. --json for machine output. |
| scripts/verify-lsp.ts | Real LSP diagnostics roundtrip for one file via the lsp-tools-mcp engine; OK/FAIL/SKIP + exit code 0/1/3. |
| scripts/lsp-server-table.ts | Embedded snapshot of the primary builtin server per language (mirrors server-definitions.ts). |
Run with Bun: curl -fsSL https://bun.sh/install | bash.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
