obsidian-runtime-debug

Debug Obsidian plugins in a live vault using eval probes and CDP profiling.

2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/GoBeromsu/obsidian-workspace --skill obsidian-runtime-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-runtime-debug
Source: https://github.com/GoBeromsu/obsidian-workspace/tree/main/.claude/skills/obsidian-runtime-debug
Command: npx skills add https://github.com/GoBeromsu/obsidian-workspace --skill obsidian-runtime-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debug, profile, and verify Obsidian community plugins in a live vault with the Obsidian CLI. Use when a plugin throws runtime errors, needs a DB or plugin-state reset, must be reinstalled into a test vault, requires DevTools/CDP profiling, or needs screenshot and DOM verification before shipping.

Core Features & Use Cases

  • Live-state debugging: Reset minimal state, run small Obsidian eval probes, and profile focused operations to verify health.
  • Deterministic resets and repros: Disable/reinstall plugins in a test vault, preserve user data.json when needed, and re-run health checks without affecting the user vault.
  • Probing, profiling, and UI verification: Use small eval probes, CDP profiler, and DOM/screenshot checks to validate runtime behavior and UI state before release.
  • Post-check workflow: Re-check errors and console output after tests and ensure readiness for shipping.

Quick Start

Begin a live debugging session by configuring a test vault and running the prescribed probes, resets, and profiling steps to validate runtime health before release.

Frequently Asked Questions about obsidian-runtime-debug

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

FAQPage Schema
How do I debug Obsidian plugins in a live vault?

Debug Obsidian plugins in a live vault by running small eval probes, applying minimal-state resets, and using CDP profiling to identify runtime errors while preserving user data during safe repros.

What is the best way to profile a corrupted Obsidian plugin state?

The best way to profile corrupted Obsidian plugin state is using the CDP profiler alongside deterministic resets in a test vault, which isolates the issue and validates runtime behavior without destroying your existing data.json file.

Can I verify Obsidian plugin UI anomalies using DOM and screenshots?

Yes, you can verify Obsidian plugin UI anomalies by capturing DOM and screenshot checks during a live debugging session to validate the runtime behavior and UI state before shipping the plugin release.

Why do I need CDP profiling for Obsidian plugin runtime issues?

You need CDP profiling for Obsidian plugin runtime issues because it allows you to profile focused operations, run small eval probes, and verify health by identifying startup errors and performance bottlenecks in a live vault.

Does Obsidian plugin debugging work without affecting my user vault?

Yes, debugging works without affecting your user vault by disabling and reinstalling plugins in a test vault, running health checks, and preserving your data.json file during deterministic resets and safe repros.