Lsp

code-yeongyu/lsp

Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

303 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

67138

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/code-yeongyu/oh-my-openagent --skill lsp

found in the instruction text

Bash runs shell commands — read the instruction before connecting

3 sections, as written by the author

Call lsp MCP tools through the tool interface; lsp.*/mcp__lsp__* are tool-call names, not shell commands.

lsp.status: list configured, installed, missing, disabled, and active language servers.
lsp.diagnostics: check one file or directory for LSP diagnostics. Prefer severity: "error" after edits.
lsp.goto_definition: locate a symbol definition from file, line, and character.
lsp.find_references: find usages of a symbol across the workspace.
lsp.symbols: inspect document symbols or search workspace symbols.
lsp.prepare_rename: check whether a rename is valid at a position.
lsp.rename: apply a language-server workspace edit for a rename.

Project config lives at .codex/lsp-client.json; user config lives at ~/.codex/lsp-client.json.

{
	"lsp": {
		"typescript": {
			"command": ["typescript-language-server", "--stdio"],
			"extensions": [".ts", ".tsx", ".js", ".jsx"]
		}
	}
}

Use lsp.status first when diagnostics report a missing language server.

Copy the folder

Take code-yeongyu/lsp from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.