Install
$ agentstack add skill-thinkinaixyz-deepchat-deepchat-data-import ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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](references/data-locations.md) to locate
agent.db,
sidecar files, encryption metadata, and backup paths.
- Read [references/sqlite-access.md](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](references/schema-reference.md) for provider config,
settings, session, message, and legacy table relationships.
- Read [references/import-recipes.md](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.dbread-write from a third-party tool. Copyagent.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.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/**
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ThinkInAIXYZ
- Source: ThinkInAIXYZ/deepchat
- License: Apache-2.0
- Homepage: https://deepchat.thinkinai.xyz/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.