Agent skill · software engineering · github
lsp-setup
Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for Copilot CLI. Detects the OS, installs the right server, and generates the JSON configuration (user-level or repo-level). Use when you need deeper code understanding and no LSP server is configured, or when the user asks to set up, install, or configure an LSP server.
Why this skill is useful
Adds executable scripts for installing and configuring LSP servers that enhance code intelligence capabilities in Copilot CLI.
What it needs
Requires copilot-cli installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
LSP Setup for GitHub Copilot CLI UTILITY SKILL — installs and configures Language Server Protocol servers for Copilot CLI. USE FOR: "setup LSP", "install language server", "configure LSP for Java", "add TypeScript LSP", "enable code intelligence", "I need go-to-definition", "find references not working", "need better code understanding" DO NOT USE FOR: general coding tasks, IDE/editor LSP configuration, non-Copilot-CLI setups Workflow 1. Ask the language — use askuser to ask which programming language(s) the user wants LSP support for 2. Detect the OS — run uname -s (or check for Windows via $env:OS / %OS%) to determine macOS, Linux, or Windows 3. Look up the LSP server — read references/lsp-servers.md for known servers, install commands, and config snippets 4. Ask scope — use askuser to ask whether the config should be user-level (~/.copilot/lsp-config.json) or repo-level (lsp.json at the repo root or .github/lsp.json) 5. Install the server — run the appropriate install command for the detected OS 6. Write the config — merge the new server entry into the chosen config file (~/.copilot/lsp-config.json for user-level; lsp.json or .github/lsp.json for repo-level). If a repo-level config already exists, keep using that location; otherwise ask the user which repo-level location they prefer. Create the file if missing and preserve existing entries. 7. Verify — confirm the LSP binary is on $PATH and the config file is valid JSON Configuration Format Copilot CLI reads LSP configuration from user-level or repo-level locations, and repo-level config takes precedence over user-level config: User-level: ~/.copilot/lsp-config.json Repo-level: lsp.json (repo root) or .github/lsp.json The JSON structure: Key rules command is the binary name (must be on $PATH) or an absolute path. args almost always includes "--stdio" to use standard I/O transport. fileExtensions maps each file extension (with leading dot) to a Language ID. Multiple servers can coexist in lspServers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/lsp-setup