lsp
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Python >=3.10
- Permissions
-
- Read-only
- Env read
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: lsp
description: Multi-language code navigation via persistent LSP daemons. Supports Python (pyright), TypeScript…
category: ai
runtime: Python
---
# lsp output preview
## PART A: Task fit
- Use case: Multi-language code navigation via persistent LSP daemons. Supports Python (pyright), TypeScript/JS, Rust, Go, C/C++, Bash, Java, CSS, HTML, JSON. Auto-detects language from file extension and lazy-starts the appropriate server. Use instead of grep for definitions, references, hover, symbols, and diagnostics. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Supported Languages / Setup / Prerequisites” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Multi-language code navigation via persistent LSP daemons. Supports Python (pyright), TypeScript/JS, Rust, Go, C/C++, Bash, Java, CSS, HTML, JSON. Auto-detects language from file extension and lazy-starts the appropriate server. Use instead of grep for definitions, references, hover, symbols, and diagnostics. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Supported Languages / Setup / Prerequisites” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/usr`, `/path`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, read environment variables, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Supported Languages / Setup / Prerequisites”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: lsp
description: Multi-language code navigation via persistent LSP daemons. Supports Python (pyright), TypeScript…
category: ai
source: tomevault-io/skills-registry
---
# lsp
## When to use
- Multi-language code navigation via persistent LSP daemons. Supports Python (pyright), TypeScript/JS, Rust, Go, C/C++…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Supported Languages / Setup / Prerequisites” and keep inference separate from source facts.
- read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "lsp" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Supported Languages / Setup / Prerequisites
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, read environment variables, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}LSP Code Navigation
Multi-language LSP client that manages per-language background daemons. Auto-detects the language from file extension and routes queries to the correct server. Each server lazy-starts on first use and idles out after 5 minutes of inactivity.
Use this instead of grep/read when you need to:
- Find where something is defined
- Find all usages of a symbol
- Get type signatures or docstrings
- List all classes/functions in a file
- Check for type errors before running code
- Search for a symbol across an entire workspace
Supported Languages
| Language | Server | Extensions | Install |
|---|---|---|---|
| Python | pyright-langserver |
.py, .pyi, .pyx | npm install -g pyright |
| TypeScript/JS | typescript-language-server |
.ts, .tsx, .js, .jsx, .mjs, .cjs | npm install -g typescript-language-server typescript |
| Rust | rust-analyzer |
.rs | rustup component add rust-analyzer |
| Go | gopls |
.go | go install golang.org/x/tools/gopls@latest |
| C/C++ | clangd |
.c, .h, .cpp, .cc, .hpp | apt install clangd or brew install llvm |
| Bash | bash-language-server |
.sh, .bash, .zsh | npm install -g bash-language-server |
| Java | jdtls |
.java | eclipse.jdt.ls |
| CSS | vscode-css-language-server |
.css, .scss, .less | npm install -g vscode-langservers-extracted |
| HTML | vscode-html-language-server |
.html, .htm | npm install -g vscode-langservers-extracted |
| JSON | vscode-json-language-server |
.json, .jsonc | npm install -g vscode-langservers-extracted |
Only install the servers you need. The skill auto-detects which are available and reports helpful install commands for missing ones.
Setup
Prerequisites
- Python 3.10+ (for the client script itself -- stdlib only, no pip deps)
- At least one language server installed (see table above)
Installation
The skill includes a Python script at {baseDir}/scripts/lsp-query.py. This is the LSP client -- it manages background daemons and handles all queries.
To make it callable as lsp-query from anywhere, symlink it into your PATH:
ln -sf {baseDir}/scripts/lsp-query.py /usr/local/bin/lsp-query
# or:
ln -sf {baseDir}/scripts/lsp-query.py ~/.npm-global/bin/lsp-queryAlternatively, invoke it directly:
{baseDir}/scripts/lsp-query.py <command> [args...]Configuration
Set LSP_WORKSPACE to the repo root before querying. If unset, defaults to the git root or cwd.
Commands
All line and column numbers are 1-indexed (human-friendly, matching editor display).
Go to Definition
lsp-query definition /path/to/file.py <line> <col>Find References
lsp-query references /path/to/file.py <line> <col>Hover (Type Info)
lsp-query hover /path/to/file.py <line> <col>Document Symbols
lsp-query symbols /path/to/file.pyWorkspace Symbol Search
lsp-query workspace-symbols "ClassName"Diagnostics
lsp-query diagnostics /path/to/file.pyCompletions
lsp-query completions /path/to/file.py <line> <col>Signature Help
lsp-query signature /path/to/file.py <line> <col>Rename Preview
lsp-query rename /path/to/file.py <line> <col> new_nameServer Management
lsp-query languages # Show all supported languages + install status
lsp-query servers # List running language daemons
lsp-query shutdown # Stop all daemons
lsp-query shutdown python # Stop just the Python daemonWhat's Included
{baseDir}/
├── SKILL.md # This file
└── scripts/
└── lsp-query.py # Python script -- multi-language LSP client + daemon managerlsp-query.py is a self-contained Python script (~850 lines, stdlib only, no pip dependencies). It:
- Forks a single background daemon process on first use
- The daemon lazy-starts language servers as needed (e.g., pyright for .py, typescript-language-server for .ts)
- Communicates with the daemon over a Unix socket (
~/.cache/lsp-query/daemon.sock) - Translates CLI commands into LSP JSON-RPC requests and prints human-readable results
- Each language server auto-stops after 5 minutes idle; the daemon itself stops when all servers are idle
Environment Variables
| Variable | Default | Description |
|---|---|---|
LSP_WORKSPACE |
git root or cwd | Workspace root for LSP servers |
LSP_SERVER |
auto per language | Override server command for ALL languages |
LSP_LANG |
auto from extension | Force a specific language (bypass detection) |
LSP_TIMEOUT |
300 |
Server idle timeout in seconds |
LSP_SOCK |
~/.cache/lsp-query/daemon.sock |
Unix socket path |
Examples
export LSP_WORKSPACE=/path/to/repo
# Python
lsp-query symbols src/model.py
lsp-query hover src/model.py 42 10
lsp-query references src/model.py 42 10
# TypeScript (auto-detected from .ts extension)
lsp-query symbols src/index.ts
lsp-query definition src/app.tsx 15 8
# Rust
lsp-query symbols src/main.rs
lsp-query diagnostics src/lib.rs
# Check what's available
lsp-query languages
lsp-query serversTroubleshooting
- "Server not found for X": The language server binary isn't installed. The error message includes the install command.
- "could not connect to LSP daemon": Daemon failed to start. Verify Python 3.10+ is available.
- Import errors in diagnostics: Expected when packages aren't installed in the current Python environment. These resolve on machines with the correct venv.
- Stale results: Run
lsp-query shutdownto restart all servers fresh. - Slow first query per language: Each server takes 1-2 seconds to cold-start. Subsequent queries to the same language are ~200ms.
- Wrong language detected: Use
LSP_LANG=rust lsp-query symbols myfileto force.
Source: AgentWorkers/skills — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review