Run RAG chatbot workflows with Verba
Ingest a bounded document set into Verba, configure retrieval and model providers, then review grounded chatbot answers before handing context to an agent workflow.
npx skills add agentskillexchange/skills --skill run-rag-chatbot-workflows-with-verba
Use Verba when an operator needs a repeatable RAG chatbot workspace for exploring a specific dataset before summarization, support-answer drafting, retrieval QA, or agent context handoff. The workflow is to install or deploy Verba, configure the Weaviate backing store and model/provider keys, ingest an explicit corpus, test representative questions, inspect retrieved context and answer quality, then decide whether the dataset is ready for downstream agent use. Invoke this instead of using a generic hosted chatbot when the work needs a local or controlled RAG environment with visible ingestion, retrieval settings, source documents, and reviewable answers. Keep the corpus, provider choices, and test questions recorded so later reviewers can reproduce the run. The scope boundary is document ingestion, retrieval configuration, and answer review for a named corpus. It is not a generic Weaviate listing, an autonomous agent framework, or an unsupervised ingestion pipeline for arbitrary private documents.
What this skill actually does
Inputs and prerequisites: Verba, Python 3.10 through 3.12 or Docker, Weaviate embedded/cloud/Docker deployment, configured model and embedding provider keys as needed..
Setup notes: Install with `pip install goldenverba`, optionally create a `.env` file with only the provider keys you intend to use, then run `verba start`. For Docker, clone https://github.com/weaviate/Verba and run `docker compose –env-file up -d –build`.
Source and verification boundary: use https://github.com/weaviate/Verba as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.