Lsp Explore

What it does

When your agent uses it

• Agent Workflows work in your project

Example prompts

• “Tell me about this symbol”
• “/lsp-explore”

Requirements

• Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
• Pre-approved tools (allowed-tools): mcp__lsp__start_lsp, mcp__lsp__go_to_symbol, mcp__lsp__inspect_symbol, mcp__lsp__go_to_implementation, mcp__lsp__find_callers, mcp__lsp__find_references, mcp__lsp__open_document, mcp__lsp__get_server_capabilities

Workflow steps

4 steps, taken from the step headings in SKILL.md.

1. 1Locate the symbol
2. 2Hover (always available)
3. 3Implementations (capability-gated)
4. 4Call hierarchy and references (run in parallel)

What it can do on your machine

Read from SKILL.md and the folder at commit 38ca488. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • mcp__lsp__start_lsp
  • mcp__lsp__go_to_symbol
  • mcp__lsp__inspect_symbol
  • mcp__lsp__go_to_implementation
  • mcp__lsp__find_callers
  • mcp__lsp__find_references
  • mcp__lsp__open_document
  • mcp__lsp__get_server_capabilities

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)

  From compatibility in the SKILL.md frontmatter.

Context cost

Lsp Explore loads about 1.6k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 309 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~35

When it runs · the whole SKILL.md, loaded when a task matches

~1.6k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from blackwell-systems/agent-lsp at commit 38ca488, republished under its MIT licence (© blackwell-systems). 309 words, ~1,578 tokens.

name

lsp-explore

description

"Tell me about this symbol": hover + implementations + call hierarchy + references in one pass — for navigating unfamiliar code.

allowed-tools

mcp__lsp__start_lsp, mcp__lsp__go_to_symbol, mcp__lsp__inspect_symbol, mcp__lsp__go_to_implementation, mcp__lsp__find_callers, mcp__lsp__find_references, mcp__lsp__open_document, mcp__lsp__get_server_capabilities

compatibility

Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)

argument-hint

[symbol-name]

user-invocable

true

license

MIT

metadata.required-capabilities

hoverProvider

metadata.optional-capabilities

implementationProvider callHierarchyProvider referencesProvider

mcp__lsp__go_to_symbol({
  "symbol_path": "Package.SymbolName",   // dot notation; e.g. "codec.Encode"
  "workspace_root": "<root>"             // optional
})
→ returns: file, line, column (1-indexed)

mcp__lsp__open_document({
  "file_path": "<file from go_to_symbol>"
})

mcp__lsp__inspect_symbol({
  "file_path": "<file from Phase 1>",
  "line": <line from Phase 1>,
  "column": <column from Phase 1>
})

mcp__lsp__get_server_capabilities()
→ returns: supported_tools list

mcp__lsp__go_to_implementation({
  "file_path": "<file from Phase 1>",
  "line": <line from Phase 1>,
  "column": <column from Phase 1>
})
→ returns: list of implementation locations (file, line)

mcp__lsp__find_callers({
  "file_path": "<file from Phase 1>",
  "line": <line from Phase 1>,
  "column": <column from Phase 1>,
  "direction": "incoming"
})
→ returns: list of caller functions with file and line

mcp__lsp__find_references({
  "file_path": "<file from Phase 1>",
  "line": <line from Phase 1>,
  "column": <column from Phase 1>,
  "include_declaration": false
})
→ returns: list of reference locations (file, line)

## Explore Report: <SymbolName>

### Definition
- File: <file>:<line>
- Hover: <hover_text or "unavailable">

### Implementations (<N> found, or "not supported")
[list of file:line entries, or "none found", or "not supported by this server"]

### Callers (incoming call hierarchy)
[list of caller function names with file:line, or "none", or "not supported"]

### References (<N> total across <M> files)
[list of file:line entries grouped by file, or "none found"]

### Summary
- Symbol kind:      <inferred from hover or "unknown">
- Reference count:  <N>
- Files with refs:  <M distinct files>
- Callers:          <K>
- Implementations:  <P or "not supported">

Goal: understand the exported function `ParseConfig` in pkg/config

Phase 1 — go_to_symbol: symbol_path="config.ParseConfig"
  → pkg/config/parser.go:42:6

open_document: pkg/config/parser.go

Phase 2 — inspect_symbol: line=42, column=6
  → hover_text: "func ParseConfig(path string) (*Config, error) — reads and
    validates a config file from path"

Phase 3 — get_server_capabilities
  → go_to_implementation: in supported_tools
  go_to_implementation: line=42, column=6
  → 0 implementations (ParseConfig is a concrete function, not an interface method)

Phase 4 (parallel):
  find_callers direction=incoming
  → 3 callers: cmd.main (cmd/main.go:14), app.Start (internal/app.go:31),
               loader.Load (internal/loader.go:55)

  find_references include_declaration=false
  → 7 references in 4 files

## Explore Report: ParseConfig

### Definition
- File: pkg/config/parser.go:42
- Hover: func ParseConfig(path string) (*Config, error) — reads and validates a
  config file from path

### Implementations (0 found)
none found

### Callers (incoming call hierarchy)
- cmd.main — cmd/main.go:14
- app.Start — internal/app.go:31
- loader.Load — internal/loader.go:55

### References (7 total across 4 files)
cmd/main.go: line 14
internal/app.go: lines 31, 87
internal/loader.go: line 55
pkg/config/parser_test.go: lines 12, 34, 56, 78

### Summary
- Symbol kind:      function
- Reference count:  7
- Files with refs:  4
- Callers:          3
- Implementations:  0

© blackwell-systems, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/lsp-explore of blackwell-systems/agent-lsp.

• SKILL.md
• references/patterns.md

Open the folder on GitHubat commit 38ca488