Skill

sync-claude-sessions

Exports Claude Code sessions to Obsidian markdown files. List, export, resume, add notes, close sessions via CLI like `cs list`, `cs export --today`, `cs resume --pick`.

Python

Markdown

Bash

developer-tools

documentation

npx claudepluginhub artemxtech/personal-os-skills --plugin recall-skill

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Export Claude Code conversations to Obsidian for observability and analysis.

Supporting Assets

schema/tags.yamlscripts/claude-sessionsworkflows/log-session.mdworkflows/setup.md

SKILL.md

Similar Skills

/export — Session Export

Exports Claude Code session JSONL files to human-readable markdown with role markers and timestamps. Use to save, review, share transcripts, or feed dev-diary pipelines.

pds

ctx-history

Browses, inspects, and imports Claude Code session history. Lists sessions by project/tool/date, shows details or full conversations, imports to markdown journals.

1 tool

ctx

session-management

242

Manages Claude Code sessions using /rename, /resume, and CLI commands for naming, checkpointing, and resuming workflows in debugging, feature development, PR reviews, and investigations.

sanctum

Stats

Stars374

Forks60

Last CommitMar 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Sync Claude Sessions

Export Claude Code conversations to Obsidian for observability and analysis.

Quick Reference

# Alias (add to ~/.zshrc)
alias cs="python3 ~/.claude/skills/sync-claude-sessions/scripts/claude-sessions"

# Common commands
cs list                    # Active sessions
cs list --all              # All sessions
cs export --today          # Export today's sessions
cs resume --pick           # Interactive resume
cs note "got it working"   # Add timestamped comment
cs close "done"            # Mark session done

Commands

Command	Description
`sync`	Sync session (hook or explicit)
`export`	Batch export (`--today`, `--all`, `<file>`)
`resume`	Resume session (`--pick`, `--active`, `<file>`)
`note`	Add timestamped comment
`close`	Mark done + optional comment
`list`	List sessions (`--active`, `--all`, `--json`)

Workflow Routing

Task	Workflow
Enable live sync hooks	workflows/setup.md
Log/annotate session	workflows/log-session.md

Output

Sessions exported to Claude-Sessions/ with:

Frontmatter: type, date, session_id, title, summary, skills, messages, status, tags, rating, comments
Content: Summary, Skills Used (linked), Artifacts (wiki-linked), My Notes, Conversation

Preserved on Sync

## My Notes section
Frontmatter: comments, related, status, tags, rating

Frontmatter Schema

See Templates/Types/claude-session.md for the canonical template.

type: claude-session
date: YYYY-MM-DD
session_id: uuid
title: "..."
summary: "..." # auto-generated by Claude Code or haiku
skills: [skill1, skill2]
messages: 42
last_activity: ISO timestamp
status: active | done | blocked | handoff
tags: []          # see schema/tags.yaml
rating: null      # 1-10
comments: |
  [2026-02-05 14:30] Comment here
  [2026-02-05 15:00] Another comment
related: []

Tags Schema

Tags are defined in schema/tags.yaml with descriptions, keywords, and examples.

Type tags: research, implementation, debugging, planning, brainstorm, admin, quick, video, automation, writing

Project tags: lab, openclaw, personal, client

Agent should read schema/tags.yaml to validate tags when logging sessions.