public-qa-chatbot

Build unauthenticated public Q&A chatbot widgets with rate limiting and semantic caching.

154|9|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/swyxio/skills --skill public-qa-chatbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-qa-chatbot
Source: https://github.com/swyxio/skills/tree/main/public-qa-chatbot
Command: npx skills add https://github.com/swyxio/skills --skill public-qa-chatbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Public-facing chatbot widgets deployed without guardrails quickly exhaust API quotas, leak internal data, or deliver poor user experiences during long conversations. This Skill distills production-tested patterns for rate limiting, security hardening, cost control, observability, and chat scroll behavior so you can serve anonymous visitors safely.

Core Features & Use Cases

  • Rate Limiting & Security: Multi-layer rate limits, origin validation, input size caps, and BYOK fallbacks protect against abuse and quota exhaustion.
  • Cost Optimization: Semantic caching, cheap model selection, and short output limits keep LLM costs predictable for FAQ-style bots.
  • Agentic Retrieval: Optional virtual filesystem tools let the model browse documentation with ls, cat, and grep-style commands instead of relying solely on top-k RAG.
  • UX Patterns: Draggable windows, streaming responses, TanStack Virtual chat lists, bottom command shelves, and theme-aware styling create polished widget experiences.

Quick Start

Use the public-qa-chatbot skill to build an unauthenticated public Q&A chatbot widget with rate limiting, semantic caching, and virtualized chat scrolling for your conference or documentation site.

Frequently Asked Questions about public-qa-chatbot

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

FAQPage Schema
How do I build a public chatbot widget that prevents API quota exhaustion from anonymous users?

Yes, you can serve anonymous visitors safely by using semantic caching and cheap model selection for cost optimization. Semantic caching retrieves similar past answers to reduce LLM calls, keeping expenses predictable for FAQ-style bots.

Does the chatbot use top-k RAG or a virtual filesystem for documentation retrieval?

The chatbot uses an optional virtual filesystem for agentic retrieval instead of relying solely on top-k RAG. This allows the model to browse documentation using ls, cat, and grep-style commands to ensure source-grounded answers.

What's the best way to implement streaming responses in a chatbot without performance issues?

The best way to implement streaming responses without performance issues is using TanStack Virtual for chat lists. This approach virtualizes long conversation scrolling, ensuring polished widget UX during continuous LLM streaming.

Can I deploy an unauthenticated LLM chatbot on a marketing site without risking internal data leakage?

Limitations of using a public Q&A chatbot without observability tracing include poor user experiences during long conversations and untracked costs. Without tracing, you cannot monitor semantic cache hits or enforce rate limiting effectively.