CtrlK
BlogDocsLog inGet started
Tessl Logo

lsp-setup

Configure a Language Server (LSP) for a specific language so editor/agent tooling — diagnostics, go-to-definition, find-references, rename — works. Use when you need to: configure LSP, lsp setup, set up or install a language server, fix 'no LSP server configured' / 'server not installed', choose between servers (basedpyright vs pyright vs ty vs ruff), or wire .codex/lsp-client.json / .opencode/lsp.json. 언어서버 설정. Routes by file extension to references/<language>/README.md for the exact builtin server, per-OS install commands (macOS/Linux/Windows), config snippets for both config files, initialization options, alternatives, and troubleshooting. Ships scripts: detect-lsp.ts (scan a project for languages + each server's install/config status) and verify-lsp.ts (run a real diagnostics roundtrip). Covers typescript, python, go, rust, c/c++, java, kotlin, c#/razor, swift, ruby, php, dart, elixir, zig, lua, bash, yaml, terraform, haskell, julia.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, actionable index that keeps the body lean, gives copy-paste commands and config, sequences a validated workflow with error-recovery, and cleanly delegates per-language detail to real one-level-deep references. Strong across all four dimensions.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — 'This skill is an index: detect → install → configure → verify' — with tight command examples and no padding explaining what an LSP is or how language servers work. The extension routing table is large but justified as the core navigation map, so every token earns its place.

3 / 3

Actionability

Fully executable, copy-paste-ready guidance: concrete commands like 'bun scripts/detect-lsp.ts <projectDir> --json', 'command -v <server-executable>', and 'bun scripts/verify-lsp.ts <file> --timeout=90000', plus a complete annotated JSONC config snippet and explicit config-loader rules — no pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced 'detect → install → configure → verify' workflow with an explicit validation checkpoint in the verify step and a feedback loop ('FAIL: language server not installed = go back to step 2'), plus OK/FAIL/SKIP outcomes with exit codes, matching the level-3 anchor.

3 / 3

Progressive Disclosure

A concise overview that routes by file extension to one-level-deep references/<language>/README.md (all 20 verified present) and a Scripts table mapping the three shipped scripts (all verified present) to their purposes — content appropriately split out of the index.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities, provides explicit 'Use when' triggers, and pins a distinct niche with specific file paths and server choices. No voice or over-claim issues; it earns top marks across all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Configure a Language Server', 'set up or install a language server', 'fix no LSP server configured / server not installed', 'choose between servers (basedpyright vs pyright vs ty vs ruff)', and 'wire .codex/lsp-client.json / .opencode/lsp.json' — plus named tooling capabilities (diagnostics, go-to-definition, find-references, rename). This exceeds the 'names domain and some actions' anchor by enumerating many specific actions.

3 / 3

Completeness

Explicitly answers both 'what' (configure a language server so diagnostics/go-to-definition/etc. work; routes by extension to per-language READMEs with install, config, and troubleshooting) and 'when' via the 'Use when you need to: ...' trigger clause, matching the level-3 anchor exactly.

3 / 3

Trigger Term Quality

Natural trigger terms users would actually say — 'configure LSP', 'lsp setup', 'set up or install a language server', and 'fix no LSP server configured' — plus the Korean '언어서버 설정' — give strong coverage of phrasings a user would naturally utter when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The niche is sharply defined — LSP setup for specific languages, with distinct triggers citing exact config paths (.codex/lsp-client.json, .opencode/lsp.json) and concrete server names — making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 20 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
code-yeongyu/lazycodex
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.