Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

LSP Setup

A skill that detects your project's languages, installs and configures the right language server, then verifies it with a real diagnostics roundtrip.

Dev & CodingIntermediate★ 67,531⑂ 5,507AI score 7/10Last updated: Aug 9, 2026

What it does

  • Maps file extensions to a language and routes to references/<language>/README.md for the exact builtin server to use.
  • Collects per-OS install commands (macOS/Linux/Windows), config snippets, initialization options, alternative servers, and troubleshooting notes.
  • detect-lsp.ts scans a project and reports each language's server id, required executable, install status, install hint, and config status (--json supported).
  • verify-lsp.ts performs a real diagnostics roundtrip and returns OK/FAIL/SKIP with exit codes.
  • Documents the config rules for .codex/lsp-client.json and .opencode/lsp.json: project vs user config precedence, priority, extensions overrides, env, disabled.
  • Covers 20+ languages including TypeScript, Python, Go, Rust, C/C++, Java, Kotlin, C#, Swift, Ruby, PHP, Dart, Elixir, Zig, Lua, Bash, YAML, Terraform, Haskell, Julia.

Who it's for

  • Developers stuck on "no LSP server configured" or "server not installed" errors.
  • Anyone deciding between competing servers such as basedpyright vs pyright vs ty vs ruff.
  • Teams working in polyglot monorepos who want diagnostics, go-to-definition, and find-references working everywhere.
  • Users of the Codex or OpenCode (omo) harness who want standardized LSP config.

Usage examples

  1. Onboarding a new repo: ask "set up LSP for this project" — bun scripts/detect-lsp.ts . shows Python and Go servers missing, and you get the exact install commands.
  2. Picking a Python server: ask "basedpyright or pyright?" and get a comparison plus a paste-ready config snippet from references/python/README.md.
  3. Debugging silence: when diagnostics never appear, run bun scripts/verify-lsp.ts src/main.rs to distinguish "not installed" from a server startup error.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the packages/shared-skills/skills/lsp-setup folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/lsp-setup/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/code-yeongyu/oh-my-openagent /tmp/oh-my-openagent && cp -r /tmp/oh-my-openagent/packages/shared-skills/skills/lsp-setup ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository into a temp folder: git clone https://github.com/code-yeongyu/oh-my-openagent /tmp/oh-my-openagent
  3. Create the skills folder if needed: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r /tmp/oh-my-openagent/packages/shared-skills/skills/lsp-setup ~/.claude/skills/
  5. Install Bun so the helper scripts run: curl -fsSL https://bun.sh/install | bash
  6. Restart Claude Code and ask something like "configure LSP" or "install a language server" to trigger the skill.
  7. Note: .codex/lsp-client.json and .opencode/lsp.json are harness-specific; in other setups rely mainly on the install commands and server-selection guidance.
View source on GitHub ↗License: NOASSERTION