agentleFS
ArtemXTechArtemXTech/personal-os-skills/skills/sync-claude-sessions/SKILL.md

sync-claude-sessions

Skill545 starsChanged 54 days agoMITView on GitHub

Sync Claude Code sessions to Obsidian markdown. Export, resume, add notes, close sessions. USE WHEN user says "sync sessions", "export sessions", "resume session", "add session note", "close session", "log session".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Pdiamondz1/hma_project_foundation★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

Files
SKILL.md

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

CommandDescription
syncSync session (hook or explicit)
exportBatch export (--today, --all, <file>)
resumeResume session (--pick, --active, <file>)
noteAdd timestamped comment
closeMark done + optional comment
listList sessions (--active, --all, --json)

Workflow Routing

TaskWorkflow
Enable live sync hooksworkflows/setup.md
Log/annotate sessionworkflows/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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.