context-db-schema

Apply MediatorLite's SQLite session schema with idempotent C# helpers.

4|1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/behl1anmol/MediatorLite --skill context-db-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-db-schema
Source: https://github.com/behl1anmol/MediatorLite/tree/main/.cursor/skills/context-db-schema
Command: npx skills add https://github.com/behl1anmol/MediatorLite --skill context-db-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MediatorLite's multi-agent workflows require durable, consistent cross-chat memory for session state, inter-agent messages, and audit logs, but manual SQLite management leads to foreign key constraint errors, session ID mismatches, and inconsistent timestamp formatting that breaks context retrieval.

Core Features & Use Cases

  • Idempotent schema management: Automatically applies the session database schema on first use with no manual CREATE TABLE steps required.
  • Type-safe helper methods: Provides pre-built C# helpers for common operations including logging agent handoffs, recording architecture decisions, tracking mistakes, and managing sprint backlog items.
  • Cross-agent context sharing: Enables parent agents and spawned subagents to share the same session context via the MEDIATORLITE_SESSION_ID environment variable, with WAL mode enabled for safe concurrent read/write access. For example, a code-reviewer subagent can pull recent handoff messages to understand implementation context before logging review findings to the shared database.

Quick Start

Use the context-db-schema skill to log a new architecture decision for your current MediatorLite session by providing the decision topic, selected option, and supporting rationale.

Frequently Asked Questions about context-db-schema

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

FAQPage Schema
How do I manage SQLite session state for MediatorLite multi-agent workflows?

Manage SQLite session state for MediatorLite workflows by using an idempotent schema that automatically creates tables on first use, enforcing foreign keys and formatting ISO-8601 UTC timestamps to ensure durable cross-chat memory.

Why does manual SQLite context management fail in .NET multi-agent workflows?

Manual SQLite context management fails in .NET multi-agent workflows because it causes foreign key constraint errors, session ID mismatches, and inconsistent timestamp formatting that breaks context retrieval. Automated schema management prevents these issues.

Can parent agents and subagents share the same session context in MediatorLite?

Parent agents and spawned subagents can share the same session context in MediatorLite via the MEDIATORLITE_SESSION_ID environment variable. SQLite WAL mode enables safe concurrent read and write access to this shared state.

How do I log architecture decisions and agent handoffs in a durable SQLite database?

Log architecture decisions and agent handoffs in a durable SQLite database using type-safe C# helper methods. These pre-built helpers manage common multi-agent operations like recording decisions, tracking mistakes, and managing sprint backlog items.

Does SQLite WAL mode support concurrent access for cross-chat agent persistence?

SQLite WAL mode supports concurrent access for cross-chat agent persistence by allowing safe concurrent read and write operations. This enables multiple agents to interact with the shared session database simultaneously without locking conflicts.

Do I need to manually create tables for MediatorLite session databases?

You do not need to manually create tables for MediatorLite session databases. The schema management is idempotent and automatically applies the session database schema on first use without requiring manual CREATE TABLE steps.