debug-claude-session
Investigate a specific Claude Code session by session ID — correlate the local transcript (`~/.claude/projects/...jsonl`) with the router's production logs to…
Install language servers (gopls, typescript-language-server, pyright, rust-analyzer) and their prerequisite toolchains (Go, Node/npm, rustup) so the lsp tool works. Use when the user asks to enable or install LSP / language-server support, when lsp_enable reports a missing
$ npx -y skills add workweave/router --skill install-lsps --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/install-lspsContext preview
The summary Claude sees to decide when to auto-load this skill.
Install language servers (gopls, typescript-language-server, pyright, rust-analyzer) and their prerequisite toolchains (Go, Node/npm, rustup) so the lsp tool works. Use when the user asks to enable or install LSP / language-server support, when lsp_enable reports a missing
name: install-lsps description: Install language servers (gopls, typescript-language-server, pyright, rust-analyzer) and their prerequisite toolchains (Go, Node/npm, rustup) so the lsp tool works. Use when the user asks to enable or install LSP / language-server support, when lsp_enable reports a missing toolchain, or when the lsp tool reports no language server is installed.
Enable the `lsp` tool for a language by installing its language server — and, when the server install needs it, the underlying toolchain.
and confirm each toolchain install separately — those are system-level changes, not part of whatever task prompted this.
`lsp_enable` with `{"language": "<language>", "action": "dismiss"}`.
exists; reach for bash only for the prerequisites `lsp_enable` refuses to install itself.
Work the ladder for each language the user wants:
1. **Check what is missing.** Server binaries: `gopls`, `typescript-language-server`, `pyright-langserver` (or `basedpyright-langserver`), `rust-analyzer` — also look in `~/go/bin` and `~/.cargo/bin`, which the lsp tool searches even when they are off PATH. Toolchains: `go`, `npm`, `rustup`. 2. **Toolchain present** → call `lsp_enable` with `{"language": "<go|typescript|python|rust>"}` and you are done; it runs the right server install and verifies the binary resolves. 3. **Toolchain missing** → show the user the command you intend to run, get their confirmation, run it in bash, then return to step 2. 4. **Verify** with a real `lsp` query (`documentSymbol` on an actual source file). The first query per workspace can take up to a minute while the server indexes; that is normal.
Go (for gopls):
brew install go # macOS sudo apt-get install -y golang-go # Debian/Ubuntu; or dnf install golang
Or the official downloads at https://go.dev/dl for anything else.
Node/npm (for typescript-language-server and pyright):
brew install node # macOS sudo apt-get install -y nodejs npm # Debian/Ubuntu
Or nvm (https://github.com/nvm-sh/nvm) when the user prefers per-user installs.
rustup (for rust-analyzer):
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
This is the official rust installer; show the user the command before running it and follow its printed PATH instructions afterwards.
`~/.cargo/bin`. The lsp tool finds both without PATH changes; other tools may still want a PATH entry.
`npx @weave-os/router --pi --lsp go,typescript,python,rust`.
Model router for agentic systems. Routes every prompt to the right model in <50ms. Cut costs 40-70% with just an endpoint change.
Repo: workweave/router
Investigate a specific Claude Code session by session ID — correlate the local transcript (`~/.claude/projects/...jsonl`) with the router's production logs to…
Investigate a specific Codex CLI session by session ID — correlate the local rollout transcript (`~/.codex/sessions/YYYY/MM/DD/rollout-*-<SESSION_ID>.jsonl`)…
Fetches feedback from a GitHub PR — review-thread comments, ad-hoc PR comments (including those posted as a review's body without a thread), and bot/advisory…
Run the Weave router locally in docker compose and drive it with `claude -p` to reproduce and verify routing/translation behavior for a specific upstream model…
Run the Weave router locally in docker compose and drive it with `codex exec` to reproduce and verify routing/translation/marker behavior for Codex's Responses…
Recipes for the lsp tool — resolving where a symbol is defined, every place it is used, type signatures and docs, file outlines, and compiler/type errors…