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.
npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill deepchat-data-import
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.
agent.db, orlegacy chat.db.
agent.db,sidecar files, encryption metadata, and backup paths.
whether the database is unencrypted, can be unlocked through Electron safeStorage, or must ask
the user for the SQLite password.
settings, session, message, and legacy table relationships.
mapping DeepChat data to another app, or creating a compatibility import.
env vars, prompt text, message traces, and chat content may be sensitive.
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.
schema_versions, sqlite_master, and the table classesunder src/main/presenter/sqlitePresenter/tables/ before assuming column availability.
Use these repository files as the current source of truth when updating the skill or answering
version-sensitive questions:
src/main/presenter/sqlitePresenter/index.tssrc/main/presenter/sqlitePresenter/connectionConfig.tssrc/main/presenter/databaseSecurityPresenter/index.tssrc/main/presenter/sqlitePresenter/tables/*.tssrc/main/presenter/agentRuntimePresenter/messageStore.tssrc/main/presenter/agentRuntimePresenter/sessionStore.tssrc/main/presenter/configPresenter/**Take thinkinaixyz/deepchat-data-import from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.