plugins/obsidian-and-notes/skills/obsidian-session/SKILL.md
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".
npx skillsauth add arosenkranz/claude-code-config obsidian-sessionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Refer to ~/.claude/skills/obsidian-core/SKILL.md for CLI patterns, preflight checks, and error handling.
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
start - Begin a new session with timestamp and objectiveupdate - Add content to current sessionend - Finalize session with summary and learningslink - Cross-reference with projects or daily notesCheck 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"
## 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]
Review the current conversation and write a concise session note.
## 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
Sessions/YYYY-MM-DD-<topic>.md exists using obsidian readstatus: complete via obsidian property:settools
Lightweight orchestrator for spec-before-plan workflow. Use when starting a feature with ambiguous requirements. Walks SPEC.md → PLAN.md → execute, delegating to /superpowers:writing-plans and /superpowers:executing-plans. Invoke when asked to "spec this out", "spec-first", "spec and plan for X", or when feature requirements are vague.
tools
Problem Statement Co-Authoring Skill
development
Structure and maintain professional brag documents with clear templates for accomplishments, projects, and growth tracking. Use when documenting achievements, creating brag document entries, formatting accomplishments, or tracking career progress.
development
Analyze technical documentation for clarity, conciseness, and effectiveness using Google Technical Writing principles. Use when reviewing documentation, checking writing quality, improving docs, or providing writing feedback.