New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Kode LSP Maintenance

by shareAI-lab in shareAI-lab/Kode-CLI

Diagnoses why Kode's LSP tool returns nothing and fixes it through plugin .lsp.json files and slash commands, then verifies with a real LSP call.

Apache-2.0Auto-check passedAgent Workflows

Install Kode LSP Maintenance

skills CLI
$ npx skills add shareAI-lab/Kode-CLI --skill lsp-maintain -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shareAI-lab/Kode-CLI lsp-maintain --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shareAI-lab/Kode-CLI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/builtin-skills/skills/lsp-maintain .claude/skills/lsp-maintain && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lsp-maintain
GitHub stars
5.2k
Token cost
~573 tokens
SKILL.md length
272 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnoses why Kode's LSP tool returns nothing and fixes it through plugin .lsp.json files and slash commands, then verifies with a real LSP call.

  • Works in 4 steps: Establish facts (no guessing) → Identify configuration source… → Apply changes through agent CLI → …
  • Working out why Kode returns no LSP results
  • SKILL.md covers Non-negotiables (policy), What “LSP enabled” means in Kode, Step 1 — Establish facts (no… and Step 2 — Identify…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Kode's LSP tool is enabled only when at least one LSP server resolves and at least one is not in an error state. The agent starts from facts: it asks about your languages and project layout, runs /lsp through SlashCommand and reads the configured servers list, and if there are none it concludes that none are configured rather than guessing about missing binaries.

Servers come only from enabled plugins, through a plugin-root .lsp.json file or an lspServers field in the plugin manifest, so adding one means enabling a plugin that provides it or editing that file. Changes are made with plugin slash commands or direct edits, never by telling you to run menu-style install commands, and are verified by re-running /lsp and making one real LSP call such as goToDefinition. Config notes cover stdio-only servers, separate args and unsupported restart and timeout fields.

When your agent uses it

  • Working out why Kode returns no LSP results
  • Adding a language server to a Kode plugin's .lsp.json
  • Checking whether LSP is enabled and which servers resolved

Example prompts

  • “LSP isn't working in Kode. Find out why and fix it.”
  • “Add a TypeScript language server to the plugin's .lsp.json and verify it works.”
  • “Which LSP servers does Kode currently have configured?”

Requirements

  • Kode CLI with plugin support
  • Pre-approved tools (allowed-tools): Read, Edit, SlashCommand

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Establish facts (no guessing)
  2. Identify configuration source (plugin-only)
  3. Apply changes through agent CLI
  4. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit c7f6fcc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Edit
    • SlashCommand

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kode LSP Maintenance loads about 573 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 272 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~573

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shareAI-lab/Kode-CLI at commit c7f6fcc, republished under its Apache-2.0 licence (© shareAI-lab). 272 words, ~573 tokens.

Download SKILL.mdSave it as .claude/skills/lsp-maintain/SKILL.md (or your agent's skills folder).
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)

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

© shareAI-lab, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/builtin-skills/skills/lsp-maintain of shareAI-lab/Kode-CLI.

Open the folder on GitHubat commit c7f6fcc

Compare with similar skills

Kode LSP Maintenance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kode LSP Maintenance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kode LSP Maintenance this skillshareAI-lab/Kode-CLI5.2k—~573Automated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Plugin Settings Patternanthropics/claude-plugins-official38k7 repos~3kAutomated safety check: PassApache-2.0
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    38k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

More from shareAI-lab/Kode-CLI

All 8 skills in this repo

  • Skill Creator

    shareAI-lab/Kode-CLI

    Guides writing a new agent skill or improving an existing one, covering how to keep it concise, how much freedom to give the agent and how to lay out bundled resources.

    5.2k GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed

  • Skill Judge

    shareAI-lab/Kode-CLI

    Evaluates the design quality of an agent skill against official specifications and patterns from existing examples, scoring it and suggesting improvements.

    5.2k GitHub starsUsed in 4 repos~7.5k tokens
    Auto-check passed

  • Vibe Coding Partner

    shareAI-lab/Kode-CLI

    Gives an agent a set of working rules for any development task: understand first, surface decisions, verify results, and load deeper reference files per scenario.

    5.2k GitHub stars~5.6k tokensUpdated today
    Auto-check passed

  • Doc Co-Authoring Workflow

    shareAI-lab/Kode-CLI

    Guides a three-stage workflow for turning partial context into a clear PRD, RFC or design doc: capture context, draft section by section, then test with a fresh reader.

    5.2k GitHub stars~977 tokensUpdated today
    Auto-check passed

  • Kode Capabilities Manager

    shareAI-lab/Kode-CLI

    Lets the Kode agent manage its own features, such as LSP, statusline, output styles and plugins, by running its slash commands for you instead of listing install steps.

    5.2k GitHub stars~760 tokensUpdated today
    Auto-check passed

  • MCP Server Builder

    shareAI-lab/Kode-CLI

    Guide to designing and building MCP servers: tool, resource and prompt design for agent usability, with TypeScript or Python implementation workflows.

    5.2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Kode LSP Maintenance

What does Kode LSP Maintenance do?

Diagnoses why Kode's LSP tool returns nothing and fixes it through plugin .lsp.json files and slash commands, then verifies with a real LSP call. Kode's LSP tool is enabled only when at least one LSP server resolves and at least one is not in an error state. The agent starts from facts: it asks about your languages and project layout, runs /lsp through SlashCommand and reads the configured servers list, and if there are none it concludes that none are configured rather than guessing about missing binaries.

When should I use Kode LSP Maintenance?

Kode LSP Maintenance fits situations like: working out why Kode returns no LSP results; adding a language server to a Kode plugin's .lsp.json; checking whether LSP is enabled and which servers resolved.

How do I install Kode LSP Maintenance in Claude Code?

Run `npx skills add shareAI-lab/Kode-CLI --skill lsp-maintain -a claude-code`. Or copy the skill folder (packages/builtin-skills/skills/lsp-maintain in shareAI-lab/Kode-CLI) into .claude/skills/lsp-maintain in your project. Claude Code loads it when a task matches its description.

How do I install Kode LSP Maintenance in Codex?

Run `npx skills add shareAI-lab/Kode-CLI --skill lsp-maintain -a codex`. Or copy the skill folder (packages/builtin-skills/skills/lsp-maintain in shareAI-lab/Kode-CLI) into .agents/skills/lsp-maintain in your project. Codex loads it when a task matches its description.

Can I use Kode LSP Maintenance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shareAI-lab/Kode-CLI --skill lsp-maintain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lsp-maintain, .gemini/skills/lsp-maintain, .github/skills/lsp-maintain and .opencode/skills/lsp-maintain in your project.

What does Kode LSP Maintenance need to run?

SKILL.md names no scripts, command-line tools or credentials: Kode LSP Maintenance is instructions for the agent only. Our summary lists: Kode CLI with plugin support. Its frontmatter pre-approves these tools: Read, Edit, SlashCommand.

Does Kode LSP Maintenance access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Kode LSP Maintenance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kode LSP Maintenance use?

Kode LSP Maintenance is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kode LSP Maintenance use?

About 573 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Kode LSP Maintenance?

Skills that share tags, products or a category with Kode LSP Maintenance: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kode LSP Maintenance?

shareAI-lab (a GitHub organization) maintains it in shareAI-lab/Kode-CLI, which has 5,234 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

Source: shareAI-lab/Kode-CLI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.