← ClaudeAtlas

save-chatlisted

Save the current Codex conversation into the user's Obsidian vault as a markdown note. Use when the user asks to "save-chat", "/save-chat", save this chat/conversation/session, or save the current discussion to Obsidian, with optional slug support.
shimosan/claude-code-save-chat · ★ 4 · AI & Automation · score 62
Install: claude install-skill shimosan/claude-code-save-chat
# save-chat (Codex skin) Thin Codex entrypoint for the shared save-chat core. Do not duplicate the note format or workflow rules in this skill. ## Source Of Truth For any save-chat task, read and follow: 1. `<library_path>/scripts/save-chat-core.md` — the shared save-chat specification (workflow authority). 2. `~/.claude/CLAUDE.md` — the host-info ("ホスト情報") section (`vault_path`, `library_path`, `ai_note_folder`, `public_note_folders`, `private_note_folders`) and the Obsidian vault management rules (vault access, wikilink, privacy). ## Resolve `<library_path>` Use the current workspace if it contains `scripts/save-chat-core.md`. If not, read `library_path` from the host-info section of `~/.claude/CLAUDE.md` (or, on machines not yet migrated to the unified layout, from `~/.claude/CLAUDE.local.md`). If neither defines it, ask the user. Do not invent paths, vault folder names, or privacy scopes. If the core file cannot be read, stop and report; do not save to a fallback path unless the user explicitly asks for it. ## Invocation Accept natural-language requests such as: - `save-chatしてください` - `/save-chat` - `save-chat <slug>` - `この会話をObsidianに保存してください` If the user provides a slug, use it as the core defines. If not, derive one from the conversation topic per the core's slug rules. ## Codex binding (implements the core's platform binding contract) - `source`: `codex` - `model` and `session_id`: read from the local Codex transcript: 1. Resolve `CODEX_HOME` (