计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
retrieval-vectorstores【效率与协作】Guides DocsGPT embeddings, vector-store selection, per-source retrieval, classic and hybrid RAG, pre-screening, GraphRAG, and retrieval diagnosis.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill to select embeddings/vector storage, configure per-source retrieval, tune ranking, enable GraphRAG, or diagnose missing/poor context.
At this snapshot, VectorCreator accepts:
faiss, elasticsearch, mongodb, qdrant, milvus, pgvector
Retriever keys are:
classic, default, hybrid, graphrag
default maps to classic behavior. A source retriever must also be allowed by RETRIEVERS_ENABLED.
A LanceDB implementation/settings surface exists in the codebase but is not registered in VectorCreator at this snapshot. Do not claim that VECTOR_STORE=lancedb works without verifying a newer checkout or adding/validating registration.
Record current embedding model/endpoint and actual vector dimension.
Record selected vector store, source count, chunk count and backup/export path.
Define target retrieval behavior per source.
Validate feature compatibility offline:
python scripts/validate_retrieval_plan.py \
--vector-store pgvector \
--retriever hybrid
Test one tiny source and expected query.
Re-ingest when embeddings, vector dimensions, chunking, or GraphRAG extraction inputs changed.
Compare retrieval results and citations before removing old data.
score_threshold is honored by pgvector and MongoDB Atlas; other stores may ignore it.VECTOR_STORE=pgvector and GRAPHRAG_ENABLED=true; enable it through the dedicated source action.For a representative query, record:
Do not diagnose answer quality until proving whether the expected chunks reached the model.