rag-mcp-lsp-ops

Manage RAG, MCP, and LSP operations for code context retrieval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill streamlines complex RAG, MCP, and LSP operations, ensuring semantic tooling is ready for coding workflows and diagnosing system availability.

Core Features & Use Cases

  • Runtime Preflight: Verifies and prepares essential services like PM2 and MCP.
  • RAG Rebuilding: Handles full or partial rebuilding and indexing of the RAG system.
  • Tooling Validation: Diagnoses MCP availability and validates semantic tools for coding tasks.
  • Use Case: Before starting a deep coding session that requires semantic understanding, use this skill to ensure your RAG index is up-to-date and your language server is functioning correctly.

Quick Start

Use the rag-mcp-lsp-ops skill to rebuild the RAG index from zero.

Frequently Asked Questions about rag-mcp-lsp-ops

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

FAQPage Schema
How do I rebuild a RAG index from scratch for semantic code search?

To rebuild a RAG index from scratch, use the designated npm scripts to trigger a full indexing process with configurable profiles and document modes, ensuring your code context retrieval system is fully refreshed and ready for semantic navigation.

Why is my MCP server not available for coding workflows?

If your MCP server is not available, run the built-in MCP diagnostics npm scripts to diagnose system availability and validate semantic tooling readiness before attempting to start your coding session.

What is the best way to verify PM2 and MCP availability before a deep coding session?

The best way to verify PM2 and MCP availability is to execute a runtime preflight check using specific npm daemon control scripts, ensuring essential services are brought online and functioning correctly for your workflow.

Can I do a partial rebuild of the RAG system instead of a full reindex?

Yes, you can perform a partial rebuild of the RAG system using configurable profiles and document modes, allowing you to update the semantic index without needing to rebuild the entire codebase from zero.

When do I need to validate semantic tooling readiness for my development environment?

You need to validate semantic tooling readiness before starting a deep coding session that requires semantic understanding, ensuring your RAG index is up-to-date and your language server is functioning correctly for accurate code context retrieval.

Do I need specific npm scripts to manage PM2 daemon control and RAG operations?

Yes, managing PM2 daemon control, diagnosing MCP availability, and executing RAG indexing requires specific npm scripts designed to handle daemon control, system diagnostics, and configurable document indexing modes.