Diagnose RAG pipeline failures by locating the failing stage and root cause.
npx skills add https://github.com/ql-link/LinkRag --skill incident-triage-ql-link
Please help me install this Agent Skill. Skill: incident-triage Source: https://github.com/ql-link/LinkRag/tree/main/.ai/skills/incident-triage Command: npx skills add https://github.com/ql-link/LinkRag --skill incident-triage-ql-link
This skill standardizes fault triage for the RAG parsing and recall pipeline, enabling engineers to quickly locate the failing stage and determine root causes.
Provide a step-by-step triage guide by reviewing parse_task_consumer, pipeline stages, and config files to identify the failing segment and recommended fixes.
High-intent search queries and answers about installing and using this skill.
To triage RAG pipeline failures, map the parse_task errors to the specific six-stage pipeline segment and classify the root cause as configuration drift, data inconsistency, code defect, or external dependency to determine the exact failing stage.
MQ consumption stalls in the RAG pipeline occur due to configuration drift, data inconsistency, code defects, or external dependency failures. Running a standardized fault triage on the consumer logs and config files isolates the exact stage and determines the necessary recovery action.
The best way to resolve Qdrant or Elasticsearch errors during RAG recall is to run a standardized fault triage that locates the failing segment and provides actionable fixes including configuration adjustments, code corrections, or data resets with safety checks.
Yes, you can get actionable fix steps for data inconsistency issues in a RAG pipeline. The triage process identifies the root cause and provides concrete remediation actions, including data reset and recovery procedures with repeatable steps to restore pipeline health.
Yes, RAG fault triage works for both configuration drift and external dependency outages. It classifies the root cause across the parsing and recall pipeline stages and provides targeted recovery actions to address the specific failure type.
To locate the exact failing stage in a stalled RAG pipeline, review the parse_task consumer, the six-stage pipeline flow, and configuration files. This step-by-step triage identifies the failing segment and recommends the appropriate fixes.
patrobRun parallel hypotheses to isolate root causes and require failing tests before patching.
OneWave-AIAnalyze CRM pipeline data to flag stalled deals and forecast revenue risk.
ql-linkIntegrate and orchestrate Kafka and RabbitMQ messaging for the toLink-Rag platform.
devendrapratapsinghDiagnose distributed system failures through log analysis and distributed tracing.
