Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
71
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
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.
895b70c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.