Obsidian Performance

This skill treats performance diagnostics as a programmatic audit. Instead of guiding the user through manual UI clicks, the agent evaluates JavaScript directly in Obsidian's runtime (via CDP Runtime.evaluate or CLI obsidian eval) to inspect vault state, plugin impact, configuration, and metadata health. Fixes are applied through the same APIs.

When to Use This Skill

• Obsidian startup is slow or getting slower over time
• The app feels laggy during typing, switching notes, or rendering
• Memory usage is unexpectedly high
• A specific plugin is suspected of causing performance degradation
• The vault has grown large and the user wants an automated health audit
• Console errors or warnings appear repeatedly
• The user wants to identify and fix broken links, orphans, or circular references
• Performance profiling via Chrome DevTools is needed

Overview

Obsidian performance issues usually stem from one of four sources: