obsidian-session | workflow-skills | ClaudePluginHub

Skill

obsidian-session

From workflow-skills

Track and document Claude Code sessions in the Obsidian vault. Creates or updates session notes with timestamps, learnings, code snippets, and file references. Use when asked to "document session", "write session notes", "save what we did", "log this session", "session summary", or "track this work".

Install

$

npx claudepluginhub arosenkranz/claude-code-config --plugin workflow-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Refer to `~/.claude/skills/obsidian-core/SKILL.md` for CLI patterns, preflight checks, and error handling.

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

157.7k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

157.7k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

157.7k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Obsidian Session Tracking

Refer to ~/.claude/skills/obsidian-core/SKILL.md for CLI patterns, preflight checks, and error handling.

Session File Naming

Session files use kebab-case in the Sessions/ folder:

Sessions/YYYY-MM-DD-brief-description.md

Example: Sessions/2026-03-02-docker-compose-setup.md

Modes

Full Session Lifecycle - Start, update, and end sessions with structured tracking
Quick Summary - Review the current conversation and write a single session entry

Full Session Lifecycle

Actions

start - Begin a new session with timestamp and objective
update - Add content to current session
end - Finalize session with summary and learnings
link - Cross-reference with projects or daily notes

Process

Check if session file exists:

obsidian read path="Sessions/YYYY-MM-DD-brief-description.md" 2>/dev/null

Empty output = file does not exist yet.

Create new session file (if it doesn't exist):

obsidian create path="Sessions/YYYY-MM-DD-brief-description.md" content="---\ntype: session\nstatus: in-progress\ndate: YYYY-MM-DD\n---\n\n# Session Title\n"

Append session content (if it already exists):

obsidian append path="Sessions/YYYY-MM-DD-brief-description.md" content="## HH:MM - Session Title\n..."

Set metadata on finalize:

obsidian property:set path="Sessions/YYYY-MM-DD-brief-description.md" name="status" value="complete"

Session Format

## HH:MM - [Session Title]

### Objective
[Brief description of session goal]

### Problems Solved
- [Problem 1 and solution]

### Code Snippets
\```language
[Relevant code]
\```

### Commands Used
\```bash
[Commands executed]
\```

### Key Learnings
- [Learning point 1]

### Files Modified
- [File path 1]

### Gotchas/Notes
- [Important discovery or warning]

Quick Summary

Review the current conversation and write a concise session note.

Quick Summary Format

## HH:MM - Brief Session Title
- **Objective**: What we accomplished
- **Problem**: Issues encountered or tasks completed
- **Solution**: Approach taken
- **Key Learning**: Important discoveries or patterns
- **Files**: List of created/modified files with full paths

Steps

Derive a kebab-case filename from the session topic
Check if Sessions/YYYY-MM-DD-<topic>.md exists using obsidian read
Create (first entry) or append (subsequent entries) using CLI
Set status: complete via obsidian property:set