CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lsp-setup

Configures a language server so editor/agent tooling (diagnostics, go-to-definition, references, rename) works. Use when a project needs an LSP installed or wired, or a 'no LSP server configured' error appears.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

Exemplary skill body: an index-style overview that routes to one-level-deep per-language references, with fully executable commands and a validated four-phase workflow including error recovery. Only trivial trims are possible.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanation of concepts Claude already knows, but minor spots could be trimmed (the redundant note that references mirror server-definitions.ts, the Bun install aside), fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Every step ships copy-paste-ready commands (detect-lsp.ts with --json, command -v, verify-lsp.ts with --timeout) plus a complete annotated JSON config shape and exact per-harness config paths with exit codes, fully covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced detect → install → configure → verify workflow with an explicit validation roundtrip and an error-recovery feedback loop ("FAIL: language server not installed = go back to step 2"); operations are non-destructive so no cap applies.

5 / 5

Progressive Disclosure

The body is a true index: an extension-to-reference routing table pointing to 20 per-language READMEs (all present, exactly one level deep), a scripts table, and clearly signaled navigation, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 states concrete capabilities and pairs a clear what with an explicit, error-message-based when clause. Trigger coverage is good though it omits a few natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete capabilities ("diagnostics, go-to-definition, references, rename"), but the full action inventory (install, configure, verify) is left to the body, matching 'several specific actions; minor gaps'.

4 / 5

Completeness

Explicitly answers both what ("Configures a language server so editor/agent tooling ... works") and when ("Use when a project needs an LSP installed or wired, or a 'no LSP server configured' error appears") with a concrete trigger phrase; the when-clause is specific rather than merely present, so it is not the 4 anchor.

5 / 5

Trigger Term Quality

Natural terms like "LSP", "language server", "installed or wired", and the literal error string "'no LSP server configured'" are strong triggers, but common variations such as language-specific terms or "code intelligence" are absent, matching 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (language server setup/wiring) with distinct triggers including an exact error message, giving minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.

Validation — 15 / 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/oh-my-openagent

Path

packages/shared-skills/skills/lsp-setup/SKILL.md

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.