Agent skill · writing content · jeremylongshore
obsidian-incident-runbook
Troubleshoot Obsidian plugin failures with systematic incident response.
Why this skill is useful
Adds executable scripts and systematic procedures for diagnosing and resolving Obsidian plugin failures that are not widely known.
What it needs
Requires bash, python3 installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian Incident Runbook Overview Systematic procedures for diagnosing and resolving Obsidian failures: plugin crashes, vault corruption, sync conflicts, performance degradation, and broken CSS/themes. Each section is a self-contained runbook -- jump to the relevant one. Prerequisites Access to the affected Obsidian vault directory Developer Console access (Ctrl+Shift+I / Cmd+Option+I) Terminal access for filesystem operations Backup awareness (know where your backups are before making changes) Instructions Step 1: Quick Triage Determine the category before diving in: Symptom Category Go to --------- ---------- ------- Obsidian crashes on open or plugin enable Plugin crash Step 2 Notes missing, corrupted, or garbled Vault corruption Step 3 Duplicate files, conflicting edits Sync conflicts Step 4 Obsidian slow, high CPU/memory, lag while typing Performance Step 5 UI elements missing, wrong colors, broken layout CSS/Theme Step 6 Step 2: Plugin Crash Recovery Immediate: Enter Safe Mode If Obsidian crashes on startup, force safe mode: Reopen Obsidian. If it loads, the disabled plugin was the cause. Diagnose from Console Open Developer Console (Ctrl+Shift+I) and look for errors: Binary search for the offending plugin If multiple plugins could be the cause: Repeat halving until you isolate the single offending plugin. Step 3: Vault Corruption Recovery Check for corrupted files Recover from .trash Obsidian moves deleted files to .trash/ in the vault: Recover from Git backup If the vault is under Git version control: Recover from filesystem snapshots Step 4: Sync Conflict Resolution Obsidian Sync conflicts Obsidian Sync creates conflict files named Note (conflict YYYY-MM-DD).md: Resolution: Open both files in Obsidian, manually merge content into the original, delete the conflict file. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-incident-runbook