obsidian-conversation-backup

Back up Clawdbot conversations to an Obsidian vault with jq and cron.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Laserducktales/clawdbot-obsidian-backup --skill obsidian-conversation-backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-conversation-backup
Source: https://github.com/Laserducktales/clawdbot-obsidian-backup/tree/main
Command: npx skills add https://github.com/Laserducktales/clawdbot-obsidian-backup --skill obsidian-conversation-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents the loss of valuable conversation history from Clawdbot, especially when using the /new command, by automatically backing up conversations to an Obsidian vault with a user-friendly format.

Core Features & Use Cases

  • Incremental Backups: Automatically saves new messages hourly, preventing data loss without duplicating content.
  • Formatted Output: Saves conversations as Obsidian callouts with user/assistant distinction, emojis, and timestamps.
  • Use Case: Ensure no important discussion points or generated code snippets are lost when starting a new conversation in Clawdbot.

Quick Start

Install the skill and configure it to automatically back up your conversations hourly.

Frequently Asked Questions about obsidian-conversation-backup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically backup Clawdbot conversation history to an Obsidian vault?

You can backup Clawdbot conversation history to an Obsidian vault by running automated shell scripts that format chat data with jq and save it as markdown files using hourly incremental snapshots.

Does this backup tool require jq and cron to format chat logs?

Yes, this backup tool requires jq to parse and format the chat logs into markdown, and it relies on cron to schedule the automated hourly incremental snapshots.

What is the best way to prevent data loss when starting a new Clawdbot chat?

The best way to prevent data loss is to configure hourly incremental backups that automatically save new messages into formatted Obsidian markdown callouts before you start a new chat.

Can I get Telegram notifications for token monitoring during conversation backups?

Yes, you can receive Telegram notifications for token monitoring as the backup process includes built-in token monitoring that alerts you through Telegram during the hourly snapshots.

How does the backup process format user and assistant messages in Obsidian?

The backup process formats user and assistant messages into Obsidian callouts, distinguishing between the two roles using emojis and timestamps parsed via jq.

Are there limitations when backing up large chat histories with shell scripts?

While the shell scripts provide on-demand full backups and organized hourly breakdowns, large chat histories may require careful cron scheduling to prevent processing bottlenecks during hourly incremental snapshots.