install-lsp

Install and configure LSP (Language Server Protocol) for Claude Code to enable go-to-definition, find-references, and real-time diagnostics

Quality

57%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/claude-code-dev/skills/install-lsp/SKILL.md

Quality

Discovery

50%

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

The description excels at specificity and distinctiveness by clearly naming LSP-related capabilities and targeting Claude Code specifically. However, it critically lacks any 'Use when...' guidance, making it incomplete for skill selection purposes. The trigger terms are technically accurate but could benefit from more natural user language variations.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when setting up code intelligence, configuring language servers, or when the user wants go-to-definition or find-references functionality'

Include natural language variations users might say: 'code navigation', 'jump to definition', 'find usages', 'intellisense', 'code intelligence'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Install and configure LSP', 'enable go-to-definition, find-references, and real-time diagnostics'. These are precise, technical capabilities.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant technical terms like 'LSP', 'Language Server Protocol', 'go-to-definition', 'find-references', 'diagnostics', but missing common user variations like 'code navigation', 'jump to definition', 'find usages', or 'intellisense'.	2 / 3
Distinctiveness Conflict Risk	Very clear niche focused specifically on LSP configuration for Claude Code. The combination of 'LSP', 'Language Server Protocol', and 'Claude Code' creates distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Implementation

64%

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

This skill provides highly actionable, executable guidance for LSP setup with two clear installation paths and comprehensive language coverage. However, it's somewhat verbose with explanatory content Claude doesn't need, and the workflow lacks integrated validation checkpoints between installation steps. The monolithic structure could benefit from splitting reference material into separate files.

Suggestions

Remove the 'Why LSP?' section - Claude understands LSP benefits; jump straight to setup options

Add validation checkpoints after each installation step (e.g., 'Verify: /plugin | grep pyright' before proceeding)

Move the LSP Server Requirements table and Troubleshooting section to separate reference files (LSP_SERVERS.md, TROUBLESHOOTING.md)

Remove the 'Best Practice' section - the guidance about combining LSP with grep is obvious to Claude

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary elements like the 'Why LSP?' section explaining benefits Claude already understands, and the 'Best Practice' section stating obvious guidance about combining tools.	2 / 3
Actionability	Provides fully executable commands throughout - specific bash commands, npm/pip installs, complete JSON configuration examples, and exact plugin installation syntax. All code is copy-paste ready.	3 / 3
Workflow Clarity	The 'Execution Instructions' section provides a clear sequence, but lacks explicit validation checkpoints. After installation steps, there's no 'verify before proceeding' pattern - just a final verification section at the end rather than integrated feedback loops.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is inline in one file. The extensive installation tables and troubleshooting could be split into separate reference files, with SKILL.md providing a leaner overview.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

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.