advanced-query

Design RAG queries with mandatory citation attribution and chunk-level provenance.

2|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Agentient/vibekit --skill advanced-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advanced-query
Source: https://github.com/Agentient/vibekit/tree/main/plugins/rag-tools/skills/advanced-query
Command: npx skills add https://github.com/Agentient/vibekit --skill advanced-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Advanced planning and design for retrieval-augmented queries with strict citation provenance to enable traceable sources and chunk-level metadata across results.

Core Features & Use Cases

  • Citation-aware querying: tracks source URIs, chunk IDs, offsets, and confidence metrics to preserve provenance.
  • Provenance-driven ranking: supports result ranking and filtering with attribution.
  • Use Case: multi-document QA tasks requiring traceable sources across documents.

Quick Start

Outline and implement the planned RAG query patterns with mandatory citation attribution when ready.

Frequently Asked Questions about advanced-query

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

FAQPage Schema
How do I add citation attribution to RAG queries for multi-document retrieval?

To add citation attribution to RAG queries, you design retrieval patterns that track source URIs, chunk identifiers, and offsets. This preserves provenance and ensures traceable sources across multi-document knowledge bases.

What is provenance-driven ranking in retrieval-augmented generation?

Provenance-driven ranking in retrieval-augmented generation filters and ranks results based on source attribution metadata. It uses confidence metrics and chunk tracking to ensure retrieved answers map to traceable origins.

How do I track chunk IDs and source mapping in a RAG pipeline?

You track chunk IDs and source mapping by implementing retrieval queries with mandatory citation metadata. This requires defining input and output contracts that preserve chunk-level identifiers and source URIs throughout the pipeline.

Does this Skill require specific dependencies for citation-aware querying?

Citation-aware querying does not require specific external dependencies to design the query patterns. You integrate the planned retrieval contracts and attribution metadata directly into your existing RAG pipeline.

What's the best way to structure input and output contracts for RAG provenance?

The best way to structure contracts for RAG provenance is to define schemas that enforce mandatory citation attribution. These contracts specify chunk identifiers, confidence metrics, and source URIs to maintain strict traceability.

Why is my RAG pipeline losing source attribution during multi-document retrieval?

Your RAG pipeline loses source attribution when queries lack mandatory citation metadata and strict provenance tracking. Designing queries with chunk identifiers and confidence metrics prevents this loss across documents.