Skip to content
cccskills
FreePublished on GitHub

lsp-maintain

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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)

  1. Ask for the user goal (languages, monorepo vs single package, whether they already use plugins).
  2. Run /lsp via SlashCommand and read the “Configured servers” list.
  3. 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

  1. Re-run /lsp and confirm servers are resolved.
  2. 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).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

The English summary is being prepared. Showing the original description.

shareAI-lab/Kode-CLI5.2KUpdated Oct 16, 2026

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).

The English summary is being prepared. Showing the original description.

shareAI-lab/Kode-CLI5.2KUpdated Oct 16, 2026

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.

The English summary is being prepared. Showing the original description.

shareAI-lab/Kode-CLI5.2KUpdated Oct 16, 2026

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.

The English summary is being prepared. Showing the original description.

shareAI-lab/Kode-CLI5.2KUpdated Oct 16, 2026

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.).

The English summary is being prepared. Showing the original description.

shareAI-lab/Kode-CLI5.2KUpdated Oct 16, 2026

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).

The English summary is being prepared. Showing the original description.

shareAI-lab/Kode-CLI5.2KUpdated Oct 16, 2026

See all skills by shareAI-lab

Report a problem with this skill