Obsidian Debug Bundle

Name: Obsidian Debug Bundle
Author: micsapp

ASecurity

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".

4 stars
0 votes
0 copies
3 views
Added September 10, 2026

toolstypescriptbash

Works with

terminal

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill obsidian-debug-bundle --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Obsidian Debug Bundle?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Obsidian Debug Bundle

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-obsidian-debug-bundle/badge)](https://www.skillsdirectory.com/skills/micsapp-obsidian-debug-bundle)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
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.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Obsidian Debug Bundle

## Overview
Collect all necessary diagnostic information for Obsidian plugin bug reports and support requests.

## Prerequisites
- Obsidian plugin with issues
- Access to vault configuration
- Terminal/command line access

## Instructions

### Step 1: Create Debug Bundle Script

### Step 2: Collect System Information

### Step 3: Collect Plugin Information

### Step 4: Collect Vault Information

### Step 5: Collect Error Logs (from Console)

For full implementation details and code examples, load:
`references/implementation-guide.md`

## Output
- `obsidian-debug-YYYYMMDD-HHMMSS.tar.gz` archive containing:
  - `summary.txt` - System and plugin info
  - `manifest.json` - Plugin manifest
  - `tsconfig.json` - TypeScript configuration
  - `console-log.txt` - Console output (manual)
  - `plugin-data.json` - Sanitized plugin data

## Error Handling
| Item | Purpose | Privacy |
|------|---------|---------|
| System info | Environment check | Safe |
| Plugin manifest | Version/config | Safe |
| Dependencies | Compatibility | Safe |
| Console logs | Error messages | Review before sharing |
| Settings | Configuration | REDACT secrets |
| Vault path | Location | DO NOT share |

## Resources
- [Obsidian Bug Reports](https://forum.obsidian.md/c/bug-reports/7)
- [Plugin Developer Help](https://forum.obsidian.md/c/developers/14)
- [Obsidian Discord #plugin-dev](https://discord.gg/obsidianmd)

## Next Steps
For rate limit issues, see `obsidian-rate-limits`.

## Examples

**Basic usage**: Apply obsidian debug bundle to a standard project setup with default configuration options.

**Advanced scenario**: Customize obsidian debug bundle for production environments with multiple constraints and team-specific requirements.