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

Pure Lsp Connect

by finos in finos/legend-engine

Attaches the pure-lsp HTTP bridge to an LSP daemon that is ALREADY running (e.g.

Apache-2.0Auto-check passed

Install Pure Lsp Connect

skills CLI
$ npx skills add finos/legend-engine --skill pure-lsp-connect -a claude-code

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

GitHub CLI
$ gh skill install finos/legend-engine pure-lsp-connect --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/finos/legend-engine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/pure-dev/skills/pure-lsp-connect .claude/skills/pure-lsp-connect && 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
pure-lsp-connect
GitHub stars
113
Token cost
~1.3k tokens
SKILL.md length
663 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Attaches the pure-lsp HTTP bridge to an LSP daemon that is ALREADY running (e.g.

  • Works in 4 steps: Verifies something is actually listening… → Checks for an existing bridge by… → If found, verifies it's actually healthy… → …
  • Connect to the existing/already-running LSP
  • SKILL.md covers Run the script and What the script automates…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pure Lsp Connect is an agent skill from finos/legend-engine. Attaches the pure-lsp HTTP bridge to an LSP daemon that is ALREADY running (e.g. started from IntelliJ, or left over from a prior session) - never spawns a new daemon JVM. Defaults to socket port 9100. Use for 'connect to the existing/already-running LSP', 'attach the bridge to the LSP on port X', or 'reconnect to the LSP' - as opposed to pure-lsp-launch-engine, which boots a new session. Also recovers a bridge whose connection has gone stale (health OK, requests fail with a broken pipe).

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with JetBrains IDEs. The licence is Apache-2.0.

When your agent uses it

  • Connect to the existing/already-running LSP
  • Attach the bridge to the LSP on port X
  • Reconnect to the LSP - as opposed to pure-lsp-launch-engine
  • Which boots a new session

Example prompts

  • “connect to the existing/already-running LSP”
  • “attach the bridge to the LSP on port X”
  • “reconnect to the LSP”
  • “/pure-lsp-connect”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Verifies something is actually listening on the socket port (/dev/tcp probe) before doing
  2. Checks for an existing bridge by confirming every pgrep candidate against /proc: it must be
  3. If found, verifies it's actually healthy (health + status). If status fails, fetches the raw
  4. If no bridge is attached, resolves repo-roots/classpath/server-jar (via resolve_lsp_server_jar in

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).

    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

Pure Lsp Connect loads about 1.3k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 663 words of instructions outside code blocks.

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

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 finos/legend-engine at commit e60ab67, republished under its Apache-2.0 licence (© finos). 663 words, ~1,318 tokens.

Download SKILL.mdSave it as .claude/skills/pure-lsp-connect/SKILL.md (or your agent's skills folder).
name
pure-lsp-connect
description
Attaches the pure-lsp HTTP bridge to an LSP daemon that is ALREADY running (e.g. started from IntelliJ, or left over from a prior session) - never spawns a new daemon JVM. Defaults to socket port 9100. Use for 'connect to the existing/already-running LSP', 'attach the bridge to the LSP on port X', or 'reconnect to the LSP' - as opposed to pure-lsp-launch-engine, which boots a new session. Also recovers a bridge whose connection has gone stale (health OK, requests fail with a broken pipe).

Connect the bridge to an already-running LSP daemon

Booting a fresh session and attaching to one already up are different intents, and conflating them is risky when the user only wants the latter: the wrong branch can end up launching a second multi-GB JVM alongside one already running. This skill is scoped to exactly one job: get the lightweight Python bridge talking to a daemon that already exists, and never touch the daemon/JVM itself unless explicitly told to.

Run the script

All the decision logic (is a daemon listening, is a bridge already attached, is it actually healthy, recover-vs-relaunch-vs-abort) is implemented deterministically in bin/pure-lsp-connect — run it rather than re-deriving these steps by hand:

bash
pure-lsp-connect [--socket-port N] [--project NAME] [--bridge-port N] [--java PATH]
  • --socket-port defaults to 9100 (this user's standing convention for LegendLspServer, configured via legendLspServerConfig.json's "port" field).
  • --project selects which project's repo-roots/classpath to launch with if no bridge is attached yet (passed through to pure-lsp-roots/pure-lsp-classpath); omit it to let those infer from $PURE_DEV_PROJECT or the current directory.
  • --bridge-port picks the bridge's own HTTP port; omit it to auto-pick the first free port starting at 8991.

On success it prints one JSON line to stdout and exits 0:

json
{"bridgeHttpPort": 8991, "socketPort": 9100, "state": "ready", "repositoryCount": 143, "symbolCount": 40756}

Hand bridgeHttpPort off to pure-lsp-check/pure-lsp-go — both take the bridge's HTTP port, not the daemon's socket port.

Exit codes:

  • 2 — nothing listening on --socket-port. Stop and tell the user to start the daemon (e.g. their IntelliJ "Legend LSP Server" run/debug config), or ask them to run pure-lsp-launch-engine if they want a brand-new session instead. Do not scan a wide port range speculatively, and do not fall back to a boot flow on your own initiative — that's the one judgment call this skill still leaves to you, not the script.
  • 3 — a bridge is up but didn't reach a healthy/ready state; the script already tried the one known automatic recovery (see below) and it didn't work. Read the diagnostic on stderr rather than guessing further — it includes the raw /status error body, since pure-lsp status's own error message hides the response body.
  • 4 — safety abort: a launch attempt didn't show a reconnect to the existing daemon in its log within the timeout, which would otherwise risk a second multi-GB JVM coming up. The script already killed the errant bridge process before returning this code. If you see this, stop and investigate (wrong socket port is the most likely cause) rather than retrying blindly.
Show full SKILL.md (274 more words)Show less

What the script automates (context if you need to debug it)

  1. Verifies something is actually listening on the socket port (/dev/tcp probe) before doing anything else — this is the hard boundary that keeps the skill from ever booting a daemon itself.
  2. Checks for an existing bridge by confirming every pgrep candidate against /proc: it must be a python process actually running -m pure_lsp_bridge.server_cli with the requested --socket-port. A bare pgrep -f is not enough — it matches the invoking shell's own command line too (observed doing exactly that), and pure-lsp-restart SIGKILLs what this returns. A looser pattern like pure.lsp would also regex-match the - in legend-pure-lsp-server inside the daemon JVM's classpath and dump 100+KB of noise. Shared helper: bin/pure-lsp-common.
  3. If found, verifies it's actually healthy (health + status). If status fails, fetches the raw error body directly (bypassing the CLI's generic "HTTP Error 500") and checks for a broken-pipe shape — the bridge's persistent socket to the daemon died underneath it, commonly because the daemon JVM had a debugger attached and sat paused at a breakpoint long enough to time out. Recovery is to kill only the bridge process (captured exact argv, never the daemon PID) and relaunch it with that same command line.
  4. If no bridge is attached, resolves repo-roots/classpath/server-jar (via resolve_lsp_server_jar in pure-lsp-common — extracted from the target project's own classpath, or borrowed from legend-engine's if the project's own classpath doesn't carry it) and launches one against the confirmed-listening socket port, then verifies the launch log actually shows a reconnect (connected to EXISTING LSP daemon) before declaring success — aborting and killing the process otherwise, rather than letting an unexpected fresh boot slide by.

© finos, 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 plugins/pure-dev/skills/pure-lsp-connect of finos/legend-engine.

Open the folder on GitHubat commit e60ab67

Compare with similar skills

Pure Lsp Connect 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.

Pure Lsp Connect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pure Lsp Connect this skillfinos/legend-engine113—~1.3kAutomated safety check: PassApache-2.0
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Evals Contextzgsm-ai/costrict4.5k1 repos~1.9kAutomated safety check: PassApache-2.0
ChangelogJetBrains/ideavim10k1 repos~2.7kAutomated safety check: PassMIT
Youtrack CommunityJetBrains/intellij-community21k—~3.2kAutomated safety check: NotesCustom licence
Compose Multiplatform Patternsmonta-app/ocpp-emulator1805 repos~2kAutomated safety check: PassApache-2.0

Similar skills

  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Evals Context

    zgsm-ai/costrict

    Provides context about the CoStrict evals system structure in this monorepo.

    4.5k GitHub starsUsed in 1 repo~1.9k tokens
    AI & LLM EngineeringAuto-check passed

  • Changelog

    JetBrains/ideavim

    Official

    Maintains the IdeaVim changelog (CHANGES.md). An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

  • Youtrack Community

    JetBrains/intellij-community

    Official

    YouTrack CLI for a community checkout; the monorepo uses youtrack.

    21k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check: notes

  • Compose Multiplatform Patterns

    monta-app/ocpp-emulator

    Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.

    180 GitHub starsUsed in 5 repos~2k tokens
    MobileAuto-check passed

  • Compare Python Typecheckers

    JetBrains/intellij-community

    Official

    Compare Python type inference with ty, pyrefly, and basedpyright.

    21k GitHub stars~617 tokensUpdated today
    Auto-check passed

More from finos/legend-engine

All 15 skills in this repo

  • Pure Backend Start

    finos/legend-engine

    Starts (or confirms) the standalone legend-engine backend - engine Server + H2 + local metadata server on fixed ports 9095/9092 - so a Pure LSP started with -Dlegend.test.

    113 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Pure Chain Update

    finos/legend-engine

    Procedure for git-syncing and rebuilding a local legend-pure + legend-engine checkout, in dependency order, with pinned dependency versions resynced.

    113 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Pure Code Style

    finos/legend-engine

    Reformats a .pure file (or a block of Pure code) to a consistent house style: 2-space indentation with no column-aligned hanging indents, tight colons in type annotations, spaced pipes on…

    113 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Pure Lsp Check

    finos/legend-engine

    Compiles/checks a single .pure file against the already-running Legend Pure LSP bridge and reports diagnostics (errors/warnings) in under a second, as a fast alternative to a full mvn test/mvn…

    113 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Pure Lsp Execute

    finos/legend-engine

    Runs exactly ONE existing Pure function by path (signature, mangled id or bare path) through the running Legend Pure LSP bridge, without a go() wrapper, and returns its typed value in returnValue.

    113 GitHub stars~883 tokensUpdated today
    Auto-check passed

  • Pure Lsp Execute Parallel

    finos/legend-engine

    Runs 2 to 30 Pure functions or tests concurrently on the warm LSP daemon via pure-lsp execute-parallel, or every test in a package or .pure file with --package/--source.

    113 GitHub stars~927 tokensUpdated today
    Auto-check passed

Works with

Questions about Pure Lsp Connect

What does Pure Lsp Connect do?

Attaches the pure-lsp HTTP bridge to an LSP daemon that is ALREADY running (e.g. Pure Lsp Connect is an agent skill from finos/legend-engine.g.

When should I use Pure Lsp Connect?

Pure Lsp Connect fits situations like: connect to the existing/already-running LSP; attach the bridge to the LSP on port X; reconnect to the LSP - as opposed to pure-lsp-launch-engine; which boots a new session.

How do I install Pure Lsp Connect in Claude Code?

Run `npx skills add finos/legend-engine --skill pure-lsp-connect -a claude-code`. Or copy the skill folder (plugins/pure-dev/skills/pure-lsp-connect in finos/legend-engine) into .claude/skills/pure-lsp-connect in your project. Claude Code loads it when a task matches its description.

How do I install Pure Lsp Connect in Codex?

Run `npx skills add finos/legend-engine --skill pure-lsp-connect -a codex`. Or copy the skill folder (plugins/pure-dev/skills/pure-lsp-connect in finos/legend-engine) into .agents/skills/pure-lsp-connect in your project. Codex loads it when a task matches its description.

Can I use Pure Lsp Connect 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 finos/legend-engine --skill pure-lsp-connect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pure-lsp-connect, .gemini/skills/pure-lsp-connect, .github/skills/pure-lsp-connect and .opencode/skills/pure-lsp-connect in your project.

What does Pure Lsp Connect need to run?

SKILL.md names no scripts, command-line tools or credentials: Pure Lsp Connect is instructions for the agent only. Our summary lists: Python 3.

Does Pure Lsp Connect 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 Pure Lsp Connect 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 Pure Lsp Connect use?

Pure Lsp Connect 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 Pure Lsp Connect use?

About 1.3k tokens (SKILL.md is roughly 5.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 Pure Lsp Connect?

Skills that share tags, products or a category with Pure Lsp Connect: Doc Sync (JetBrains/ideavim, 10k stars), Evals Context (zgsm-ai/costrict, 4.5k stars), Changelog (JetBrains/ideavim, 10k stars) and Youtrack Community (JetBrains/intellij-community, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pure Lsp Connect?

finos (a GitHub organization) maintains it in finos/legend-engine, which has 113 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 10, 2026.

Source: finos/legend-engine on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.