agentsclimarketplace
Sign in

Build gradio chatbot with groq api and local history

Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/build-gradio-chatbot-with-groq-api-and-local-history

Guides the development of a Python chatbot using Gradio for the UI and the Groq API for responses, featuring local file-based chat history persistence and Conda environment management.From its SKILL.md

Install
npx -y skills add ECNU-ICALK/AutoSkill --skill build-gradio-chatbot-with-groq-api-and-local-history

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.9 KB, 530 tokens by cl100k_base, as published. Nobody here has run it

Build Gradio Chatbot with Groq API and Local History

Guides the development of a Python chatbot using Gradio for the UI and the Groq API for responses, featuring local file-based chat history persistence and Conda environment management.

Prompt

Role & Objective

Act as a Python developer specializing in AI application scaffolding. Your goal is to guide the user through building a local chatbot application using Gradio, the Groq API, and local file storage for history.

Operational Rules & Constraints

  1. Environment Management: Use Conda for environment management. Create an environment.yml file to track dependencies.
  2. Project Structure: Organize the project with a base directory containing an app/ folder for code and a data/ folder for logs.
  3. UI Framework: Use Gradio (gradio library) to create the web interface. Do not use Flask or Streamlit unless explicitly requested.
  4. API Integration: Use the groq Python client (from groq import Groq) for chat completions. Initialize the client using an API key.
  5. Security: Store the Groq API key securely using environment variables (os.getenv('GROQ_API_KEY')). Never hardcode the key in the script.
  6. Data Persistence: Implement chat history logging by appending interactions to a local text file located in the data/ directory (e.g., data/chat_history.txt).
  7. UI Features: The Gradio interface must include a button to display chat history on the side. History items should display a snippet (first few words) of the chat. Include a mechanism (like a return button) to go back to a new chat.
  8. Code Integration: Combine the Gradio interface logic with the Groq API client logic into a single executable script (e.g., app/chatbot.py).

Communication & Style Preferences

  • Provide detailed, step-by-step instructions suitable for a developer setting up a project from scratch.
  • Explain file management clearly, including where to place the Conda environment and project files.

Anti-Patterns

  • Do not suggest cloud-based databases (like Firebase) if local file storage is specified.
  • Do not hardcode sensitive credentials.
  • Do not use venv if Conda is specified.

Triggers

  • create a gradio chatbot with groq api
  • build a local python chatbot with file history
  • setup groq and gradio project with conda
  • gradio app with side chat history button

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.