chat-history-import
Use when the user wants to import external chat exports into OpenClaw. This skill normalizes raw chat history into conversation-archive-compatible JSONL, then guides the model to distill daily memory and `MEMORY.md` candidates before applying merges with user confirmation.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/dashhuang--openclaw-chat-history-import)HTML
<a href="/listings/dashhuang--openclaw-chat-history-import"><img src="/api/listings/dashhuang--openclaw-chat-history-import/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Install `chat-history-import`
安装 `chat-history-import`
Copy the repository root into:
把仓库根目录复制到:
<workspace>/skills/chat-history-import
Install `conversation-history`
安装 `conversation-history`
Copy the companion skill directory into:
把配套 skill 目录复制到:
<workspace>/skills/conversation-history
Shared on one machine
单机共享安装
For shared install, copy:
如果想做共享安装,复制到:
~/.openclaw/skills/chat-history-import ~/.openclaw/skills/conversation-history
Then start a new OpenClaw session or run:
然后启动一个新的 OpenClaw session,或者运行:
openclaw skills info chat-history-import openclaw skills info conversation-history
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 362 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: chat-history-import
- description: Use when the user wants to import external chat exports into OpenClaw. This skill normalizes raw chat history into conversation-archive-compatible JSONL, then guides the model to distill daily memory and `MEMORY.md` candidates before applying merges with user confirmation.
- metadata: { "openclaw": { "emoji": "🗂️", "homepage": "https://github.com/dashhuang/openclaw-chat-history-import", "requires": { "bins": ["python3"] } } }
- ---
- # Chat History Import
- Use this skill when a user wants to import chat history from Claude, ChatGPT, Telegram Desktop exports, Slack exports, markdown logs, JSON/JSONL transcripts, or similar archives into an OpenClaw workspace.
- The most common source formats for this skill are ChatGPT exports and Claude exports.
- Telegram Desktop HTML exports are also supported when the user wants to backfill a Telegram direct chat or group into OpenClaw's raw archive.
- If the user has not exported data yet, suggest the usual official export entry points first:
- - ChatGPT: `Settings -> Data Controls -> Export`
- - Claude: `Settings -> Privacy -> Export data`
- These exports usually arrive as ZIP files and are good candidates for the built-in import flow.
- ## What This Skill Owns
- - raw archive import into `logs/message-archive-raw/`
- - daily memory distillation into `memory/YYYY-MM-DD.md`
- - `MEMORY.md` candidate generation
- - review and apply workflow for memory merges
- ## Related OpenClaw Components
- This skill is not a replacement for the live archive plugin or archive search skill.
- - `conversation-archive` plugin
- - Recommended when the workspace wants future live chats written into the same `logs/message-archive-raw/` tree.
- - This skill should emit archive files that are fully compatible with that plugin's raw archive layout.
- - `conversation-history` skill
- - Strongly recommended when the user wants agents to search imported history after import.
- - This import skill writes archive files; it does not replace archive recall/search workflows on its own.
- Preferred combined setup:
- 1. use `chat-history-import` to backfill old history
- 2. use `conversation-archive` to keep new history flowing in
- 3. use `conversation-history` to search both imported and live archive data
- ## What Scripts Do vs. What The Model Does
- Scripts handle deterministic work:
- - inspect the source archive
- - normalize messages into the archive schema
- - validate archive compatibility
- - write review artifacts
- - apply approved memory merges
- Validation must be reported in two layers when relevant:
- - `import-batch validation`: whether the files written by this import are valid
- - `full-archive validation`: whether the entire existing archive tree is valid
- If full-archive validation fails because of pre-existing files outside this import batch, do not describe the new import itself as failed. Report the historical archive issue separately.
- The model handles semantic work:
- - decide what each day is worth remembering
- - rewrite imported history into the style of existing OpenClaw daily memory
- - decide what belongs in `MEMORY.md`
- - compare imported `MEMORY.md` candidates against existing `MEMORY.md`
- Do not try to replace this semantic step with Python heuristics.
- Also do not assume the bundled Python parsers can recognize every source format.
- For unknown input formats, the model may need to inspect the source and write a temporary format-specific parser.
- ## Core Rules
- 1. Do not import external history into `agents/<agentId>/sessions/`.
- 2. Treat `logs/message-archive-raw/` as the canonical destination for imported raw chat history.
- 3. Imported archive output must pass `{baseDir}/scripts/validate_archive.py` and stay compatible with the `conversation-archive` plugin's archive contract.
- 4. Daily memory should merge into the existing `memory/YYYY-MM-DD.md` file for that date.
- 5. Daily memory body should look like normal OpenClaw memory: concise Chinese bullets, minimal metadata, no “Claude 备份里显示” phrasing.
- 6. Use a short HTML comment only to mark import provenance.
- 7. `MEMORY.md` is the default memory file here and is always review-required before apply.
- ## Large Export Handling
- If the user says they already uploaded an archive, but the current chat channel only exposes a placeholder or incomplete file payload, treat that as a transport limitation first.
- For large ChatGPT or similar exports, guide the user toward a smaller text-focused package before retrying upload:
- 1. unzip the export locally
- 2. keep the conversation JSON files first
- 3. keep optional small metadata files only when useful
- 4. remove bulky attachments such as images, audio, video, PDFs, Office files, and other binary artifacts
- 5. re-zip the reduced package and retry import
- For ChatGPT-style exports, the most important files are usually:
- - `conversations.json`
- - `conversations-*.json`
- - optional: `group_chats.json`
- - optional: `export_manifest.json`
- If the reduced archive still cannot be uploaded through the chat channel, ask for one of these instead:
- - a direct download URL
- - a host-local file path
- - a cloud storage link that can be fetched from the host
- Use a temp path or another host-local staging path for large imports rather than polluting `workspace/`.
- ## Import Workflow
- ### 1. Inspect
- Start by inspecting the source:
- ```bash
- python3 {baseDir}/scripts/inspect_import.py /path/to/archive-or-file
- ```
- Use local file structure first. Use web research only as fallback for unclear formats.
- When helpful, check whether the current workspace already has `conversation-archive` and `conversation-history` available, so the user can be told what will happen after import:
- - archive-only import
- - import plus future live archive
- - import plus searchable archive recall
- ### 2. Normalize Raw Archive
- Normalize the source into the archive schema described in `{baseDir}/references/schema.md`:
- ```bash
- python3 {baseDir}/scripts/normalize_import.py /path/to/archive --archive-root logs/message-archive-raw --workspace workspace --agent-id main --apply
- python3 {baseDir}/scripts/validate_archive.py logs/message-archive-raw
- ```
- After validation, explicitly separate these outcomes:
- 1. whether the newly written files from this import batch are valid
- 2. whether the pre-existing archive tree is fully valid
- If validation errors point to old archive files unrelated to the current import, report that clearly as a historical archive issue rather than an import-batch failure.
- ## Unknown Format Handling
- When the bundled parser does not recognize the input format, use this fallback sequence:
- 1. Inspect the source files directly.
- 2. Determine whether the structure is simple enough to map by hand.
- 3. If not, write a temporary Python parser under a temp directory.
- 4. Make that parser output the canonical archive JSONL shape from `{baseDir}/references/schema.md`.
- 5. Run `{baseDir}/scripts/validate_archive.py` on the result before claiming success.
- Preferred order:
- 1. bundled parser
- 2. model-assisted direct mapping
- 3. model-authored temporary parser
- Guardrails for temporary parsers:
- - only transform source data into canonical archive JSONL
- - do not write directly into `MEMORY.md`
- - do not bypass the archive validator
- - keep source-specific logic isolated; do not pollute the skill with one-off code unless the format is worth supporting permanently
- If a bundled parser is missing for a format that seems broadly reusable, mention that it may be worth promoting the temporary parser into a maintained parser later.
- ### 3. Distill Daily Memory
- This step is model-driven.
- Before writing any daily memory, switch into Plan Mode (or an equivalent explicit checklist workflow) and review the import one date at a time.
- When the runtime supports subAgents or delegated parallel review, prefer using them to review imported dates one by one or in very small date batches.
- The goal is coverage and auditability, not speed alone.
- Use the helper script to build the review checklist whenever possible:
- ```bash
- python3 {baseDir}/scripts/build_review_checklist.py logs/message-archive-raw \
- --source-archive <archive-name> \
- --source-provider <provider> \
- --md-out tmp/chat-import-review-checklist.md \
- --json-out tmp/chat-import-review-checklist.json
- ```
- This helper gives you a date-by-date checklist with entry counts so the Plan Mode review can be explicit and auditable.
- Required review process:
- 1. list every imported `YYYY-MM-DD.jsonl` date file first
- 2. create a checklist covering all imported dates
- 3. when subAgents are available, assign imported dates one by one, or in very small date batches, so every date has an explicit review owner
- 4. read each date fully before deciding what to write
- 5. do not infer from titles, conversation names, or sampling alone
- 6. do not apply `MEMORY.md` standards when deciding daily memory
- 7. after finishing review for one date, mark that checklist item as done immediately
- 8. only claim daily-memory completion after every imported date has been marked reviewed
- 9. when a date already has a local daily memory file, still check for missing imported bullets before deciding no change is needed
- Checklist discipline is part of the workflow, not an optional nicety.
- If a date was reviewed, the checklist should show that review explicitly.
- Before writing any memory, first read the local memory rules from the current OpenClaw environment.
- Read in this order when available:
- 1. local `openclaw.json`
- - focus on `agents.defaults.compaction.memoryFlush.prompt`
- - focus on `agents.defaults.compaction.memoryFlush.systemPrompt`
- 2. workspace `AGENTS.md`
- - look for memory-writing rules, what counts as worth remembering, and what to exclude
- 3. existing `MEMORY.md`
- - learn the default memory style already in use
- 4. recent `memory/YYYY-MM-DD.md`
- - learn the local daily memory writing style from actual files, not assumptions
- Use these local rules as the primary source of truth.
- If local rules conflict with anything in this skill, follow the local rules.
- The generic guidance in this skill is not an equal second source of truth; it is fallback-only scaffolding for cases where the local environment is missing rules or is still too vague to decide.
- For ready-to-use prompt templates, read `{baseDir}/references/prompts.md`.
- For each relevant date:
- - read the imported archive entries for that day
- - decide what is important enough to preserve in that day's log by applying the local OpenClaw memory rules first
- - only if those local rules are missing or too vague, fall back to the generic daily-memory heuristics bundled with this skill
- - write only the few items that survive that local-rule-first judgment
- - match existing OpenClaw daily memory style
- Daily memory is a day log, not a default-memory summary. Do not over-filter it using long-term-memory standards.
- Good output shape:
- ```md
- # 2024-04-14
- <!-- imported-memory provider=claude archive=data-...zip -->
- - 开始用 Claude 辅助起草中文股东信,采用“逐段整理,最后整合全文”的工作方式。
- ```
- Bad output shape:
- - profile dumps
- - long autobiographical summaries
- - “Claude 备份显示……”
- - verbose provenance in the body
- ### 4. Distill `MEMORY.md` Candidates
- Choose one of these modes explicitly:
- 1. `source-memory only`
- Use a dedicated memory-like file from the import source when available, such as Claude `memories.json`.
- 2. `archive-distill only`
- Distill `MEMORY.md` candidates directly from the imported archive.
- 3. `hybrid`
- Use source memory as the base, then refine or supplement it from archive evidence.
- Default:
- - if source memory exists, prefer `source-memory only`
- - only use `archive-distill only` or `hybrid` when the user explicitly wants the heavier path
- Before choosing wording and granularity, read local `MEMORY.md` and recent daily memory files so the imported candidates match the current workspace style.
- Preferred user-facing wording:
- - call `MEMORY.md` the default memory or 默认记忆
- - only use “长期记忆” when needed to contrast it with daily logs
- - avoid treating “long-term memory” as the canonical product term
- Warn the user that archive-wide `MEMORY.md` distillation is slower and more dependent on model quality.
- ### 5. Stage Review Payload
- After the model writes daily memory bullets and `MEMORY.md` bullets, save them in a JSON payload with this shape:
- ```json
- {
- "daily_memory": [
- {
- "date": "2024-04-14",
- "source_provider": "claude",
- "source_archive": "claude-export.zip",
- "bullets": [
- "开始用外部模型辅助起草正式中文文稿,采用“逐段整理,最后整合全文”的工作方式。"
- ]
- }
- ],
- "memory_md": [
- {
- "section": "关于用户",
- "source_provider": "claude",
- "source_archive": "claude-export.zip",
- "bullets": [
- "用户可在多语言环境中自然切换,个人交流常偏好中文。",
- "长期关注科技、游戏与时事。"
- ]
- }
- ]
- }
- ```
- Then stage or apply with:
- ```bash
- python3 {baseDir}/scripts/memory_merge.py /path/to/payload.json --review-root tmp/chat-history-import-review
- ```
- Use `memory_md` as the preferred payload key.
- `long_term_memory` is still accepted for compatibility, but new work should use `memory_md`.
- ### 6. Apply
- Daily memory can be applied directly:
- ```bash
- python3 {baseDir}/scripts/memory_merge.py /path/to/payload.json --memory-root memory --apply-daily
- ```
- `MEMORY.md` candidates must be confirmed first:
- ```bash
- python3 {baseDir}/scripts/memory_merge.py /path/to/payload.json --memory-file MEMORY.md --apply-long-term
- ```
- After a successful import, ask the user whether they want to delete the source archive, extracted source directory, and temp files to save disk space.
- Do not delete them without explicit confirmation.
- ## Output Expectations
- When reporting progress or completion, include:
- - detected source format
- - archive root written
- - import-batch validation result
- - full-archive validation result (if checked)
- - reviewed dates / total imported dates
- - which daily memory dates were updated
- - whether `MEMORY.md` candidates were only staged or also applied
- ## Guardrails
- - Do not claim imported archive compatibility unless validation passes.
- - Do not describe the current import as failed when only pre-existing archive files failed full-archive validation.
- - Do not imply that imported history will automatically be searchable unless the workspace also has an archive-retrieval workflow such as `conversation-history`.
- - Do not imply that future live chats will keep flowing into the same archive tree unless `conversation-archive` or equivalent live archive plumbing is enabled.
- - Do not let imported daily memory read like a profile summary.
- - Do not silently overwrite existing `MEMORY.md` facts.
- - Do not add bulky metadata into daily memory bodies.
- - Do not skip daily-memory review based only on titles, thread names, or sparse sampling.
- - Do not apply `MEMORY.md` filtering standards to daily memory distillation.
- - Do not assume unknown source formats can be handled safely without inspection.
- - Do not promote a temporary parser into the skill unless it is stable and broadly reusable.
- - Do not invent memory-writing preferences when the local OpenClaw environment already exposes them in config or existing memory files.
- Read `{baseDir}/references/schema.md` before changing archive output.
README.md · README · 325 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # OpenClaw Chat History Import
- I’m [Dash](https://x.com/DashHuang), CEO of [XD Inc.](https://2400.hk/).
- 我是 [Dash](https://x.com/DashHuang),[心动公司](https://2400.hk/) CEO。
- I built this skill because I do not want valuable long-term AI chat history and memory to stay scattered across third-party products forever. They should be brought back into an environment we control, manage, customize, and keep evolving over time.
- 我做这个 skill,是因为我不希望长期有价值的 AI 聊天记录和记忆信息,一直分散在各种第三方产品里。它们应该被逐步收回到一个由自己控制、可管理、可定制、也能持续演进的环境里。
- This skill helps import past conversations from tools like ChatGPT and Claude into OpenClaw, so that old chat history can become OpenClaw's own raw archive and memory.
- 这个 skill 的作用,就是把 ChatGPT、Claude 等工具里的过往聊天记录导入 OpenClaw,让这些历史逐步变成 OpenClaw 自己的 raw archive 和记忆。
- Today that system may be OpenClaw. In the future it may be something else. The important part is keeping the data in a state we control.
- 今天这个承接系统可以是 OpenClaw,将来也可能是别的产品。关键不是某一个具体产品,而是这些数据始终处在自己可控的状态里。
- An OpenClaw skill bundle for turning your past AI chat history into OpenClaw's own memory.
- 这是一个 OpenClaw skill bundle,核心用途是把你过去在其他 AI 工具里的聊天记录,导入到 OpenClaw 里,变成龙虾自己的记忆。
- It helps migrate old conversations from tools like ChatGPT and Claude into OpenClaw, so that past chat history can become:
- 它适合把 ChatGPT、Claude 等工具里的旧聊天迁移进 OpenClaw,让这些历史记录变成:
- - searchable raw archive
- - daily memory
- - `MEMORY.md`
- - 可搜索的原始 archive
- - 每日记忆
- - `MEMORY.md`
- In short: instead of leaving your old AI conversations stranded across different products, this bundle helps bring them into OpenClaw's own memory system.
- 一句话说:它不是把旧聊天继续留在别的 AI 产品里,而是把它们收进 OpenClaw 自己的记忆系统里。
- The bundle currently includes two companion skills:
- 这个仓库目前包含两个互相配合的 skill:
- - `chat-history-import`
- - `conversation-history`
- `chat-history-import` imports external history into:
- `chat-history-import` 会把外部聊天历史导入到:
- - `logs/message-archive-raw/`
- - `memory/YYYY-MM-DD.md`
- - `MEMORY.md`
- `conversation-history` searches archive files later, so agents can recall old decisions, links, wording, and chronology.
- `conversation-history` 用来在导入后搜索 archive 文件,方便 agent 回忆旧决策、旧链接、原话和时间线。
- This bundle is designed for interactive, review-first migration from Claude exports, ChatGPT exports, Slack-style transcripts, and other structured or semi-structured chat archives.
- 这个 bundle 面向交互式、先审阅再落盘的迁移流程,适合 Claude 导出、ChatGPT 导出、Slack 风格转储,以及其他结构化或半结构化聊天存档。
- ## Common Sources
- ## 常见来源
- The most common use case is importing history from previous AI chat tools, especially ChatGPT and Claude.
- It now also supports Telegram Desktop HTML exports when you want to backfill a Telegram direct chat or group into the same archive tree used by OpenClaw's live `conversation-archive` plugin.
- 最常见的使用场景,是把你在其他 AI 聊天工具里的旧历史导入进来,尤其是 ChatGPT 和 Claude。
- ### ChatGPT export
- ### ChatGPT 导出
- As of now, the usual path is:
- 截至目前,常见导出路径是:
- - ChatGPT
- - `Settings`
- - `Data Controls`
- - `Export`
- That export usually arrives as a ZIP and commonly includes files such as `conversations.json`.
- 导出的结果通常是一个 ZIP,里面常见会有 `conversations.json` 之类的文件。
- ### Claude export
- ### Claude 导出
- As of now, the usual path is:
- 截至目前,常见导出路径是:
- - Claude
- - `Settings`
- - `Privacy`
- - `Export data`
- That export also typically arrives as a ZIP and may include files such as `conversations.json`, `memories.json`, `projects.json`, and account metadata.
- 导出的结果通常也是一个 ZIP,里面可能包含 `conversations.json`、`memories.json`、`projects.json` 以及账户元数据。
- If the source is not ChatGPT or Claude, this bundle can still help, but the import may need model-assisted format inspection or a temporary parser.
- 如果来源不是 ChatGPT 或 Claude,这个 bundle 也仍然可以尝试导入,只是更可能需要模型辅助识别格式,或者临时写一个 parser。
- ### Telegram Desktop export
- ### Telegram Desktop 导出
- Telegram Desktop exports usually arrive as a directory containing `messages.html`, `messages2.html`, and so on.
- Telegram Desktop 的导出通常是一个目录,里面包含 `messages.html`、`messages2.html` 等文件。
- Use the normal inspect and normalize flow, but provide the target OpenClaw chat identity explicitly so the imported history lands in the canonical Telegram archive path:
- 检查和导入时,额外提供目标 OpenClaw chat identity,这样历史才会落到正确的 Telegram archive 路径里:
- ```bash
- python3 scripts/inspect_import.py /path/to/ChatExport_xxx
- python3 scripts/normalize_import.py /path/to/ChatExport_xxx \
- --workspace workspace-food-group \
- --agent-id food-group \
- --chat-type group \
- --peer-id -1003778432310 \
- --assistant-name Cindy \
- --apply
- ```
- ## Included Skills
- ## 包含的 Skills
- ### `chat-history-import`
- The main import workflow.
- 主导入工作流。
- Use it to inspect export files, normalize raw history into `logs/message-archive-raw/`, distill daily memory, and stage `MEMORY.md` candidates for review.
- 它负责检查导出文件、把原始聊天规范化写入 `logs/message-archive-raw/`、提炼 daily memory,并生成待审阅的 `MEMORY.md` 候选内容。
- ### `conversation-history`
- The companion retrieval workflow.
- 配套的历史检索工作流。
- Use it after import when an agent needs to search old decisions, exact wording, old links, or chronology from raw archive files.
- 在导入完成后,如果 agent 需要查找旧决策、原话、旧链接或时间线,就使用它来搜索 raw archive 文件。
- ## Recommended Companion Components
- ## 推荐搭配组件
- ### `conversation-archive` plugin
- Recommended, but not required.
- 推荐安装,但不是硬依赖。
- Use it when you want imported history and future live chat history to live under the same archive layout.
- 如果你希望“导入的旧历史”和“未来实时聊天历史”都落到同一套 archive 目录结构里,就应该搭配它使用。
- In practice:
- 实际效果是:
- - `chat-history-import` backfills old history
- - `conversation-archive` keeps new history flowing in
- - `conversation-history` searches both imported and live archive data
- - `chat-history-import` 负责补历史
- - `conversation-archive` 负责持续写入新消息
- - `conversation-history` 负责搜索导入历史和实时归档
- ## Requirements
- ## 依赖
- - OpenClaw
- - `python3`
- ## Install
- ## 安装
- ### Install `chat-history-import`
- ### 安装 `chat-history-import`
- Copy the repository root into:
- 把仓库根目录复制到:
- ```text
- <workspace>/skills/chat-history-import
- ```
- ### Install `conversation-history`
- ### 安装 `conversation-history`
- Copy the companion skill directory into:
- 把配套 skill 目录复制到:
- ```text
- <workspace>/skills/conversation-history
- ```
- ### Shared on one machine
- ### 单机共享安装
- For shared install, copy:
- 如果想做共享安装,复制到:
- ```text
- ~/.openclaw/skills/chat-history-import
- ~/.openclaw/skills/conversation-history
- ```
- Then start a new OpenClaw session or run:
- 然后启动一个新的 OpenClaw session,或者运行:
- ```bash
- openclaw skills info chat-history-import
- openclaw skills info conversation-history
- ```
- ## Duplicate Install Notes
- ## 重复安装说明
- If OpenClaw already provides `conversation-history` from a plugin or shared skills directory, avoid installing a second copy into the same scope.
- 如果 OpenClaw 已经通过插件或 shared skills 目录提供了 `conversation-history`,就不要在同一个 scope 里再装第二份。
- Practical rule:
- 实践上建议这样处理:
- - one `conversation-history` per scope is best
- - workspace-local copies typically override shared copies
- - if both exist, check `openclaw skills info conversation-history` to see which source is active
- - 每个 scope 最好只保留一份 `conversation-history`
- - workspace-local 通常会覆盖 shared 版本
- - 如果两份都在,运行 `openclaw skills info conversation-history` 看当前实际生效的是哪一份
- ## Publish To ClawHub
- ## 发布到 ClawHub
- For the import skill at repo root:
- 发布仓库根目录的导入 skill:
- ```bash
- clawhub publish . \
- --slug chat-history-import \
- --name "Chat History Import" \
- --version 0.1.0 \
- --tags latest \
- --changelog "Initial public release."
- ```
- For the companion retrieval skill:
- 发布配套的检索 skill:
- ```bash
- clawhub publish ./conversation-history \
- --slug conversation-history \
- --name "Conversation History" \
- --version 0.1.0 \
- --tags latest \
- --changelog "Initial public release."
- ```
- ## Validate Locally
- ## 本地校验
- ```bash
- python3 -m py_compile scripts/*.py
- python3 -m py_compile conversation-history/scripts/*.py
- openclaw skills info chat-history-import
- ```
- ## Repository Layout
- ## 仓库结构
- - `SKILL.md`
- OpenClaw skill entrypoint and workflow instructions for `chat-history-import`.
- - `conversation-history/`
- Companion archive retrieval skill.
- - `references/`
- Archive schema and memory distillation prompt templates.
- - `scripts/`
- Deterministic helpers for inspect, normalize, validate, and merge.
- - `SKILL.md`
- `chat-history-import` 的 OpenClaw skill 入口和工作流说明。
- - `conversation-history/`
- 配套的 archive 检索 skill。
- - `references/`
- archive schema 与 memory 提炼提示词模板。
- - `scripts/`
- 用于 inspect、normalize、validate 和 merge 的确定性辅助脚本。
- ## License
- ## 许可证
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.