Troubleshoot Obsidian plugin failures with systematic incident response. Use when plugins crash, data is corrupted, or users report critical issues with your Obsidian plugin. Trigger with phrases like "obsidian crash", "obsidian plugin broken", "obsidian incident", "debug obsidian failure", "obsidian emergency".
From obsidian-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin obsidian-packThis skill is limited to using the following tools:
references/implementation-guide.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.
Systematic procedures for diagnosing and resolving Obsidian plugin incidents.
For full implementation details and code examples, load:
references/implementation-guide.md
| Issue | Cause | Quick Fix |
|---|---|---|
| Console not opening | Obsidian crash | Start with --remote-debugging-port |
| Can't access vault | Permissions | Check file permissions |
| Plugin won't disable | Corrupt config | Edit community-plugins.json manually |
| Total crash | Memory/disk | Free up system resources |
For data handling patterns, see obsidian-data-handling.
Basic usage: Apply obsidian incident runbook to a standard project setup with default configuration options.
Advanced scenario: Customize obsidian incident runbook for production environments with multiple constraints and team-specific requirements.