databases

List, inspect, and switch Claudia SQLite memory databases.

283|44|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/kbanc85/claudia --skill databases-kbanc85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: databases
Source: https://github.com/kbanc85/claudia/tree/main/template-v2/.claude/skills/databases
Command: npx skills add https://github.com/kbanc85/claudia --skill databases-kbanc85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claudia memory databases can become scattered across workspaces, making it hard to see what exists, where data lives, and how to switch contexts when focusing on a project. This Skill consolidates visibility, isolation, and switching in one place.

Core Features & Use Cases

  • View production and demo databases, understand workspace associations, and verify database health.
  • Switch the active database to change context for a given project, preserving isolation and updating reporting accordingly.
  • Quickly assess database size, counts of people and memories, and recent activity to plan maintenance and de-duplication.

Quick Start

Ask Claudia to view and switch between your memory databases with a single command.

Frequently Asked Questions about databases

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

FAQPage Schema
How do I switch between Claudia memory databases for different workspaces?

To switch memory databases, you change the active database context to isolate project data. This updates reporting and memory associations, preserving isolation so you only interact with the relevant workspace's people and memories.

What is the best way to view all my SQLite memory databases and their sizes?

Viewing SQLite memory databases involves listing all production and demo files at ~/.claudia/memory. This reports workspace associations, database sizes, counts of people and memories, and last activity to help plan maintenance and cleanup.

Do I need local SQLite3 databases to manage my Claudia workspace memory?

Yes, local SQLite3 databases located at ~/.claudia/memory and ~/.claudia/demo are required. The tool uses sqlite3 queries to report workspace data, counts, and last activity, requiring these specific local files to function correctly for context switching.

Can I check the health and contents of my Claudia memory databases?

Yes, you can check database health by displaying sizes and contents for planning and de-duplication. It reports workspace associations, counts of people and memories, and recent activity to verify database health and identify when cleanup is needed.

Why are my Claudia memory databases scattered across multiple workspaces?

Claudia memory databases become scattered across workspaces as different projects generate isolated data over time. This fragmentation makes it hard to see what exists and where data lives, which is why consolidating visibility and switching contexts in one place is necessary.