Lsp Setup Assistant

Detect, plan, and configure Language Server Protocol (LSP) support for any project with safety-first verification.

Install
cmdop skills install agensi-lsp-setup-assistant

LSP Setup Assistant is a skill that addresses the problem of unconfigured or broken LSP support in new and existing repositories. It scans project structure, analyzes manifests and lockfiles to identify the technology stack, and checks for any existing configurations before proposing changes. Supported languages include Python, TypeScript, Go, Rust, C++, Java, and others.

Before touching any file, the skill generates a detailed Setup Plan for developer approval. This plan-first approach prevents the common failure mode where an AI agent applies global installs or writes incorrect config paths. Once approved, the skill installs and configures industry-standard language servers including pyright for Python, rust-analyzer for Rust, and gopls for Go.

Conflict resolution is built in: the skill detects competing language servers that could cause duplicate error reporting or performance degradation and flags them before proceeding. After installation, it verifies that the server binary is present and that diagnostics are actually firing, rather than simply running an install command and reporting success. All installations are scoped to the project to avoid polluting the global environment. This makes it suitable for onboarding into unfamiliar codebases, setting up CI environments, or standardizing LSP configuration across a team.

Use cases

  • Detect which language servers are needed for a polyglot repository and generate a setup plan
  • Configure pyright for a Python project with project-scoped isolation
  • Set up rust-analyzer and verify diagnostics are active before finishing
  • Identify and resolve conflicting LSP servers causing duplicate errors
  • Onboard into an unfamiliar codebase and restore full code intelligence without manual research
  • Standardize gopls configuration across multiple Go projects in a team

When to use it

  • Starting work in a new or cloned repository with no LSP configuration
  • Diagnosing broken autocompletion or go-to-definition in an existing project
  • Enforcing project-scoped server installations rather than global ones
  • Resolving conflicts between multiple competing language servers
  • Verifying that LSP diagnostics are genuinely active after a setup step

When not to use it

  • The project requires a language server not covered by the skill's detection logic
  • No tools are exposed by this skill, so it cannot be composed into a tool-call pipeline
  • Environments where no approval step is possible and fully automated unattended setup is required
  • Projects that already have a working, validated LSP configuration needing no changes