Obsidian Debug BundleSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: obsidian-debug-bundle description: 'Collect Obsidian plugin debug evidence for support and troubleshooting. Use when encountering persistent issues, preparing bug reports, or collecting diagnostic information for plugin problems. Trigger with phrases like "obsidian debug", "obsidian diagnostic", "collect obsidian logs", "obsidian support bundle". ' allowed-tools: Read, Bash(grep:*), Bash(tar:*), Grep, Write version: 1.13.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - obsidian - debugging compatibility: Designed for Claude Code --- # 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: ```bash # macOS VAULT_PATH=~/Documents/MyVault # Linux VAULT_PATH=~/Obsidian/MyVault # Windows (Git Bash) VAULT_PATH="/c/Users/$USER/Documents/MyVault" # Verify it's a valid vault ls "$VAULT_PATH/.obsidian/app.json" && echo "Valid vault" || echo "Not a vault" ``` ### Step 2: Collect Obsidian Version and App Settings ```bash # Obsidian version is in the installer log or app settings cat "$VAULT_PATH/.obsidian/app.json" 2>/dev/null | python3 -m json.tool # Check installer version (macOS) mdls -name kMDItemVersion /Applications/Obsidian.app 2>/dev/null # Check installer version (Linux, snap) snap info obsidian 2>/dev/null | grep installed ``` ### Step 3: List Installed Plugins and Their Versions ```bash # Active community plugins echo "=== Active Plugins ===" cat "$VAULT_PATH/.obsidian/community-plugins.json" 2>/dev/null | python3 -m json.tool # Plugin details (name, version, minAppVersion) echo "=== Plugin Manifests ===" for dir in "$VAULT_PATH/.obsidian/plugins"/*/; do if [ -f "$dir/manifest.json" ]; then echo "--- $(basename "$dir") ---" python3 -c " import json m = json.load(open('$dir/manifest.json')) print(f\" version: {m.get('version', 'unknown')}\") print(f\" minAppVersion: {m.get('minAppVersion', 'unknown')}\") print(f\" author: {m.get('author', 'unknown')}\") " fi done ``` ### Step 4: Collect Theme and Appearance Info ```bash echo "=== Appearance ===" cat "$VAULT_PATH/.obsidian/appearance.json" 2>/dev/null | python3 -m json.tool # Check for custom CSS snippets echo "=== CSS Snippets ===" ls "$VAULT_PATH/.obsidian/snippets/" 2>/dev/null || echo "No snippets directory" # Check active theme THEME=$(python3 -c " import json try: a = json.load(open('$VAULT_PATH/.obsidian/appearance.json')) print(a.get('cssTheme', 'Default')) except: print('Default') ") echo "Active theme: $THEME" ``` ### Step 5: Gather Vault Statistics ```bash echo "=== Vault Stats ===" # File counts by type echo "Markdown files: $(find "$VAULT_PATH" -name '*.md' -not -path '*/.obsidian/*' -not -path '*/.trash/*' | wc -l)" echo "Attachments: $(find "$VAULT_PATH" \( -name '*.png' -o -name '*.jpg' -o -name '*.pdf' -o -name '*.mp3' \) -not -path '*/.obsidian/*' | wc -l)" echo "Total files: $(find "$VAULT_PATH" -type f -not -path '*/.obsidian/*' -not -path '*/.trash/*' | wc -l)" # Vault size echo "Vault size: $(du -sh "$VAULT_PATH" 2>/dev/null | cut -f1)" echo ".obsidian size: $(du -sh "$VAULT_PATH/.obsidian" 2>/dev/null | cut -f1)" ``` ### 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: ```javascript // Paste in Obsidian's Developer Console (() => { const errors = []; const originalError = console.error; console.error = (...args) => { errors.push({ time: new Date().toISOString(), message: args.map(String).join(' ') }); originalError.apply(console, args); }; // After reproducing the issue, run: // copy(JSON.stringify(errors, null, 2)) // This copies the error log to clipboard console.log(`Error capture active. Reproduce your issue, then run: copy(JSON.stringify(errors, null, 2))`); })(); ``` Alternatively, check for existing errors: ```javascript // Quick dump of plugin load errors app.plugins.manifests; // All registered plugins app.plugins.enabledPlugins; // Currently enabled set // Check if a specific plugin failed to load: app.plugins.plugins['your-plugin']; // undefined = failed to load ``` ### Step 7: Detect CSS Conflicts ```bash # Check for snippet overrides that might conflict for snippet in "$VAULT_PATH/.obsidian/snippets"/*.css; do [ -f "$snippet" ] || continue echo "=== $(basename "$snippet") ===" # Look for broad selectors that commonly cause conflicts grep -n 'body\b\|\.app-container\|\.workspace\|\.markdown-preview\|!important' "$snippet" | head -20 done # Check theme CSS size (large themes are conflict-prone) THEME_DIR="$VAULT_PATH/.obsidian/themes/$THEME" if [ -d "$THEME_DIR" ]; then echo "Theme CSS size: $(wc -c < "$THEME_DIR/theme.css" 2>/dev/null) bytes" fi ``` ### Step 8: Generate the Debug Report Combine all diagnostics into a single markdown note: ```bash REPORT="$VAULT_PATH/debug-report-$(date +%Y%m%d-%H%M%S).md" cat > "$REPORT" <<'HEADER' # Obsidian Debug Report HEADER cat >> "$REPORT" <<EOF Generated: $(date -u +"%Y-%m-%dT%H:%M:%SZ") Platform: $(uname -s) $(uname -m) Node: $(node --version 2>/dev/null || echo 'N/A') ## App Settings \`\`\`json $(cat "$VAULT_PATH/.obsidian/app.json" 2>/dev/null || echo '{}') \`\`\` ## Active Plugins \`\`\`json $(cat "$VAULT_PATH/.obsidian/community-plugins.json" 2>/dev/null || echo '[]') \`\`\` ## Plugin Versio
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__obsidian-debug-bundle.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Obsidian Debug Bundle skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Obsidian Debug Bundle safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Obsidian Debug Bundle access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Obsidian Debug Bundle work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.