# Local Conversation History

Entry point for local AI conversation history across Claude Code, Codex and Kimi CLI...

- Repository: https://github.com/daymade/claude-code-skills (1509 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add daymade/claude-code-skills --skill local-conversation-history -g -a claude-code -y`
Codex: `npx skills add daymade/claude-code-skills --skill local-conversation-history -g -a codex -y`
Cursor: `npx skills add daymade/claude-code-skills --skill local-conversation-history -g -a cursor -y`
Gemini CLI: `npx skills add daymade/claude-code-skills --skill local-conversation-history -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add daymade/claude-code-skills`

## Description

Entry point for local AI conversation history across Claude Code, Codex and Kimi CLI: routes each request to the reader or continuation skill that owns it and keeps the cross-provider inventory. Use when the platform is unknown or plural ("what was I working on", "we discussed this once") and for any Kimi CLI history. When platform and action are already clear, load that skill directly.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Local Conversation History, router

This skill decides **which** skill runs. It does not parse history itself, does
not own commands for a single provider, and never re-implements what an executor
already does. If you find yourself explaining flags for one provider, you are in
the wrong skill, hand off and stop.

## Route by platform × action

For a backup-health request ("are our conversation backups working?" / "历史备份是否正常"),
read the owning backup configuration and storage SOP before selecting a history reader.
Use `git-large-files-storage-setup`'s backup-health workflow when that Skill is installed;
otherwise use the existing storage owner's procedure and report any missing dependency.
Keep this route read-only. Verify provider/source coverage, the actual backup round,
destination originals, recovery samples and the alert job separately. Do not resume a
paused collector or rebuild an index to check a backup. Use provider readers only for
selected original/session identity checks, not conversation-body searches to discover
backup jobs. Keep account, machine and credential paths in the user's owning configuration.

Establish two things before routing: **which platform** the conversation lived
on, and whether the user wants **evidence** (what was said/done) or
**resumption** (take the work forward).

| Platform | Read evidence | Continue the work |
|---|---|---|
| Claude Code | `daymade-claude-code:read-claude-code-history` | `daymade-claude-code:continue-claude-code-work` |
| OpenAI Codex | `daymade-claude-code:read-codex-history` | `daymade-claude-code:continue-codex-work` |
| Kimi CLI | `read-claude-code-history`, with the Kimi scope named, see **Provider scope** | no continuation skill exists |

Resumption always follows a read. The continuation skills require a verified
read receipt; routing straight to them without one is a defect, not a shortcut.

The rest: https://github.com/daymade/claude-code-skills/blob/HEAD/daymade-claude-code/local-conversation-history/SKILL.md