LSP setup for GitHub Copilot CLI

Prerequisites: the GitHub Copilot CLI installed, plus a package manager (Homebrew, apt, winget, etc.) to fetch the LSP server binary — the skill is a setup utility the agent follows Install "LSP setup for GitHub Copilot CLI" for me. It gives my agent @github's LSP setup workflow: ask which language(s) need code intelligence, detect the OS, look up the server and install command in references/lsp-servers.md, ask the config scope (user-level ~/.copilot/lsp-config.json or repo-level lsp.json / .github/lsp.json), install the server binary, write and merge the JSON config without clobbering existing entries, and verify the binary is on $PATH with valid JSON — enabling go-to-definition, find-references, hover and type info. Reminds the user to /exit and relaunch Copilot CLI so the config loads, then check with /lsp. MIT-licensed. Repository: https://github.com/github/awesome-copilot/blob/main/skills/lsp-setup/SKILL.md 1. Fetch the SKILL.md file (and the references/ folder) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "lsp-setup". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the Copilot CLI, tell the agent which language to set up — the agent asks me before writing any config). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.