manage-conversation-db

Implement stateless conversation persistence with async database queries and user isolation.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon --skill manage-conversation-db
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-conversation-db
Source: https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon/tree/main/.claude/skills/manage-conversation-db
Command: npx skills add https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon --skill manage-conversation-db

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to implement stateless conversation persistence for chat applications, enabling reliable loading/creation of conversations by ID and durable storage of user and assistant messages.

Core Features & Use Cases

  • Conversation Lifecycle: Create new conversations or load existing ones by ID.
  • Message Storage: Persist messages with role, content, and optional metadata (tool_name, tool_call_id).
  • History Retrieval: Fetch conversation history in chronological order for agent input.
  • Async Operations: Support non-blocking database queries to improve throughput.
  • User Isolation: Ensure conversations are scoped to a specific user_id.

Quick Start

  • Set up the database models for Conversation and Message (as shown in the code sample).
  • Initialize an AsyncSession and a ConversationService with the session.
  • Example flows:
    • Get or create a conversation for user_id "user-123".
    • Save a user message and an assistant reply.
    • Retrieve the latest 50 messages for a conversation.

Frequently Asked Questions about manage-conversation-db

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

FAQPage Schema
How do I implement stateless conversation persistence for a chat backend?▼

To persist chat history statelessly, you define Conversation and Message database models using SQLModel, initialize an AsyncSession, and use a service pattern to store and retrieve messages by conversation ID.

How does asynchronous database access work for retrieving conversation history?▼

Asynchronous database access for conversation history works by using non-blocking queries to fetch messages in chronological order, improving backend throughput when loading the latest 50 messages for agent input.

Can I use SQLModel to store user and assistant messages with metadata?▼

Yes, you can use SQLModel to define a Message model that persists user and assistant roles, text content, and optional metadata like tool_name and tool_call_id for each conversation entry.

What is the best way to enforce user isolation when managing chat conversations?▼

User isolation is enforced by scoping all conversation creation and retrieval operations to a specific user_id, ensuring that one user cannot access or load another user's conversation history.

Do I need an async database session to manage conversation lifecycles?▼

You need an async database session to support non-blocking operations when creating or loading conversations by ID and saving messages, which ensures high throughput for chat applications.