log

Summarizes the current conversation and saves it as a Markdown log in Obsidian.

4|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/okm321/dotfiles --skill log-okm321
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: log
Source: https://github.com/okm321/dotfiles/tree/main/claude/skills/log
Command: npx skills add https://github.com/okm321/dotfiles --skill log-okm321

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI conversations contain valuable decisions, file changes, and lessons learned that are easily lost once the session ends. This Skill captures the current conversation, structures it into a reusable summary, and archives it in your Obsidian vault for future reference. ## Core Features & Use Cases - Conversation Analysis: Extracts main topics, key decisions, created or modified files, and lessons learned from the current session. - Structured Markdown Logs: Generates a log with frontmatter (creation date, tags), an overview, summary sections (actions, decisions, deliverables, notes), and a collapsible full conversation transcript. - Automatic Titling and Filing: Auto-generates a title when none is given, sanitizes filenames by replacing spaces with hyphens, and saves to ~/obsidian/Logs/{YYYYMMDD}_{title}.md. - Use Case: After a long debugging or research session, run /log React 19 investigation to archive the findings, decisions, and full transcript into your Obsidian knowledge base. ## Quick Start Ask the assistant to summarize this conversation and save it as a log in Obsidian, optionally providing a title for the log file.

Frequently Asked Questions about log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save an AI conversation to Obsidian?▼

Run the log command with an optional title, such as /log React 19 investigation. The Skill analyzes the conversation, builds a structured Markdown summary with frontmatter and a full transcript, and saves it to ~/obsidian/Logs with a date-prefixed filename.

How do I generate a title automatically for a conversation log?▼

Invoke /log without any arguments. The Skill analyzes the conversation content and generates an appropriate title on its own, then uses it for both the heading and the filename.

What format does the conversation log use?▼

The log is a Markdown file with YAML frontmatter containing the creation timestamp and topic tags. The body includes an overview, summary sections for actions, decisions, deliverables, and notes, plus the full conversation inside a collapsible details block.

Where are conversation logs saved and how are files named?▼

Logs are saved to ~/obsidian/Logs/ with filenames in the format {YYYYMMDD}_{title}.md. Spaces in the title are replaced with hyphens, and the Skill reports the saved file path after writing.

What are the limitations of automated conversation logging?▼

The summary quality depends on what is present in the current session context, so details from earlier closed sessions cannot be captured. It also assumes the Obsidian Logs directory exists at the configured path.