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 Launch Engine

by finos in finos/legend-engine

Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'.

Apache-2.0Auto-check passed

Install Pure Lsp Launch Engine

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

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

GitHub CLI
$ gh skill install finos/legend-engine pure-lsp-launch-engine --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-launch-engine .claude/skills/pure-lsp-launch-engine && 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-launch-engine
GitHub stars
113
Token cost
~1.4k tokens
SKILL.md length
695 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'.

  • The user wants to start/launch/boot the Pure LSP for legend-engine with nothing unusual - unlike pure-lsp-connect
  • SKILL.md covers Run the script, It backgrounds itself, waits… and Then
  • Calls git
  • Which attaches to a daemon that is already running

What it does

Pure Lsp Launch Engine is an agent skill from finos/legend-engine. Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'. Brings the backend engine Server up by default so execute()/go() use real plan-generation; --no-backend opts out. Use when the user wants to start/launch/boot the Pure LSP for legend-engine with nothing unusual - unlike pure-lsp-connect, which attaches to a daemon that is already running.

Its SKILL.md is about 1.4k 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 Java. The licence is Apache-2.0.

When your agent uses it

  • The user wants to start/launch/boot the Pure LSP for legend-engine with nothing unusual - unlike pure-lsp-connect
  • Which attaches to a daemon that is already running

Example prompts

  • “just start the LSP for legend-engine”
  • “Use the pure-lsp-launch-engine skill to launch the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just…”
  • “/pure-lsp-launch-engine”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 43f4e69. 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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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 Launch Engine loads about 1.4k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 695 words of instructions outside code blocks.

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

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 43f4e69, republished under its Apache-2.0 licence (© finos). 695 words, ~1,443 tokens.

