Agent skill · data analytics · jeremylongshore
obsidian-debug-bundle
Collect Obsidian plugin debug evidence for support and troubleshooting.
Why this skill is useful
Provides specific commands and procedures for collecting diagnostic information from the Obsidian vault that the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian Debug Bundle Current State !node --version 2>/dev/null echo 'N/A' !python3 --version 2>/dev/null echo 'N/A' !uname -a Overview Collect comprehensive diagnostics from an Obsidian vault: app version, installed plugins, active theme, vault stats, console errors, and CSS conflicts. Package everything into a markdown debug report. Prerequisites Access to the Obsidian vault's filesystem (the vault directory) Terminal access to run collection commands Developer Console access in Obsidian (Ctrl+Shift+I / Cmd+Option+I) Instructions Step 1: Identify the Vault Path Obsidian stores vault data in the vault root under .obsidian/. Locate it: Step 2: Collect Obsidian Version and App Settings Step 3: List Installed Plugins and Their Versions Step 4: Collect Theme and Appearance Info Step 5: Gather Vault Statistics Step 6: Capture Console Errors Open Obsidian's Developer Console (Ctrl+Shift+I / Cmd+Option+I), then run this in the Console tab to export errors: Alternatively, check for existing errors: Step 7: Detect CSS Conflicts Step 8: Generate the Debug Report Combine all diagnostics into a single markdown note: Output debug-report-YYYYMMDD-HHMMSS.md in the vault root containing: Platform and Obsidian version Complete plugin list with versions Active theme and CSS snippet inventory Vault statistics (file count, size) Appearance configuration Empty section for pasting console errors after reproducing the issue Error Handling Item Privacy Risk Action ------ ------------- -------- app.json Contains vault path Redact path before sharing Plugin data.json May contain API keys Never include automatically Console logs May contain file names Review before sharing Vault path Personal directory info Replace with <vault> before sharing CSS snippets Generally safe OK to share community-plugins.json Plugin list only Safe to share Examples Quick bug report: Run Steps 2-5 from terminal, paste output into a GitHub issue. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-debug-bundle--0c953b