Run any Skill in Manus with one click

lsp-maintain

Stars5,160

Forks767

UpdatedJune 21, 2026 at 05:16

Diagnose and align Kode LSP behavior with the reference CLI (plugin-based .lsp.json, stdio-only, no install menus). Use when LSP results are missing, LSP is disabled, or you need to configure plugin LSP servers without telling the user to run menu-style install commands.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

shareAI-lab

shareAI-lab/Kode-CLI

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	lsp-maintain
description	Diagnose and align Kode LSP behavior with the reference CLI (plugin-based .lsp.json, stdio-only, no install menus). Use when LSP results are missing, LSP is disabled, or you need to configure plugin LSP servers without telling the user to run menu-style install commands.
allowed-tools	Read Edit SlashCommand

LSP Maintain (Reference-aligned)

Non-negotiables (policy)

Do not respond with menu-style instructions like “run /lsp-maintain install” or “run /lsp-maintain doctor”.
Prefer executing capability changes through SlashCommand (e.g. /plugin ..., /lsp) or Edit to configuration files.
Keep the conversation focused: only load deeper resources if absolutely necessary.

What “LSP enabled” means in Kode

Kode’s LSP tool is enabled only when there is at least one resolved LSP server and at least one is not in error.

Step 1 — Establish facts (no guessing)

Ask for the user goal (languages, monorepo vs single package, whether they already use plugins).
Run /lsp via SlashCommand and read the “Configured servers” list.
If there are zero servers, conclude: no LSP servers are configured (do not speculate about missing binaries).

Step 2 — Identify configuration source (plugin-only)

Kode resolves LSP servers from enabled plugins:

Plugin root .lsp.json (JSON, top-level record)
Plugin manifest field lspServers (inline record or relative file path within plugin root)

If the user needs a new server, the correct path is: enable a plugin that provides it, or add/update a plugin’s .lsp.json.

Step 3 — Apply changes through agent CLI

Prefer:

Use SlashCommand to manage plugins (/plugin ...) and re-check with /lsp.
Use Edit to update the plugin’s .lsp.json or manifest lspServers record/file.

Step 4 — Verify

Re-run /lsp and confirm servers are resolved.
Attempt one LSP tool call (e.g. goToDefinition) on a file extension that is mapped in extensionToLanguage.

Notes for LSP server config authoring

command must be an executable (avoid embedding arguments; use args).
Kode runs servers using stdio pipes.
Do not use restartOnCrash, startupTimeout, or shutdownTimeout in the config (Kode treats them as unsupported).

More from this repository

same repository

capabilities-manage

shareAI-lab/Kode-CLI

Kode capability-management playbook: treat features (LSP, statusline, output styles, plugins, notifications) as configurable capabilities and drive changes through the agent CLI (SlashCommand/Task) instead of pushing users into menu-like flows. Use when the user asks to enable/disable/configure a capability, diagnose why it’s off, or wants the agent to self-manage Kode’s own features (meta capability management).

2026-06-215.2k

doc-coauthoring

shareAI-lab/Kode-CLI

A structured workflow for co-authoring high-signal docs (PRD, RFC, design docs, proposals, decision records). Use when the user needs to turn messy context into a readable artifact with clear goals, tradeoffs, and next steps. Emphasizes context capture, outline-first drafting, and context-free reader testing to catch blind spots.

2026-06-215.2k

frontend-design

shareAI-lab/Kode-CLI

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

2026-06-215.2k

internal-comms

shareAI-lab/Kode-CLI

A set of resources to help write internal communications in common company formats. Use when asked to write internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

2026-06-215.2k

mcp-builder

shareAI-lab/Kode-CLI

Guide for building high-quality MCP (Model Context Protocol) servers and tools: what MCP is, how to design tools/resources/prompts for agent usability, and how to implement servers in TypeScript or Python. Use when you need MCP best practices, server architecture patterns, or a step-by-step build workflow (with language preference).

2026-06-215.2k

permissions-debug

shareAI-lab/Kode-CLI

Troubleshoot Kode permission prompts/denials (tool allowlists, commandAllowedTools, dontAsk fail-closed, subagent inheritance). Use when tools are unexpectedly blocked, permission prompts repeat, or behavior differs between main agent and subagents.

2026-06-215.2k

name	lsp-maintain
description	Diagnose and align Kode LSP behavior with the reference CLI (plugin-based .lsp.json, stdio-only, no install menus). Use when LSP results are missing, LSP is disabled, or you need to configure plugin LSP servers without telling the user to run menu-style install commands.
allowed-tools	Read Edit SlashCommand

LSP Maintain (Reference-aligned)

Non-negotiables (policy)

Do not respond with menu-style instructions like “run /lsp-maintain install” or “run /lsp-maintain doctor”.
Prefer executing capability changes through SlashCommand (e.g. /plugin ..., /lsp) or Edit to configuration files.
Keep the conversation focused: only load deeper resources if absolutely necessary.

What “LSP enabled” means in Kode

Kode’s LSP tool is enabled only when there is at least one resolved LSP server and at least one is not in error.

Step 1 — Establish facts (no guessing)

Ask for the user goal (languages, monorepo vs single package, whether they already use plugins).
Run /lsp via SlashCommand and read the “Configured servers” list.
If there are zero servers, conclude: no LSP servers are configured (do not speculate about missing binaries).

Step 2 — Identify configuration source (plugin-only)

Kode resolves LSP servers from enabled plugins:

Plugin root .lsp.json (JSON, top-level record)
Plugin manifest field lspServers (inline record or relative file path within plugin root)

If the user needs a new server, the correct path is: enable a plugin that provides it, or add/update a plugin’s .lsp.json.

Step 3 — Apply changes through agent CLI

Prefer:

Use SlashCommand to manage plugins (/plugin ...) and re-check with /lsp.
Use Edit to update the plugin’s .lsp.json or manifest lspServers record/file.

Step 4 — Verify

Re-run /lsp and confirm servers are resolved.
Attempt one LSP tool call (e.g. goToDefinition) on a file extension that is mapped in extensionToLanguage.

Notes for LSP server config authoring

command must be an executable (avoid embedding arguments; use args).
Kode runs servers using stdio pipes.
Do not use restartOnCrash, startupTimeout, or shutdownTimeout in the config (Kode treats them as unsupported).