obsidian-incident-runbook
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".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- obsidian-incident-runbook
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- 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".
- allowed-tools
- Read, Grep, Bash(node:*)
- compatible-with
- claude-code, codex, openclaw
02 资源文件 1
- 参考文档references/implementation-guide.md6.8 KB
03 SKILL.md 正文
Obsidian Incident Runbook
Overview
Systematic procedures for diagnosing and resolving Obsidian plugin incidents.
Prerequisites
- Access to affected system/vault
- Developer Console access
- Plugin source code access
Instructions
Step 1: Quick Triage
For full implementation details and code examples, load:
references/implementation-guide.md
Output
- Issue identified and categorized
- Diagnostic information collected
- Fix applied
- Users notified
- Post-incident review completed
Error Handling
| 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 |
Resources
Next Steps
For data handling patterns, see obsidian-data-handling.
Examples
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.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.