/build-kb-assistant
Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V. ✓ Copied. Switch to Claude and paste — ⌘/Ctrl+V.
/build-kb-assistant
Welcome to the RBA Knowledge Base Assistant Builder. I'll ask a few questions to understand what you're building and route you to the right skill — or run the full sequence if you're starting a new assistant from scratch.
Intake questions
Ask these in order. Stop when you have enough to recommend a route.
What is the assistant for?
- Internal employee knowledge base (HR policies, IT procedures, project methodology)?
- Client-facing product assistant (documentation, FAQs, support knowledge)?
- Project team assistant (SOW templates, retrospective knowledge, delivery methodology)?
- Something else?
Where does the source content live?
- SharePoint / Microsoft 365
- Sitecore XM Cloud (content export)
- Optimizely CMS (Content Delivery API)
- Umbraco (Content Delivery API)
- Azure Blob Storage / document library
- Local file system (PDFs, DOCX, PPTX)
- Multiple sources (which?)
Where will the assistant be deployed?
- Microsoft Teams bot
- Web chat widget (embedded iframe)
- Copilot Studio custom connector
- Claude plugin (OpenAPI tool)
- All of the above / not yet decided
Where are you in the build process?
- Starting from scratch — no index, no pipeline
- Index exists — need to design the retrieval pipeline
- Pipeline running — need to evaluate quality before launch
- Evaluation passed — need to package and deploy
- Already live — need an operations runbook
- Doing a quality review of an existing deliverable
Any security requirements?
- Content has row-level permissions (SharePoint library permissions, CMS security roles)?
- Entra ID authentication required for the assistant UI?
- Any compliance requirements (data residency, sensitivity labels)?
Routing
Based on the answers, invoke the appropriate skill or sequence:
| Starting point | Skills to invoke (in order) |
|---|---|
| Starting from scratch | kb-source-ingestion → kb-rag-pipeline-architect → kb-qa-evaluator → kb-assistant-packager → kb-deployment-runbook |
| Index exists, no pipeline | kb-rag-pipeline-architect → kb-qa-evaluator → kb-assistant-packager |
| Pipeline running, pre-launch | kb-qa-evaluator → kb-assistant-packager → kb-deployment-runbook |
| Evaluation passed | kb-assistant-packager → kb-deployment-runbook |
| Already live, need runbook | kb-deployment-runbook |
| Quality gate review | kb-quality-reviewer agent |
| Content source planning only | kb-source-ingestion |
| RAG architecture design only | kb-rag-pipeline-architect |
Full sequence (starting from scratch)
If the user is starting a new assistant from scratch, run the skills in this order:
kb-source-ingestion— audit content sources, design chunking strategy, produce index schemakb-rag-pipeline-architect— design retrieval strategy, write system prompt, generate Bicep stubskb-qa-evaluator— generate golden question set, score faithfulness/relevance, confirm PASS gatekb-assistant-packager— generate production Bicep, Teams manifest, OpenAPI definition, handover dockb-deployment-runbook— write day-2 ops runbook, re-ingestion procedures, escalation pathskb-quality-revieweragent — final gate review before client handover
Estimated time per skill: 10–20 minutes per deliverable depending on content complexity.
Technical details
- Source
- kb-assistant-builder
- Author
- Dakota Smith
- Invocation
/build-kb-assistant- Maturity
- experimental
- Security review
- No security review
- Owners
-
- delivery
- File
plugins/kb-assistant-builder/commands/build-kb-assistant.md
Edit this command on GitHub — opens GitHub's web editor. No git knowledge needed.