MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-understand --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lsp-understand .claude/skills/lsp-understand && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lsp-understand" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand into .claude/skills/lsp-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-understand", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understandType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-understand --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lsp-understand .agents/skills/lsp-understand && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lsp-understand" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand into .agents/skills/lsp-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-understand", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-understand --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lsp-understand .cursor/skills/lsp-understand && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lsp-understand" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand into .cursor/skills/lsp-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-understand", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/blackwell-systems/agent-lsp.git --path skills/lsp-understand--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-understand --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lsp-understand .gemini/skills/lsp-understand && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lsp-understand" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand into .gemini/skills/lsp-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-understand", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install blackwell-systems/agent-lsp lsp-understandInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lsp-understand .github/skills/lsp-understand && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lsp-understand" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand into .github/skills/lsp-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-understand", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-understand --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lsp-understand .opencode/skills/lsp-understand && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lsp-understand" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand into .opencode/skills/lsp-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-understand", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
lsp-understandDeep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source.
Lsp Understand is an agent skill from blackwell-systems/agent-lsp. Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Broader than lsp-explore: accepts files, synthesizes multi-symbol relationships, and produces a navigable dependency map.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/patterns.md`). Compatibility notes: Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
It sits in Agent Workflows. It works with Model Context Protocol. The repository describes itself as: MCP server that orchestrates language servers into agent-native workflows. 65 tools, 30 CI-verified languages. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 38ca488. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
mcp__lsp__inspect_symbolmcp__lsp__go_to_implementationmcp__lsp__find_callersmcp__lsp__find_referencesmcp__lsp__get_symbol_sourcemcp__lsp__list_symbolsmcp__lsp__open_documentmcp__lsp__go_to_symbolmcp__lsp__get_server_capabilitiesFrom allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
From compatibility in the SKILL.md frontmatter.
Lsp Understand loads about 2.8k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 654 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from blackwell-systems/agent-lsp at commit 38ca488, republished under its MIT licence (© blackwell-systems). 654 words, ~2,843 tokens.
.claude/skills/lsp-understand/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Requires the agent-lsp MCP server.
Deep-dive exploration of unfamiliar code — given a symbol or file, synthesizes hover info, implementations, call hierarchy (bounded to 2 levels), all references, and source into a structured Code Map.
Read-only — does not modify any files.
/lsp-explore is a single-symbol pass: given one symbol name, it runs hover +
implementations + call hierarchy + references and produces a per-symbol report.
Use lsp-explore for quick "what is this one thing" questions.
/lsp-understand is broader in three ways:
Use lsp-understand for "how does this module work as a whole."
Mode A (symbol): User provides a symbol name in dot notation
(e.g., "codec.Encode", "Handler.ServeHTTP").
Mode B (file): User provides an absolute file path. All exported symbols in the file become the entry points.
Call mcp__lsp__get_server_capabilities before Step 2 to determine which
capabilities are available. Skip steps that require missing capabilities:
go_to_implementation: skip Step 2b if implementationProvider: falsefind_callers: skip Steps 2c and 2d if callHierarchyProvider: false; note
in the Code Map output that call hierarchy was unavailableCall mcp__lsp__go_to_symbol to locate the symbol definition:
mcp__lsp__go_to_symbol({
"symbol_path": "<dot-notation name>", // e.g. "codec.Encode"
"workspace_root": "<root>" // optional
})
→ returns: file_path, line, column (1-indexed)Record file_path, line, and column. If go_to_symbol returns nothing,
report:
Symbol not found:
<name>Check the dot-notation path (e.g. "Package.Symbol") and ensure the workspace root covers the file.
Stop immediately — do not proceed to Step 2.
The single symbol becomes the sole entry point.
Call mcp__lsp__open_document then mcp__lsp__list_symbols:
mcp__lsp__open_document({ "file_path": "<absolute path>" })
mcp__lsp__list_symbols({ "file_path": "<absolute path>" })
→ returns: list of symbols with kind, line, columnFilter to exported symbols:
export keywordpub visibilityCap at 10 exported symbols maximum. If more than 10 are found, prioritize top-level functions and types; skip constants and variables.
Each filtered symbol becomes an entry point with its file_path, line, and
column.
For each entry point, run the following sub-steps. Where possible, parallelize calls within each step.
Call mcp__lsp__inspect_symbol using position_pattern with the @@
marker (see references/patterns.md):
mcp__lsp__inspect_symbol({
"file_path": "<file>",
"position_pattern": "<symbol@@name>",
"line_scope_start": <line - 5>,
"line_scope_end": <line + 5>
})
→ returns: hover text with type signature and doc commentStore result as hover_text. If the call fails or returns nothing, set
hover_text to an empty string. Do not stop.
If implementationProvider is available in server capabilities:
mcp__lsp__go_to_implementation({
"file_path": "<file>",
"line": <line>,
"column": <column>
})
→ returns: list of concrete implementation locationsSkip if capability is absent. Record "not supported by this server" rather
than stopping.
If callHierarchyProvider is available:
Level 1 — Direct callers:
mcp__lsp__find_callers({
"file_path": "<file>",
"line": <line>,
"column": <column>,
"direction": "incoming"
})
→ returns: list of direct caller functions with file and lineLevel 2 — Callers of callers:
For each Level 1 caller, call mcp__lsp__find_callers once more:
mcp__lsp__find_callers({
"file_path": "<caller file>",
"line": <caller line>,
"column": <caller column>,
"direction": "incoming"
})
→ returns: Level 2 callersSTOP at Level 2 — do not recurse further under any circumstances.
If Level 2 callers > 10: summarize by count and file, do not list individually.
If callHierarchyProvider is available:
mcp__lsp__find_callers({
"file_path": "<file>",
"line": <line>,
"column": <column>,
"direction": "outgoing"
})
→ returns: list of functions this symbol callsLevel 1 only — no recursion.
mcp__lsp__find_references({
"file_path": "<file>",
"line": <line>,
"column": <column>,
"include_declaration": false
})
→ returns: every usage site across the workspaceGroup by file and count distinct files.
mcp__lsp__get_symbol_source({
"file_path": "<file>",
"line": <line>,
"column": <column>
})
→ returns: implementation bodyAfter analyzing all entry points, identify cross-symbol relationships:
This synthesis step is what distinguishes /lsp-understand from running
multiple /lsp-explore calls. The output is a dependency map, not isolated
per-symbol reports.
Produce a structured Code Map with these sections:
## Code Map: <target>
### Summary
<2-3 sentence description of what this code does, synthesized from
hover docs and source reading>
### Symbols (<N> analyzed)
#### <SymbolName>
- **Type:** <type signature from hover>
- **Source:** <file:line>
- **Incoming callers (L1):** <list; count only if > 5>
- **Incoming callers (L2):** <summarized; e.g., "called by 3 HTTP handlers">
- **Outgoing calls:** <what this symbol calls>
- **Implements:** <interface name, if applicable>
- **References:** N sites across M files
### Dependency Relationships
<symbols that call each other, as a simple text diagram or list>
e.g.:
HandlerA → Parse → Validate
HandlerB → Parse
### Entry Points to This Code
<top-level callers that are NOT in this file — where does outside code
call in?>
### Depth-limit Note
Call hierarchy stopped at 2 levels. <N> additional callers exist beyond
Level 2 — use /lsp-explore on specific symbols to drill deeper.These limits are hard constraints — never exceed them:
Goal: understand how the file pkg/codec/encoder.go works as a whole
Step 1 — Mode B (file path)
open_document: pkg/codec/encoder.go
list_symbols: pkg/codec/encoder.go
→ exported symbols: Encoder (type), Encode (func), Reset (func), NewEncoder (func)
→ 4 exported symbols (under 10 cap)
get_server_capabilities
→ go_to_implementation: supported
→ find_callers: supported
Step 2 — Per-symbol analysis (run in parallel across symbols)
Symbol: NewEncoder (pkg/codec/encoder.go:12)
inspect_symbol → "func NewEncoder(w io.Writer) *Encoder"
go_to_implementation → 0 (concrete function)
find_callers incoming L1 → 5 callers
find_callers incoming L2 → 3 callers of those callers
find_callers outgoing → calls: bufio.NewWriter
find_references → 5 sites in 3 files
get_symbol_source → implementation body
Symbol: Encode (pkg/codec/encoder.go:28)
inspect_symbol → "func (e *Encoder) Encode(v any) error"
go_to_implementation → implements codec.Encoder interface
find_callers incoming L1 → 8 callers (listed)
find_callers incoming L2 → > 10: "12 additional callers across 5 files"
find_callers outgoing → calls: NewEncoder, e.w.Flush
find_references → 8 sites in 5 files
get_symbol_source → implementation body
(similar for Encoder type and Reset func...)
Step 3 — Synthesize relationships
- Encode calls NewEncoder (internal dependency)
- NewEncoder and Encode share callers in cmd/main.go
- Encode implements codec.Encoder interface
## Code Map: pkg/codec/encoder.go
### Summary
This file implements a streaming JSON encoder backed by a buffered writer.
NewEncoder constructs an Encoder wrapping any io.Writer; Encode serializes
values and flushes. Reset allows reuse without allocation.
### Symbols (4 analyzed)
#### NewEncoder
- **Type:** func NewEncoder(w io.Writer) *Encoder
- **Source:** pkg/codec/encoder.go:12
- **Incoming callers (L1):** cmd.main, app.Start, loader.Load, test.Setup, bench.Run
- **Incoming callers (L2):** 3 callers across 2 files
- **Outgoing calls:** bufio.NewWriter
- **Implements:** n/a
- **References:** 5 sites across 3 files
#### Encode
- **Type:** func (e *Encoder) Encode(v any) error
- **Source:** pkg/codec/encoder.go:28
- **Incoming callers (L1):** 8 callers (cmd/main.go, internal/app.go, ...)
- **Incoming callers (L2):** 12 additional callers across 5 files (depth limit reached)
- **Outgoing calls:** NewEncoder, e.w.Flush
- **Implements:** codec.Encoder
- **References:** 8 sites across 5 files
...
### Dependency Relationships
cmd.main → NewEncoder → bufio.NewWriter
cmd.main → Encode → NewEncoder
Encode → Reset
### Entry Points to This Code
- cmd.main (cmd/main.go:14)
- app.Start (internal/app.go:31)
- loader.Load (internal/loader.go:55)
### Depth-limit Note
Call hierarchy stopped at 2 levels. 12 additional callers exist beyond
Level 2 for Encode — use /lsp-explore on specific symbols to drill deeper.© 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
SKILL.md and 1 other file (references) in skills/lsp-understand of blackwell-systems/agent-lsp.
Open the folder on GitHubat commit 38ca488
Lsp Understand next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lsp Understand this skillblackwell-systems/agent-lsp | 160 | — | ~2.8k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
blackwell-systems/agent-lsp
Enumerate exported symbols in a file and surface those with zero references across the workspace.
blackwell-systems/agent-lsp
Safe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp.
blackwell-systems/agent-lsp
Apply available quick-fix code actions for all current diagnostics in a file, one at a time with re-collection between each fix.
blackwell-systems/agent-lsp
Trigger language server code generation — implement interface stubs, generate test skeletons, add missing methods, generate mock types.
blackwell-systems/agent-lsp
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it.
blackwell-systems/agent-lsp
Two-phase safe rename across the entire workspace. An agent skill from blackwell-systems/agent-lsp.
Works with
Categories
Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Lsp Understand is an agent skill from blackwell-systems/agent-lsp. Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source.
Lsp Understand fits situations like: agent Workflows work in your project.
Run `npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a claude-code`. Or copy the skill folder (skills/lsp-understand in blackwell-systems/agent-lsp) into .claude/skills/lsp-understand in your project. Claude Code loads it when a task matches its description.
Run `npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a codex`. Or copy the skill folder (skills/lsp-understand in blackwell-systems/agent-lsp) into .agents/skills/lsp-understand in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blackwell-systems/agent-lsp --skill lsp-understand -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lsp-understand, .gemini/skills/lsp-understand, .github/skills/lsp-understand and .opencode/skills/lsp-understand in your project.
SKILL.md names no scripts, command-line tools or credentials: Lsp Understand is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__lsp__inspect_symbol, mcp__lsp__go_to_implementation, mcp__lsp__find_callers, mcp__lsp__find_references, mcp__lsp__get_symbol_source, mcp__lsp__list_symbols, mcp__lsp__open_document, mcp__lsp__go_to_symbol, mcp__lsp__get_server_capabilities. Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Lsp Understand is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 499 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Lsp Understand: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
blackwell-systems (a GitHub user) maintains it in blackwell-systems/agent-lsp, which has 160 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 10, 2026.
Source: blackwell-systems/agent-lsp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.