Obsidian Plugin Performance Diagnose

This skill is specifically for attributing Obsidian performance problems to individual plugins. Unlike general vault audits, it focuses on precise measurement, CPU profiling, and automated isolation of the culprit plugin.

When to Use This Skill

• A specific plugin is suspected of causing performance degradation
• Obsidian startup is slow and the user wants to know which plugin is responsible
• Memory usage is unexpectedly high and leaking from a plugin
• UI lag or typing delay correlates with a plugin's activity
• The user wants to isolate a regression without manually toggling safe mode
• Performance profiling via Chrome DevTools is needed to see exact call-stack attribution

Overview

Community plugins are the most common cause of Obsidian performance issues. This skill provides four methods of attribution, from coarse to precise: