agency-lsp-index-engineer

Orchestrate multiple Language Server Protocol clients into a unified semantic code graph.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/anavvanzin/Research --skill agency-lsp-index-engineer-anavvanzin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-lsp-index-engineer
Source: https://github.com/anavvanzin/Research/tree/main/cowork/integrations/antigravity/agency-lsp-index-engineer
Command: npx skills add https://github.com/anavvanzin/Research --skill agency-lsp-index-engineer-anavvanzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multiple Language Server Protocol clients to build a cohesive semantic graph of code entities, enabling unified navigation and analysis across languages.

Core Features & Use Cases

  • LSP orchestration: manage multiple language servers concurrently and negotiate capabilities.
  • Semantic graph: transform LSP responses into a unified graph with nodes (files, symbols) and edges (contains, references, calls).
  • Real-time updates: incremental graph updates via file watching and Git hooks for immediate feedback.
  • Performance targets: sub-500ms responses for definitions, references, and hover data across large repos.
  • Use cases: polyglot codebases requiring cross-language symbol resolution and cross-file navigation.

Quick Start

Install required LSP servers and initialize the LSP orchestrator for your project root.

Frequently Asked Questions about agency-lsp-index-engineer

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

FAQPage Schema
How do I build a unified semantic code index across a polyglot codebase?

To build a unified semantic code index, you orchestrate multiple Language Server Protocol clients to construct a cohesive graph of code entities, enabling cross-language symbol navigation and analysis.

What is the best way to get real-time symbol definitions and references in large repositories?

The best way to achieve real-time symbol definitions is using incremental graph updates via file watching and Git hooks, maintaining sub-500ms response latency for queries across large repositories.

Can I use LSP orchestration to manage multiple language servers concurrently?

Yes, LSP orchestration manages multiple language servers concurrently by negotiating capabilities and transforming LSP responses into a unified graph with nodes for files and symbols.

How do I set up a semantic graph for cross-language code intelligence?

To set up a semantic graph, install required LSP servers and initialize the LSP orchestrator for your project root to map references, calls, and symbol containment across languages.

Does this semantic index approach work with TypeScript, PHP, Go, Rust, and Python?

Yes, this semantic index approach applies directly to polyglot codebases using TypeScript, PHP, Go, Rust, and Python, providing cross-language symbol resolution and cross-file navigation.

Why does LSP protocol compliance matter for scalable symbol indexing?

LSP protocol compliance matters for scalable symbol indexing because it standardizes communication across language servers, enabling a persistent cache and consistent low-latency queries.