Get the FREE Ultimate OpenClaw Setup Guide →

obsidian-memory

Scanned
npx machina-cli add skill shane9coy/katana-agent/obsidian-memory --openclaw
Files (1)
SKILL.md
3.3 KB

Obsidian Memory Vault

Location

All memory files live in ~/.katana/memory/. This is an Obsidian-compatible vault.

Structure

~/.katana/memory/
├── core/
│   ├── soul.md          — Your identity and behavior. READ ON SESSION START.
│   ├── user.md          — Facts about the user. READ ON SESSION START.
│   └── routines.md      — Learned patterns and workflows.
├── sessions/            — Past session summaries (date-prefixed .md files)
├── projects/            — Per-project context and history
├── skills/              — Reusable skills (you can create new ones here)
│   └── _index.md        — Master index of all skills
└── work.md              — Running work log (newest entries at TOP)

On Session Start

  1. Read ~/.katana/memory/core/soul.md for your identity
  2. Read ~/.katana/memory/core/user.md for user context
  3. Check if current project has a folder in ~/.katana/memory/projects/
  4. If so, read the project's latest session entries

Writing Memories

Work Log (work.md)

Prepend new entries at the TOP of ~/.katana/memory/work.md:

## YYYY-MM-DD — project-tag
Summary of what was accomplished. Key decisions. What's next.

Project Memory

If working on a specific project, also update: ~/.katana/memory/projects/{project-name}/sessions.md

Core Memory (rare — important personal facts only)

If user reveals preferences, facts, or identity info:

  • Update ~/.katana/memory/core/user.md in the appropriate section
  • Always confirm before writing to core files

Soul Updates (very rare)

If user requests a behavior change:

  • Append to ~/.katana/memory/core/soul.md → Learned Behaviors section
  • Always notify user when modifying soul.md

Recalling Memories

When asked about past work:

  1. Search ~/.katana/memory/work.md for relevant entries
  2. Search ~/.katana/memory/projects/ for project-specific context
  3. Search ~/.katana/memory/skills/_index.md for relevant skills
  4. Use grep/find for keyword matching across all .md files

Creating Skills

When you solve a complex, reusable problem:

  1. Read ~/.katana/memory/skills/_index.md — check if similar skill exists
  2. If exists → UPDATE the existing skill with new learnings (don't duplicate)
  3. If new → create folder in appropriate category: ~/.katana/memory/skills/{category}/{skill-name}/
  4. Write SKILL.md with proper frontmatter:
---
aliases: [skill-name]
name: skill-name
created: YYYY-MM-DD
tags: [skill, category, relevant-tags]
times_used: 0
last_used: null
---
  1. Update ~/.katana/memory/skills/_index.md with new entry
  2. Use [[wikilinks]] to connect to related sessions and projects

Formatting Rules (Obsidian Compatibility)

  • Always include YAML frontmatter with date, tags, project
  • Use [[wikilinks]] for cross-references between notes
  • Use #tags for categorization
  • Keep summaries concise (2-4 sentences per work.md entry)
  • Name files descriptively (not just SKILL.md for standalone notes)

Source

git clone https://github.com/shane9coy/katana-agent/blob/main/templates/universal/skills/obsidian-memory/SKILL.mdView on GitHub

Overview

Obsidian Memory Vault stores past sessions, projects, and user preferences for Katana. It lives at ~/.katana/memory/ as an Obsidian-compatible vault and is consulted on session start and when recalling past work.

How This Skill Works

Memory is organized into core, sessions, projects, and skills folders. On session start, the agent reads core/soul.md for identity and core/user.md for user context, checks for an active project folder, and loads the latest project sessions if present. When recalling, the agent searches work.md, project histories, and the skills index to assemble relevant context.

When to Use It

  • When starting a new session to establish identity and user context
  • When recalling prior work or project decisions
  • When referencing user preferences or agent identity
  • When generating summaries of past projects for reporting
  • When updating work progress after completing tasks

Quick Start

  1. Step 1: Verify the vault at ~/.katana/memory/ exists and is accessible
  2. Step 2: On session start, read ~/.katana/memory/core/soul.md and ~/.katana/memory/core/user.md
  3. Step 3: When recalling, search ~/.katana/memory/work.md, projects/, and skills index for context

Best Practices

  • Keep memory entries concise and focused on facts
  • Confirm before writing to core memories like user or soul
  • Prepend new work log entries to work.md for quick access
  • Maintain consistent file naming and folder structure
  • Regularly review and prune memory content to avoid drift

Example Use Cases

  • Start of a session reads soul.md and user.md to tailor the conversation
  • Recall a previous project to inform a current design decision
  • Update work.md with the latest daily progress
  • Create or update per-project sessions.md with key milestones
  • Adjust user preferences in core/user.md after user feedback

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers