How do I install the Rust Lsp skill?

Run npx skillmds@latest add fedemagnani/rust-lsp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rust Lsp safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rust Lsp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rust Lsp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rust Lsp?

fedemagnani (@fedemagnani) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rust Lsp by fedemagnani — Agent Skill

Name: Rust Lsp
Author: fedemagnani

Rust Lsp

This skill MUST be used for semantic Rust navigation and analysis: resolving definitions across crate boundaries, finding all references to a symbol, inspecting inferred types or trait implementations, searching symbols by name, and renaming symbols safely. SHOULD be preferred over grep or file reads whenever the task requires Rust-aware understanding.

fedemagnani bbb2f0a 2 files · 2.7 KB Updated Sep 17, 2026

File contents

Rust Analyzer Agent Skill

When to use

MUST use the MCP tools when the task involves:

Resolving where a symbol is defined, including across crate boundaries
Finding all references to a function, type, field, or trait method
Inspecting type signatures, inferred types, or trait implementations
Searching for symbols by name across a workspace
Renaming a symbol across all usage sites

SHOULD prefer the MCP tools over grep or file reads when the task requires Rust-aware semantic understanding (scoping, imports, trait dispatch, macro expansion).

Fall back to grep or file reads when the task is not Rust-specific, targets string literals or comments, or covers files outside the Rust compilation.

Installation

If the Rust LSP tools are not available yet, run scripts/install.sh from this skill before using the MCP tools. Treat the tools as "not available yet" whenever the current session does not expose the Rust LSP MCP tool APIs: attempt the install/setup path first, then verify whether the tools become usable.

Common workflows

Navigate to a definition

definitions at the symbol position
Read the target file at the returned location

Find all callers

references at the function name position
Review the returned locations

Inspect a type

hover at the position — returns the resolved type even for inferred types, trait objects, and generic instantiations

Find a symbol by name

workspace_symbols with the name as query
Read the returned location if needed

Rename a symbol safely

open_document with the file contents
rename_symbol at the position with the new name
Apply the returned workspace edits to disk
close_document when done

Update in-memory content for analysis

Position-based tools work on saved files without open_document. Use the document lifecycle only when analyzing unsaved or in-memory content:

open_document to synchronize contents with rust-analyzer
replace_document to update contents (version auto-increments)
close_document when done (idempotent)

React to project structure changes

reload_workspace after editing Cargo.toml or adding/removing crates
rebuild_proc_macros if proc-macro source changed

---name: rust-lspdescription: This skill MUST be used for semantic Rust navigation and analysis: resolving definitions across crate boundaries, finding all references to a symbol, inspecting inferred types or trait implementations, searching symbols by name, and renaming symbols safely. SHOULD be preferred over grep or file reads whenever the task requires Rust-aware understanding.---# Rust Analyzer Agent Skill## When to use**MUST** use the MCP tools when the task involves:- Resolving where a symbol is defined, including across crate boundaries- Finding all references to a function, type, field, or trait method- Inspecting type signatures, inferred types, or trait implementations- Searching for symbols by name across a workspace- Renaming a symbol across all usage sites**SHOULD** prefer the MCP tools over grep or file reads when the task requires Rust-awaresemantic understanding (scoping, imports, trait dispatch, macro expansion).**Fall back to grep or file reads** when the task is not Rust-specific, targets string literalsor comments, or covers files outside the Rust compilation.## InstallationIf the Rust LSP tools are not available yet, run `scripts/install.sh` from this skill before using the MCP tools. Treat the tools as "not available yet" whenever the current session does not expose the Rust LSP MCP tool APIs: attempt the install/setup path first, then verify whether the tools become usable.## Common workflows### Navigate to a definition1. `definitions` at the symbol position2. Read the target file at the returned location### Find all callers1. `references` at the function name position2. Review the returned locations### Inspect a type1. `hover` at the position — returns the resolved type even for inferred types, trait objects, and generic instantiations### Find a symbol by name1. `workspace_symbols` with the name as query2. Read the returned location if needed### Rename a symbol safely1. `open_document` with the file contents2. `rename_symbol` at the position with the new name3. Apply the returned workspace edits to disk4. `close_document` when done### Update in-memory content for analysisPosition-based tools work on saved files without `open_document`. Use the documentlifecycle only when analyzing unsaved or in-memory content:1. `open_document` to synchronize contents with rust-analyzer2. `replace_document` to update contents (version auto-increments)3. `close_document` when done (idempotent)### React to project structure changes1. `reload_workspace` after editing `Cargo.toml` or adding/removing crates2. `rebuild_proc_macros` if proc-macro source changed

Frequently asked questions