Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-impact -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-impact --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-impact .claude/skills/lsp-impact && 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-impact" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact into .claude/skills/lsp-impact/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-impact", 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-impactType 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-impact -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-impact --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-impact .agents/skills/lsp-impact && 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-impact" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact into .agents/skills/lsp-impact/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-impact", 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-impact -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-impact --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-impact .cursor/skills/lsp-impact && 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-impact" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact into .cursor/skills/lsp-impact/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-impact", 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-impact--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-impact -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-impact --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-impact .gemini/skills/lsp-impact && 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-impact" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact into .gemini/skills/lsp-impact/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-impact", 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-impactInstalls 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-impact -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-impact .github/skills/lsp-impact && 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-impact" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact into .github/skills/lsp-impact/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-impact", 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-impact -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-impact --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-impact .opencode/skills/lsp-impact && 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-impact" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact into .opencode/skills/lsp-impact/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-impact", 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-impactBlast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it.
Lsp Impact is an agent skill from 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. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.
Its SKILL.md is about 1.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 Development, covering Refactoring. 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.
6 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__go_to_symbolmcp__lsp__find_callersmcp__lsp__type_hierarchymcp__lsp__find_referencesmcp__lsp__get_server_capabilitiesmcp__lsp__blast_radiusFrom 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 Impact loads about 1.8k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 618 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). 618 words, ~1,803 tokens.
.claude/skills/lsp-impact/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.
Blast-radius analysis for any symbol or file. Discovers all direct references, callers (via call hierarchy), and type relationships before you touch anything. Read-only — does not modify any files.
Run this skill before lsp-edit-export: impact tells you what exists and how widespread the change is; lsp-edit-export tells you how to execute the change safely.
Invocation:
"internal/lsp/client.go") → use the File-level entry (Step 0) to surface all exported-symbol impact at once."codec.Encode", "Buffer.Reset") → skip Step 0; start at Prerequisites, then Step 1.Use this shortcut when the user is changing or auditing an entire file rather
than a single symbol. blast_radius enumerates all exported symbols in
the file, resolves their references, and returns test callers (with enclosing
test function names) and non-test callers in a single call.
mcp__lsp__blast_radius({
"changed_files": ["/abs/path/to/file.go"],
"include_transitive": false // set true to surface second-order callers
})Returns:
affected_symbols — each exported symbol with its reference counttest_callers — test files + enclosing test function namesnon_test_callers — production call sitesDecision after Step 0:
| Result | Action |
|---|---|
| 0 non-test callers | Low blast radius. Proceed with change. |
| Few callers, known files | Medium risk. Update each call site. |
| Many callers across packages | High risk. Consider staged rollout. |
| Want symbol-level detail | Continue to Steps 1–5 for any specific symbol. |
Skip Steps 1–5 if the file-level summary is sufficient.
If LSP is not yet initialized, call mcp__lsp__start_lsp with the workspace
root first.
Check what the server supports before proceeding — find_callers and
type_hierarchy are optional LSP features not implemented by all servers:
mcp__lsp__get_server_capabilities()Note which tools appear in supported_tools. Steps 3 and 4 below depend on
this result.
Use go_to_symbol with the symbol name provided by the user:
mcp__lsp__go_to_symbol({
"symbol_path": "Package.SymbolName",
"workspace_root": "/abs/path" // optional, narrows scope
})
→ returns: file, line, column (1-indexed)symbol_path uses dot notation. For a top-level function Encode in package
codec, use "codec.Encode". For a method Reset on type Buffer, use
"Buffer.Reset".
Record the returned file, line, and column — you will pass them to
every subsequent step.
Call find_references with include_declaration: false to find every usage
site across the workspace:
mcp__lsp__find_references({
"file_path": "<file from Step 1>",
"position_pattern": "func @@SymbolName(", // adjust prefix for symbol kind
"include_declaration": false
})Collect all reference locations. Group results by file. Record the total count and list of files — these feed the Impact Report.
See references/patterns.md for position_pattern
examples by language and symbol kind.
Only if find_callers appears in supported_tools from Step 0.
mcp__lsp__find_callers({
"file_path": "<file from Step 1>",
"line": <line from Step 1>,
"column": <column from Step 1>,
"direction": "incoming" // use "both" if callees are also needed
})If find_callers is not in supported_tools, skip this step entirely.
Note "call hierarchy not supported by this server" in the Impact Report.
Only applicable when the symbol is a type, interface, or class (not a
plain function or method). Only if type_hierarchy appears in supported_tools.
mcp__lsp__type_hierarchy({
"file_path": "<file from Step 1>",
"line": <line from Step 1>,
"column": <column from Step 1>,
"direction": "both"
})If the symbol is a function or method: skip this step; note
"not applicable (function)" in the report.
If type_hierarchy is not in supported_tools: skip this step; note
"not supported by this server" in the report.
Produce the Impact Report using the format defined in references/patterns.md.
Include:
find_callers incoming (or skip note)type_hierarchy (or skip note)Then apply the decision guide:
| Blast radius | Recommendation |
|---|---|
| 0 references | Likely dead code. Confirm with lsp-dead-code before deleting. |
| 1–5 files | Low risk. Proceed. Update all callers. |
| 6–20 files | Medium risk. Plan changes carefully. Stage in waves. |
| > 20 files | High risk. Consider a deprecation path or feature flag. |
Goal: assess blast radius of exported function `ParseConfig` in pkg/config
Prerequisites — get_server_capabilities:
→ supported_tools: [go_to_symbol, find_references, find_callers, ...]
→ type_hierarchy: not in supported_tools
Step 1 — go_to_symbol: symbol_path="config.ParseConfig"
→ pkg/config/parser.go:42:6
Step 2 — find_references: position_pattern="func @@ParseConfig("
→ 7 references in 4 files
→ cmd/main.go, internal/app.go, internal/loader.go, pkg/config/parser_test.go
Step 3 — find_callers: direction="incoming"
→ callers: cmd.main (cmd/main.go:14), app.Start (internal/app.go:31), ...
Step 4 — type_hierarchy: skipped (function), also not supported by server
Step 5 — Impact Report:
## Impact Report: ParseConfig
- Kind: function
- Definition: pkg/config/parser.go:42:6
- References: 7 across 4 files
...
- Risk level: lowposition_pattern with @@ is a agent-lsp extension. If your MCP client
does not support it, fall back to explicit line and column parameters from
the location returned by go_to_symbol in Step 1.
© 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-impact of blackwell-systems/agent-lsp.
Open the folder on GitHubat commit 38ca488
Lsp Impact 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 Impact this skillblackwell-systems/agent-lsp | 160 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Guidelinesakash-network/node | 1.1k | 20 repos | ~577 | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Component Refactoringlangflow-ai/langflow | 155k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Ponytail Lazy Developer ModeDietrichGebert/ponytail | 160k | 1 repos | ~873 | Automated safety check: Pass | MIT | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT |
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
DietrichGebert/ponytail
Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
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
Two-phase safe rename across the entire workspace. An agent skill from blackwell-systems/agent-lsp.
blackwell-systems/agent-lsp
Speculative code editing session — simulate changes in memory before touching disk.
Categories
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Lsp Impact is an agent skill from 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.
Lsp Impact fits situations like: changing the signature of any function; tasks that involve Refactoring.
Run `npx skills add blackwell-systems/agent-lsp --skill lsp-impact -a claude-code`. Or copy the skill folder (skills/lsp-impact in blackwell-systems/agent-lsp) into .claude/skills/lsp-impact in your project. Claude Code loads it when a task matches its description.
Run `npx skills add blackwell-systems/agent-lsp --skill lsp-impact -a codex`. Or copy the skill folder (skills/lsp-impact in blackwell-systems/agent-lsp) into .agents/skills/lsp-impact 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-impact -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-impact, .gemini/skills/lsp-impact, .github/skills/lsp-impact and .opencode/skills/lsp-impact in your project.
SKILL.md names no scripts, command-line tools or credentials: Lsp Impact is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__lsp__go_to_symbol, mcp__lsp__find_callers, mcp__lsp__type_hierarchy, mcp__lsp__find_references, mcp__lsp__get_server_capabilities, mcp__lsp__blast_radius. 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 Impact is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.8k tokens (SKILL.md is roughly 7.2k 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 1.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Lsp Impact: Guidelines (akash-network/node, 1.1k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Component Refactoring (langflow-ai/langflow, 155k stars) and Ponytail Lazy Developer Mode (DietrichGebert/ponytail, 160k 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.