Download SKILL.mdSave it as .claude/skills/pure-lsp-launch-engine/SKILL.md (or your agent's skills folder).
name
pure-lsp-launch-engine
description
Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'. Brings the backend engine Server up by default so execute()/go() use real plan-generation; --no-backend opts out. Use when the user wants to start/launch/boot the Pure LSP for legend-engine with nothing unusual - unlike pure-lsp-connect, which attaches to a daemon that is already running.

Launch the Pure LSP for legend-engine (defaults baked in)

The real entrypoint for the common case: legend-engine-scoped LSP, backend engine Server on by default, no per-run decisions. A thin wrapper over pure-lsp-launch legend-engine; for a scope the project registry doesn't describe, build the pure-lsp-server command by hand per references/lsp-devloop-internals.md.

Run the script

bash
pure-lsp-launch-engine [--port N] [--socket-port N] [--java PATH]
                       [--backend-server-host HOST] [--backend-server-port N] [--no-backend]
                       [--source legend-pure] [--full-source]
                       [extra args passed through to pure-lsp-server, e.g. --jvm-arg=-D...]

Defaults: --port 8991, --socket-port 9100 (this shop's standing convention for LegendLspServer, shared with pure-lsp-connect/pure-lsp-restart's default), --java = plain java on PATH (JDK 11). $LEGEND_ENGINE_ROOT defaults to the checkout containing the current directory. Only legend-engine is source-rooted; legend-pure comes from the classpath jar and needs no checkout or $LEGEND_PURE_ROOT. Add --source legend-pure to edit platform .pure live too (needs $LEGEND_PURE_ROOT), or --full-source for the whole chain.

Backend is on by default. If nothing's listening on 127.0.0.1:9095 the script runs pure-backend-start itself and wires the resulting -Dlegend.test.server.* jvm-args in, so execute()/go() take the real plan-gen path. --no-backend gives a plain interpreted session. A failed backend start aborts the launch rather than silently degrading to interpreted — so if you want interpreted, ask for it explicitly.

Whenever the backend is wired in, ExecPlan/PlanLocal/FullInteractiveExec also default to true — the same "3 trues" legendLspServerConfig.json sets for the engine-side config-driven launcher of this same daemon. Plan-gen then runs locally against the live graph rather than the backend's own jars, so a Pure-only edit is reflected immediately with no jar rebuild. Override any of them with a trailing --jvm-arg=-Dpure.options.X=... — it lands after these defaults and wins.

Since the daemon it starts is on a fixed socket port, re-running this after a daemon on that port is already up reconnects to the existing warm session (via pure-lsp-server's own reconnect logic — the same behavior pure-lsp-connect relies on) rather than double-booting a second JVM.

If a bridge is already listening on the HTTP port, this script refuses to launch and exits 0 after printing that bridge's /health (repo-roots, jvm-args, socket port) so you can see whether it is the session you wanted. It does not try to start a second one: the bridge binds its HTTP port before doing anything else, so a second launch dies instantly on Address already in use — and this script would then poll that same port, get the EXISTING bridge's ready, and report a successful launch while the configuration you just asked for was silently discarded. To run a second independent session pass a free --port/--socket-port; to rebuild this one use pure-lsp-restart --socket-port 9100.

Show full SKILL.md (296 more words)Show less

It backgrounds itself, waits for ready, and warms welcome.pure — then returns

Unlike a bare pure-lsp-server call this does not block your terminal. It launches the bridge fully detached (setsid nohup ... & disown, so a process-group teardown can't reap it), polls pure-lsp status until ready/failed, then pushes and compiles legend-engine's own welcome.pure ($LEGEND_ENGINE_ROOT/welcome.pure) into the session overlay via pure-lsp check — not go, so it's compiled and go()-ready but never executed — before printing a final summary and exiting. You get your shell prompt (or tool call) back immediately with the bridge already running and warmed, no separate verification call needed.

If welcome.pure doesn't exist yet, a minimal go():Any[*] wrapper is created for you — but only when legend-engine's checkout actually .gitignores it (true today), so this never leaves an untracked file a later git add -A could sweep into a commit. If the checkout stopped ignoring it, the launcher skips creation and tells you to add the ignore rule yourself.

Exit codes: 0 ready and warmed (or welcome.pure missing/failed to compile — that's a non-fatal warning printed to stderr, not a failure, since the LSP itself is still usable), 1 bad args or missing server jar/dependency dir, 3 the bridge never reached ready (or reported failed) within the timeout — see the two log paths it prints.

Two separate logs, one writer each: /tmp/pure_lsp_bridge_8991.log (the Python bridge — argument errors, classpath resolution, bind failures) and /tmp/pure_lsp_server_8991.log (the LSP daemon JVM's own output). They used to be one file written by both, which meant a relaunch truncated the log out from under the still-running daemon.

Then

The shared dev-loop conventions (talking to the bridge, welcome.pure, database setup) are in references/lsp-devloop-usage-rules.md.

Hand the resolved --port off to pure-lsp-check/pure-lsp-go/pure-lsp status for the actual compile/execute work — go() is already warmed and ready to run against welcome.pure immediately.

© 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-launch-engine of finos/legend-engine.

Open the folder on GitHubat commit 43f4e69

Compare with similar skills

Pure Lsp Launch Engine 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 Launch Engine compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pure Lsp Launch Engine this skillfinos/legend-engine113—~1.4kAutomated safety check: PassApache-2.0
Brainstormingxpinjection/test-driven-spring-boot11254 repos~2.6kAutomated safety check: PassMIT
Android API Diffgkd-kit/gkd43k—~796Automated safety check: PassGPL-3.0
Video Cover Imageitwanger/toBeBetterJavaer18k—~3.3kAutomated safety check: PassNone
Lancedb Update Lance Dependencylancedb/lancedb12k—~1.1kAutomated safety check: PassApache-2.0
Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk11k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Brainstorming

    xpinjection/test-driven-spring-boot

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.

    112 GitHub starsUsed in 54 repos~2.6k tokens
    Agent WorkflowsAuto-check passed

  • Android API Diff

    gkd-kit/gkd

    Looks up Android framework Java and AIDL APIs across versions with the android-api-diff CLI: signatures, availability, source files and hidden-API access code.

    43k GitHub stars~796 tokensUpdated yesterday
    MobileAuto-check passed

  • Video Cover Image

    itwanger/toBeBetterJavaer

    Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics.

    18k GitHub stars~3.3k tokensUpdated yesterday
    Media & CreativeAuto-check passed

  • Lancedb Update Lance Dependency

    lancedb/lancedb

    Update LanceDB to a specific Lance release or tag. An agent skill from lancedb/lancedb.

    12k GitHub stars~1.1k tokensUpdated today
    DatabasesAuto-check passed

  • Java SDK E2E Test with Replay Snapshot

    github/copilot-sdk

    Official

    Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.

    11k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Fory Release

    apache/fory

    Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.

    4.6k GitHub stars~2.9k tokensUpdated yesterday
    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 Connect

    finos/legend-engine

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

    113 GitHub stars~1.3k 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

Works with

Questions about Pure Lsp Launch Engine

What does Pure Lsp Launch Engine do?

Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'. Pure Lsp Launch Engine is an agent skill from finos/legend-engine. Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'.

When should I use Pure Lsp Launch Engine?

Pure Lsp Launch Engine fits situations like: the user wants to start/launch/boot the Pure LSP for legend-engine with nothing unusual - unlike pure-lsp-connect; which attaches to a daemon that is already running.

How do I install Pure Lsp Launch Engine in Claude Code?

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

How do I install Pure Lsp Launch Engine in Codex?

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

Can I use Pure Lsp Launch Engine 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-launch-engine -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-launch-engine, .gemini/skills/pure-lsp-launch-engine, .github/skills/pure-lsp-launch-engine and .opencode/skills/pure-lsp-launch-engine in your project.

What does Pure Lsp Launch Engine need to run?

Going by SKILL.md and its folder, Pure Lsp Launch Engine needs the command-line tools its instructions call (git). Our summary lists: Python 3.

Does Pure Lsp Launch Engine access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Pure Lsp Launch Engine 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 Launch Engine use?

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

About 1.4k tokens (SKILL.md is roughly 5.8k 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 Launch Engine?

Skills that share tags, products or a category with Pure Lsp Launch Engine: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), Android API Diff (gkd-kit/gkd, 43k stars), Video Cover Image (itwanger/toBeBetterJavaer, 18k stars) and Lancedb Update Lance Dependency (lancedb/lancedb, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pure Lsp Launch Engine?

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 8, 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.