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

LSP Code Intelligence

Teaches the agent when and how to use language-server tools for diagnostics, definitions, references, and safe renames.

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

What it does

Guides the agent to call Language Server Protocol tools inside the current workspace:

  • lsp.status — list configured, installed, missing, disabled, and active language servers
  • lsp.diagnostics — check a file or directory for problems (prefer severity: "error" right after edits)
  • lsp.goto_definition — jump to a symbol's definition from file/line/character
  • lsp.find_references — find every usage of a symbol across the workspace
  • lsp.symbols — inspect document symbols or search workspace symbols
  • lsp.prepare_rename / lsp.rename — validate a rename position, then apply the workspace edit

Configuration lives in the project's .codex/lsp-client.json or the user-level ~/.codex/lsp-client.json, mapping each language to a server command and file extensions.

Who it's for

  • Developers navigating large codebases who need precise lookups instead of grep
  • Anyone refactoring who wants renames applied safely across every reference
  • Teams that want compile/type errors surfaced immediately after an edit

Examples

  1. Post-edit check: "Run error-level diagnostics on the files you just changed" → the agent calls lsp.diagnostics with severity: "error".
  2. Safe rename: "Rename UserService to AccountService" → lsp.prepare_rename validates the position, then lsp.rename applies the workspace edit.
  3. Impact analysis: "What breaks if I delete this function?" → lsp.find_references enumerates every call site, with lsp.goto_definition for the source.
  4. Troubleshooting: when diagnostics come back empty, lsp.status reveals whether the language server is actually installed and active.

· · · 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/omo-codex/plugin/components/lsp/skills/lsp folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/lsp/.
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.git /tmp/oh-my-openagent && mkdir -p ~/.claude/skills && cp -r /tmp/oh-my-openagent/packages/omo-codex/plugin/components/lsp/skills/lsp ~/.claude/skills/lsp

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

  1. Open a terminal.
  2. Clone the repository: git clone https://github.com/code-yeongyu/oh-my-openagent.git /tmp/oh-my-openagent
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r /tmp/oh-my-openagent/packages/omo-codex/plugin/components/lsp/skills/lsp ~/.claude/skills/lsp
  5. Connect an lsp MCP server to your agent. This skill assumes the lsp.* tools already exist; without the server, every call fails.
  6. Create .codex/lsp-client.json in your project (or ~/.codex/lsp-client.json) and declare your servers, e.g. {"lsp":{"typescript":{"command":["typescript-language-server","--stdio"],"extensions":[".ts",".tsx"]}}}
  7. Install the matching language-server binaries, e.g. npm i -g typescript-language-server typescript.
  8. Restart the agent and ask "check lsp status" to verify everything is wired up.
View source on GitHub ↗License: NOASSERTION