ChatGPT Import
v1.0.2Import and embed ChatGPT conversation history into OpenClaw's memory search database for easy archival and retrieval of past chats.
⭐ 2· 719·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, SKILL.md, and the included scripts all align: converting ChatGPT's conversations.json to markdown and embedding those texts into an OpenClaw-compatible SQLite DB. However, the registry metadata lists no required environment variables or primary credential, while the runtime requires an OpenAI API key (OPENAI_API_KEY or --api-key). This is a metadata/documentation inconsistency (not functional maliciousness).
Instruction Scope
SKILL.md precisely instructs export → convert → embed → register DB with OpenClaw. The scripts only read user-provided export files and the output directory, call OpenAI's embeddings endpoint (api.openai.com), and write a local SQLite DB. There are no instructions to read unrelated system files or send data to unexpected endpoints. The README explicitly warns about sending secrets and about backups.
Install Mechanism
No install spec; this is an instruction+script bundle with no network install step. All code is included in the package and uses standard Python stdlib; nothing is downloaded or extracted at install time.
Credentials
The functionality legitimately requires an OpenAI API key to call the embeddings API, and filesystem access to the user's exported conversations and to write the output DB. The metadata, however, declares no required env vars or primary credential — this mismatch should be corrected. No other credentials or unrelated environment access are requested.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or permanent presence. It does not modify other skills or system-wide config by itself; it only creates a local DB file at a user-specified path and suggests user actions to add that DB to OpenClaw's search paths.
Assessment
This skill appears to do exactly what it claims: convert your ChatGPT export into markdown and embed it using OpenAI embeddings into a local SQLite DB for OpenClaw. Before running it, consider the following:
- The scripts send your conversation text to OpenAI's embeddings endpoint (api.openai.com). If conversations include sensitive secrets, remove or scrub them first, or use a scoped API key. The SKILL.md notes this.
- The registry metadata does not list the required OPENAI_API_KEY env var — supply a key via OPENAI_API_KEY or --api-key when running. Treat this as a documentation gap rather than malicious behavior, but be cautious.
- Review and run the scripts locally in a controlled environment. The code is included and readable; verify paths and back up your data before running (the script refuses to overwrite an existing DB but you should still back up exports).
- If you need stronger privacy, consider using a provider or on-prem embedding solution instead of sending transcripts to the public OpenAI API.
If you want, I can highlight the exact lines where the API call occurs and where the key is read, or produce a checklist to run this safely (e.g., run in a temp directory, use a scoped key, inspect outputs).Like a lobster shell, security has layers — review code before you run it.
latestvk97a46q0h2abbh13k0f9my4cx9815q4g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.