mcpbeat

Deepchat Data Import

thinkinaixyz/deepchat-data-import

Help developers build third-party tools that import, inspect, migrate, or analyze DeepChat data. Use when Codex needs to work with DeepChat provider configuration, model configuration, MCP/app settings, sessions, messages, legacy chat data, `agent.db`, `chat.db`, SQLCipher encrypted SQLite, Electron safeStorage wrapped passwords, Tauri importers, or native macOS/Windows/Linux data access.

6k tokens
context cost
the whole folder, loaded on every use
6
files
instructions only
0
copies elsewhere
how many repositories repackaged it
6187
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill deepchat-data-import

The instruction itself

5 sections, as written by the author

DeepChat Data Import

Overview

Use this skill to design or implement importers for DeepChat local data. Treat DeepChat's SQLite

schema as an internal but documentable contract: inspect the current schema when precision matters,

prefer read-only snapshots, and avoid writing to a live profile.

Workflow

  • Identify the source: live DeepChat profile, copied profile, sync backup, exported agent.db, or

legacy chat.db.

  • Read references/data-locations.md to locate agent.db,

sidecar files, encryption metadata, and backup paths.

  • Read references/sqlite-access.md before opening SQLite. Decide

whether the database is unencrypted, can be unlocked through Electron safeStorage, or must ask

the user for the SQLite password.

  • Read references/schema-reference.md for provider config,

settings, session, message, and legacy table relationships.

  • Read references/import-recipes.md when writing extractor code,

mapping DeepChat data to another app, or creating a compatibility import.

Safety Rules

  • Get explicit user consent before reading local DeepChat data. Provider keys, OAuth tokens, MCP

env vars, prompt text, message traces, and chat content may be sensitive.

  • Never open the active agent.db read-write from a third-party tool. Copy agent.db,

agent.db-wal, and agent.db-shm, or use SQLite backup APIs through DeepChat itself.

  • If DeepChat is running, either ask the user to quit it or make a WAL-aware snapshot before import.
  • Prefer parameterized key APIs for SQLCipher passwords. Do not interpolate passwords into SQL.
  • Redact secrets by default in logs, telemetry, previews, and generated sample output.
  • When the schema has changed, inspect schema_versions, sqlite_master, and the table classes

under src/main/presenter/sqlitePresenter/tables/ before assuming column availability.

Source Files

Use these repository files as the current source of truth when updating the skill or answering

version-sensitive questions:

  • src/main/presenter/sqlitePresenter/index.ts
  • src/main/presenter/sqlitePresenter/connectionConfig.ts
  • src/main/presenter/databaseSecurityPresenter/index.ts
  • src/main/presenter/sqlitePresenter/tables/*.ts
  • src/main/presenter/agentRuntimePresenter/messageStore.ts
  • src/main/presenter/agentRuntimePresenter/sessionStore.ts
  • src/main/presenter/configPresenter/**

How to use it

Copy the folder

Take thinkinaixyz/deepchat-data-import from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.