lsp-ops

Manage local TypeScript LSP wrapper operations for semantic navigation, diagnostics, and code actions.

3|1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Ilenburg1993/chatgpt-docker-puppeteer --skill lsp-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsp-ops
Source: https://github.com/Ilenburg1993/chatgpt-docker-puppeteer/tree/main/.github/skills/lsp-ops
Command: npx skills add https://github.com/Ilenburg1993/chatgpt-docker-puppeteer --skill lsp-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides guidance for managing and aligning the local TypeScript Language Server Protocol (LSP) wrapper with its canonical contract and schema definitions.

Core Features & Use Cases

  • LSP Wrapper Management: Understand and maintain the local tsserver wrapper.
  • Contract Alignment: Ensure consistency between code, schema, and skill documentation for LSP operations.
  • Use Case: When updating the LSP daemon, use this skill to verify that all supported operations are correctly documented and aligned with the defined schema.

Quick Start

Use the lsp-ops skill to confirm the daemon operation list.

Frequently Asked Questions about lsp-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage TypeScript Language Server Protocol operations for semantic navigation and diagnostics?

TypeScript LSP operations are managed by maintaining a local tsserver wrapper, which handles semantic navigation, diagnostics, and code actions while ensuring consistency with defined schema contracts.

What is the best way to align LSP daemon updates with schema definitions?

Aligning LSP daemon updates requires using validation tooling to audit the wrapper operations, ensuring all supported operations are correctly documented and match the defined schema contract.

How do I verify the operation list for a local TypeScript LSP wrapper?

Verifying the TypeScript LSP wrapper operation list involves checking the daemon's supported operations and confirming they align with the canonical contract and operational documentation.

Do I need specific validation tooling for LSP contract governance?

Yes, adhering to defined schemas and using validation tooling is required for auditing and aligning the TypeScript Language Server Protocol wrapper with its canonical contract.

Why does LSP code analysis require consistency between the daemon and documentation?

LSP code analysis requires this consistency to ensure that semantic navigation and diagnostics accurately reflect the defined schema contract, preventing operational misalignment during daemon updates.