Claude Conversation Logger

VerifiedSafe

Saves the current conversation to Obsidian as a structured log, summarizing key topics, decisions, and files. Use /log [title] to archive sessions and quickly recall context.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#log#obsidian#conversation-summary#note-taking

Recommended for

Automated summary

This skill summarizes the current conversation with Claude and saves it as a structured log in Obsidian.

Strengths

  • Automatically generates a structured summary with metadata (date, tags)
  • Creates a ready-to-use Markdown file in a dedicated Obsidian folder
  • Includes the full conversation log for future reference

Limitations

  • Requires Obsidian for optimal use (hardcoded save path)
  • Summary quality depends on the AI's analysis of the conversation
  • Only works with the /log command within Claude Code
When to use it

Use this skill when you want to keep a structured record of a work session or discussion with Claude in your Obsidian knowledge base.

When not to use it

Avoid using it for trivial or temporary conversations that don't need archiving, or if you don't use Obsidian.

Security analysis

Safe
Quality score85/100

The skill instructs the AI to summarize a conversation and save it as a Markdown file locally. It does not involve network access, command execution, or destructive operations. The file writing is confined to a specific directory (~/obsidian/Logs), and there is no exfiltration risk beyond what the user already exposes in the conversation. While file system access is powerful, the skill uses it for a benign logging purpose.

No concerns found

How this analysis is made

Examples

Auto-title log
/log
Custom title log
/log React 19 調査と設定作業

name: log description: 現在の会話をまとめてログとして保存

Log Skill

Claude との会話をまとめて Obsidian に保存する。

Usage

/log [タイトル]

Examples

/log                           # 自動でタイトル生成
/log React 19 調査と設定作業    # タイトル指定

Instructions

1. 会話の分析

現在の会話を分析し、以下を抽出:

  • 主なトピック・目的
  • 重要な決定事項
  • 作成・変更したファイル
  • 学んだこと・メモ

2. ログ作成

以下のフォーマットで Markdown を作成:

---
created: {YYYY-MM-DD HH:mm}
tags: [log, {トピックタグ}]
---

# {タイトル}

## 概要
{会話の目的・背景を1-2文で}

## 要約

### やったこと
- {箇条書きで主要なアクション}

### 決定事項
- {決まったこと、採用した方針}

### 成果物
- {作成/変更したファイルのリスト}

### メモ
- {学んだこと、今後の TODO など}

---

<details>
<summary>会話ログ(全文)</summary>

{会話の全文をここに}

</details>

3. 保存

  • 保存先: ~/obsidian/Logs/{YYYYMMDD}_{タイトル}.md
  • タイトル未指定時: 会話内容から自動生成
  • ファイル名のスペースはハイフンに置換
  • 保存後、ファイルパスを報告

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/claude-conversation-logger-mm8o52gl' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/claude-conversation-logger-mm8o52gl/download' --output '.skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md.part' && mv '.skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md.part' '.skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md' && test -s '.skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/log' && cp -R '.skill-downloads/claude-conversation-logger-mm8o52gl' '.claude/skills/log'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/claude-conversation-logger-mm8o52gl'

openskills read 'claude-conversation-logger-mm8o52gl'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/claude-conversation-logger-mm8o52gl/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills