[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F89KF5E90HMWH39PF8APR3":3,"skill-same:01M6F89KF5E90HMWH39PF8APR3":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6F89KF5E90HMWH39PF8APR3","obsidian-incident-runbook",null,"Troubleshoot Obsidian plugin failures with systematic incident response.\nUse when plugins crash, data is corrupted, or users report critical issues\nwith your Obsidian plugin.\nTrigger with phrases like \"obsidian crash\", \"obsidian plugin broken\",\n\"obsidian incident\", \"debug obsidian failure\", \"obsidian emergency\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1981,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fobsidian-pack\u002Fskills\u002Fobsidian-incident-runbook\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"obsidian incident runbook","runbook","obsidian","incident","use","when","corrupted","with","users","trigger","io","critical","systematic","read","broken","node","Bash","data","issues","debug","troubleshoot","incident response","2026-11-10 10:12:30",false,"---\nname: obsidian-incident-runbook\ndescription: |\n  Troubleshoot Obsidian plugin failures with systematic incident response.\n  Use when plugins crash, data is corrupted, or users report critical issues\n  with your Obsidian plugin.\n  Trigger with phrases like \"obsidian crash\", \"obsidian plugin broken\",\n  \"obsidian incident\", \"debug obsidian failure\", \"obsidian emergency\".\nallowed-tools: Read, Grep, Bash(node:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Obsidian Incident Runbook\n\n## Overview\nSystematic procedures for diagnosing and resolving Obsidian plugin incidents.\n\n## Prerequisites\n- Access to affected system\u002Fvault\n- Developer Console access\n- Plugin source code access\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Data loss\u002Fcorruption | Immediate | Notes deleted, vault corrupted |\n| P2 | Plugin unusable | \u003C 1 hour | Crash on load, all features broken |\n| P3 | Feature degraded | \u003C 4 hours | One feature not working |\n| P4 | Minor issue | Next release | UI glitch, minor inconvenience |\n\n## Instructions\n\n### Step 1: Quick Triage\n```markdown\n## Initial Assessment\n\n1. **Identify the issue**\n   - What is the user-reported symptom?\n   - When did it start?\n   - What changed (Obsidian update, plugin update, new plugins)?\n\n2. **Check the basics**\n   - [ ] Obsidian version?\n   - [ ] Plugin version?\n   - [ ] Desktop or mobile?\n   - [ ] Operating system?\n\n3. **Reproduce the issue**\n   - [ ] Can you reproduce it?\n   - [ ] Is it consistent or intermittent?\n   - [ ] Does it happen in a new vault?\n```\n\n### Step 2: Gather Diagnostic Information\n```markdown\n## Diagnostic Commands\n\n### In Obsidian (Ctrl\u002FCmd+Shift+I)\n\n1. **Check Console for errors:**\n   - Look for red error messages\n   - Note any stack traces\n   - Check for repeated errors\n\n2. **Check plugin status:**\n   ```javascript\n   \u002F\u002F In console\n   app.plugins.getPlugin('my-plugin-id')\n   ```\n\n3. **Check settings:**\n   ```javascript\n   \u002F\u002F View plugin settings\n   app.plugins.getPlugin('my-plugin-id').settings\n   ```\n\n4. **Check loaded status:**\n   ```javascript\n   \u002F\u002F Is plugin loaded?\n   app.plugins.enabledPlugins.has('my-plugin-id')\n   ```\n\n### File System Checks\n\n```bash\n# Check plugin files exist\nls -la \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002F\n\n# Check for corrupt JSON\ncat \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002Fmanifest.json | jq .\ncat \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002Fdata.json | jq .\n\n# Check file permissions\nls -la \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002F*\n```\n```\n\n### Step 3: Decision Tree\n```\nPlugin not loading?\n├─ Error in console?\n│   ├─ \"Cannot find module\" → Missing dependency, rebuild plugin\n│   ├─ Syntax error → Check main.js, rebuild\n│   ├─ \"Plugin failed to load\" → Check manifest.json\n│   └─ Runtime error → Check onload() code\n├─ No error, plugin enabled but not working?\n│   ├─ Commands not appearing → Check addCommand() calls\n│   ├─ Settings not showing → Check addSettingTab()\n│   └─ Features not working → Check specific feature code\n└─ Plugin not in list?\n    ├─ Check .obsidian\u002Fplugins folder\n    └─ Check community-plugins.json\n\nData corruption suspected?\n├─ Settings corrupted → Delete data.json, restart\n├─ Notes corrupted → Check recent vault backups\n├─ Links broken → Run link consistency check\n└─ Frontmatter corrupted → Parse and fix YAML\n```\n\n### Step 4: Common Fixes by Error Type\n\n#### Plugin Fails to Load\n```bash\n# Fix 1: Rebuild plugin\ncd \u002Fpath\u002Fto\u002Fplugin\nnpm run build\n\n# Fix 2: Reset plugin data\nrm \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002Fdata.json\n\n# Fix 3: Reinstall plugin\nrm -rf \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\n# Reinstall from community plugins or manually\n```\n\n#### Settings Corrupted\n```javascript\n\u002F\u002F In console - reset to defaults\nconst plugin = app.plugins.getPlugin('my-plugin-id');\nplugin.settings = { \u002F* DEFAULT_SETTINGS *\u002F };\nawait plugin.saveSettings();\n\u002F\u002F Restart Obsidian\n```\n\n#### Crash on Specific File\n```javascript\n\u002F\u002F Identify problematic file\n\u002F\u002F Check recent file-open events in console\n\n\u002F\u002F Test with specific file\nconst file = app.vault.getAbstractFileByPath('problematic\u002Ffile.md');\nconst content = await app.vault.read(file);\n\u002F\u002F Check for unusual content\u002Ffrontmatter\n```\n\n### Step 5: Emergency Procedures\n\n#### P1: Data Loss Prevention\n```bash\n#!\u002Fbin\u002Fbash\n# emergency-backup.sh\n\nVAULT_PATH=\"\u002Fpath\u002Fto\u002Fvault\"\nBACKUP_PATH=\"\u002Fpath\u002Fto\u002Fbackup-$(date +%Y%m%d-%H%M%S)\"\n\n# Immediate backup\ncp -r \"$VAULT_PATH\" \"$BACKUP_PATH\"\necho \"Backup created at: $BACKUP_PATH\"\n\n# Disable the problematic plugin\necho '[]' > \"$VAULT_PATH\u002F.obsidian\u002Fcommunity-plugins.json\"\necho \"All plugins disabled. Restart Obsidian.\"\n```\n\n#### P1: Vault Corruption Recovery\n```markdown\n## Vault Recovery Steps\n\n1. **Stop Obsidian immediately**\n   - Don't make any changes\n   - Close all Obsidian windows\n\n2. **Create backup of current state**\n   ```bash\n   cp -r \u002Fpath\u002Fto\u002Fvault \u002Fpath\u002Fto\u002Fvault-corrupted-backup\n   ```\n\n3. **Check for Obsidian sync backup**\n   - Obsidian Sync: Settings > Sync > View version history\n   - Manual: Check your backup solution\n\n4. **Restore from backup**\n   ```bash\n   # If using git\n   cd \u002Fpath\u002Fto\u002Fvault\n   git log --oneline -20  # Find good commit\n   git checkout \u003Ccommit>\n   ```\n\n5. **Disable plugins**\n   - Start Obsidian in safe mode (hold Shift on startup)\n   - Or manually: `echo '[]' > .obsidian\u002Fcommunity-plugins.json`\n```\n\n### Step 6: Communication Templates\n\n#### User Response Template\n```markdown\n## Response to User\n\nHi,\n\nThank you for reporting this issue. I'm sorry you're experiencing problems with [plugin name].\n\n**What I understand:**\n- [Summarize the issue]\n\n**Immediate steps to try:**\n1. [First thing to try]\n2. [Second thing to try]\n\n**Information I need:**\n- Obsidian version (Settings > About)\n- Plugin version\n- Any error messages from Developer Console (Ctrl\u002FCmd+Shift+I)\n\n**Workaround (if available):**\n[Describe temporary workaround]\n\nI'll investigate this as a priority and provide an update within [timeframe].\n```\n\n#### GitHub Issue Template\n```markdown\n## Bug Report\n\n**Plugin:** [name] v[version]\n**Obsidian:** v[version]\n**OS:** [Windows\u002FmacOS\u002FLinux]\n\n### Issue Description\n[Clear description]\n\n### Steps to Reproduce\n1.\n2.\n3.\n\n### Expected Behavior\n[What should happen]\n\n### Actual Behavior\n[What happens]\n\n### Console Errors\n```\n[Paste errors]\n```\n\n### Additional Context\n- Started after: [event\u002Fupdate]\n- Frequency: [always\u002Fsometimes\u002Fonce]\n- Workaround: [if any]\n```\n\n### Step 7: Post-Incident Actions\n\n#### Root Cause Analysis Template\n```markdown\n## Post-Incident Review\n\n**Incident:** [Brief description]\n**Date:** [Date]\n**Duration:** [Time to resolution]\n**Severity:** P[1-4]\n\n### Timeline\n- [Time] - Issue reported\n- [Time] - Investigation started\n- [Time] - Root cause identified\n- [Time] - Fix deployed\n- [Time] - Confirmed resolved\n\n### Root Cause\n[Technical explanation]\n\n### Impact\n- Users affected: [estimate]\n- Data loss: [yes\u002Fno, details]\n\n### Action Items\n- [ ] [Preventive measure] - Due: [date]\n- [ ] [Documentation update] - Due: [date]\n- [ ] [Test coverage] - Due: [date]\n\n### Lessons Learned\n[What can we do better]\n```\n\n## Output\n- Issue identified and categorized\n- Diagnostic information collected\n- Fix applied\n- Users notified\n- Post-incident review completed\n\n## Error Handling\n| Issue | Cause | Quick Fix |\n|-------|-------|-----------|\n| Console not opening | Obsidian crash | Start with --remote-debugging-port |\n| Can't access vault | Permissions | Check file permissions |\n| Plugin won't disable | Corrupt config | Edit community-plugins.json manually |\n| Total crash | Memory\u002Fdisk | Free up system resources |\n\n## Examples\n\n### Quick Health Check Script\n```javascript\n\u002F\u002F Run in Obsidian console\n(function checkPluginHealth() {\n  const plugin = app.plugins.getPlugin('my-plugin-id');\n\n  console.log('Plugin Status:');\n  console.log('- Loaded:', !!plugin);\n  console.log('- Enabled:', app.plugins.enabledPlugins.has('my-plugin-id'));\n\n  if (plugin) {\n    console.log('- Version:', plugin.manifest.version);\n    console.log('- Settings valid:', !!plugin.settings);\n  }\n\n  console.log('\\nRecent Errors:');\n  \u002F\u002F Check for recent errors in your error tracking\n})();\n```\n\n## Resources\n- [Obsidian Forum - Bug Reports](https:\u002F\u002Fforum.obsidian.md\u002Fc\u002Fbug-reports\u002F7)\n- [Obsidian Discord - Help](https:\u002F\u002Fdiscord.gg\u002Fobsidianmd)\n- [Plugin Developer Documentation](https:\u002F\u002Fdocs.obsidian.md\u002FPlugins)\n\n## Next Steps\nFor data handling patterns, see `obsidian-data-handling`.\n","# Obsidian Incident Runbook\n\n## Overview\nSystematic procedures for diagnosing and resolving Obsidian plugin incidents.\n\n## Prerequisites\n- Access to affected system\u002Fvault\n- Developer Console access\n- Plugin source code access\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Data loss\u002Fcorruption | Immediate | Notes deleted, vault corrupted |\n| P2 | Plugin unusable | \u003C 1 hour | Crash on load, all features broken |\n| P3 | Feature degraded | \u003C 4 hours | One feature not working |\n| P4 | Minor issue | Next release | UI glitch, minor inconvenience |\n\n## Instructions\n\n### Step 1: Quick Triage\n```markdown\n## Initial Assessment\n\n1. **Identify the issue**\n   - What is the user-reported symptom?\n   - When did it start?\n   - What changed (Obsidian update, plugin update, new plugins)?\n\n2. **Check the basics**\n   - [ ] Obsidian version?\n   - [ ] Plugin version?\n   - [ ] Desktop or mobile?\n   - [ ] Operating system?\n\n3. **Reproduce the issue**\n   - [ ] Can you reproduce it?\n   - [ ] Is it consistent or intermittent?\n   - [ ] Does it happen in a new vault?\n```\n\n### Step 2: Gather Diagnostic Information\n```markdown\n## Diagnostic Commands\n\n### In Obsidian (Ctrl\u002FCmd+Shift+I)\n\n1. **Check Console for errors:**\n   - Look for red error messages\n   - Note any stack traces\n   - Check for repeated errors\n\n2. **Check plugin status:**\n   ```javascript\n   \u002F\u002F In console\n   app.plugins.getPlugin('my-plugin-id')\n   ```\n\n3. **Check settings:**\n   ```javascript\n   \u002F\u002F View plugin settings\n   app.plugins.getPlugin('my-plugin-id').settings\n   ```\n\n4. **Check loaded status:**\n   ```javascript\n   \u002F\u002F Is plugin loaded?\n   app.plugins.enabledPlugins.has('my-plugin-id')\n   ```\n\n### File System Checks\n\n```bash\n# Check plugin files exist\nls -la \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002F\n\n# Check for corrupt JSON\ncat \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002Fmanifest.json | jq .\ncat \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002Fdata.json | jq .\n\n# Check file permissions\nls -la \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002F*\n```\n```\n\n### Step 3: Decision Tree\n```\nPlugin not loading?\n├─ Error in console?\n│   ├─ \"Cannot find module\" → Missing dependency, rebuild plugin\n│   ├─ Syntax error → Check main.js, rebuild\n│   ├─ \"Plugin failed to load\" → Check manifest.json\n│   └─ Runtime error → Check onload() code\n├─ No error, plugin enabled but not working?\n│   ├─ Commands not appearing → Check addCommand() calls\n│   ├─ Settings not showing → Check addSettingTab()\n│   └─ Features not working → Check specific feature code\n└─ Plugin not in list?\n    ├─ Check .obsidian\u002Fplugins folder\n    └─ Check community-plugins.json\n\nData corruption suspected?\n├─ Settings corrupted → Delete data.json, restart\n├─ Notes corrupted → Check recent vault backups\n├─ Links broken → Run link consistency check\n└─ Frontmatter corrupted → Parse and fix YAML\n```\n\n### Step 4: Common Fixes by Error Type\n\n#### Plugin Fails to Load\n```bash\n# Fix 1: Rebuild plugin\ncd \u002Fpath\u002Fto\u002Fplugin\nnpm run build\n\n# Fix 2: Reset plugin data\nrm \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\u002Fdata.json\n\n# Fix 3: Reinstall plugin\nrm -rf \u002Fpath\u002Fto\u002Fvault\u002F.obsidian\u002Fplugins\u002Fmy-plugin\n# Reinstall from community plugins or manually\n```\n\n#### Settings Corrupted\n```javascript\n\u002F\u002F In console - reset to defaults\nconst plugin = app.plugins.getPlugin('my-plugin-id');\nplugin.settings = { \u002F* DEFAULT_SETTINGS *\u002F };\nawait plugin.saveSettings();\n\u002F\u002F Restart Obsidian\n```\n\n#### Crash on Specific File\n```javascript\n\u002F\u002F Identify problematic file\n\u002F\u002F Check recent file-open events in console\n\n\u002F\u002F Test with specific file\nconst file = app.vault.getAbstractFileByPath('problematic\u002Ffile.md');\nconst content = await app.vault.read(file);\n\u002F\u002F Check for unusual content\u002Ffrontmatter\n```\n\n### Step 5: Emergency Procedures\n\n#### P1: Data Loss Prevention\n```bash\n#!\u002Fbin\u002Fbash\n# emergency-backup.sh\n\nVAULT_PATH=\"\u002Fpath\u002Fto\u002Fvault\"\nBACKUP_PATH=\"\u002Fpath\u002Fto\u002Fbackup-$(date +%Y%m%d-%H%M%S)\"\n\n# Immediate backup\ncp -r \"$VAULT_PATH\" \"$BACKUP_PATH\"\necho \"Backup created at: $BACKUP_PATH\"\n\n# Disable the problematic plugin\necho '[]' > \"$VAULT_PATH\u002F.obsidian\u002Fcommunity-plugins.json\"\necho \"All plugins disabled. Restart Obsidian.\"\n```\n\n#### P1: Vault Corruption Recovery\n```markdown\n## Vault Recovery Steps\n\n1. **Stop Obsidian immediately**\n   - Don't make any changes\n   - Close all Obsidian windows\n\n2. **Create backup of current state**\n   ```bash\n   cp -r \u002Fpath\u002Fto\u002Fvault \u002Fpath\u002Fto\u002Fvault-corrupted-backup\n   ```\n\n3. **Check for Obsidian sync backup**\n   - Obsidian Sync: Settings > Sync > View version history\n   - Manual: Check your backup solution\n\n4. **Restore from backup**\n   ```bash\n   # If using git\n   cd \u002Fpath\u002Fto\u002Fvault\n   git log --oneline -20  # Find good commit\n   git checkout \u003Ccommit>\n   ```\n\n5. **Disable plugins**\n   - Start Obsidian in safe mode (hold Shift on startup)\n   - Or manually: `echo '[]' > .obsidian\u002Fcommunity-plugins.json`\n```\n\n### Step 6: Communication Templates\n\n#### User Response Template\n```markdown\n## Response to User\n\nHi,\n\nThank you for reporting this issue. I'm sorry you're experiencing problems with [plugin name].\n\n**What I understand:**\n- [Summarize the issue]\n\n**Immediate steps to try:**\n1. [First thing to try]\n2. [Second thing to try]\n\n**Information I need:**\n- Obsidian version (Settings > About)\n- Plugin version\n- Any error messages from Developer Console (Ctrl\u002FCmd+Shift+I)\n\n**Workaround (if available):**\n[Describe temporary workaround]\n\nI'll investigate this as a priority and provide an update within [timeframe].\n```\n\n#### GitHub Issue Template\n```markdown\n## Bug Report\n\n**Plugin:** [name] v[version]\n**Obsidian:** v[version]\n**OS:** [Windows\u002FmacOS\u002FLinux]\n\n### Issue Description\n[Clear description]\n\n### Steps to Reproduce\n1.\n2.\n3.\n\n### Expected Behavior\n[What should happen]\n\n### Actual Behavior\n[What happens]\n\n### Console Errors\n```\n[Paste errors]\n```\n\n### Additional Context\n- Started after: [event\u002Fupdate]\n- Frequency: [always\u002Fsometimes\u002Fonce]\n- Workaround: [if any]\n```\n\n### Step 7: Post-Incident Actions\n\n#### Root Cause Analysis Template\n```markdown\n## Post-Incident Review\n\n**Incident:** [Brief description]\n**Date:** [Date]\n**Duration:** [Time to resolution]\n**Severity:** P[1-4]\n\n### Timeline\n- [Time] - Issue reported\n- [Time] - Investigation started\n- [Time] - Root cause identified\n- [Time] - Fix deployed\n- [Time] - Confirmed resolved\n\n### Root Cause\n[Technical explanation]\n\n### Impact\n- Users affected: [estimate]\n- Data loss: [yes\u002Fno, details]\n\n### Action Items\n- [ ] [Preventive measure] - Due: [date]\n- [ ] [Documentation update] - Due: [date]\n- [ ] [Test coverage] - Due: [date]\n\n### Lessons Learned\n[What can we do better]\n```\n\n## Output\n- Issue identified and categorized\n- Diagnostic information collected\n- Fix applied\n- Users notified\n- Post-incident review completed\n\n## Error Handling\n| Issue | Cause | Quick Fix |\n|-------|-------|-----------|\n| Console not opening | Obsidian crash | Start with --remote-debugging-port |\n| Can't access vault | Permissions | Check file permissions |\n| Plugin won't disable | Corrupt config | Edit community-plugins.json manually |\n| Total crash | Memory\u002Fdisk | Free up system resources |\n\n## Examples\n\n### Quick Health Check Script\n```javascript\n\u002F\u002F Run in Obsidian console\n(function checkPluginHealth() {\n  const plugin = app.plugins.getPlugin('my-plugin-id');\n\n  console.log('Plugin Status:');\n  console.log('- Loaded:', !!plugin);\n  console.log('- Enabled:', app.plugins.enabledPlugins.has('my-plugin-id'));\n\n  if (plugin) {\n    console.log('- Version:', plugin.manifest.version);\n    console.log('- Settings valid:', !!plugin.settings);\n  }\n\n  console.log('\\nRecent Errors:');\n  \u002F\u002F Check for recent errors in your error tracking\n})();\n```\n\n## Resources\n- [Obsidian Forum - Bug Reports](https:\u002F\u002Fforum.obsidian.md\u002Fc\u002Fbug-reports\u002F7)\n- [Obsidian Discord - Help](https:\u002F\u002Fdiscord.gg\u002Fobsidianmd)\n- [Plugin Developer Documentation](https:\u002F\u002Fdocs.obsidian.md\u002FPlugins)\n\n## Next Steps\nFor data handling patterns, see `obsidian-data-handling`.\n",{"name":5,"author":51,"license":15,"version":52,"description":53,"allowed-tools":54},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Troubleshoot Obsidian plugin failures with systematic incident response.\nUse when plugins crash, data is corrupted, or users report critical issues\nwith your Obsidian plugin.\nTrigger with phrases like \"obsidian crash\", \"obsidian plugin broken\",\n\"obsidian incident\", \"debug obsidian failure\", \"obsidian emergency\".\n","Read, Grep, Bash(node:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fobsidian-pack\u002Fskills\u002Fobsidian-incident-runbook",231,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-12 03:15:57",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill obsidian-incident-runbook",{"tool":70,"command":71},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill obsidian-incident-runbook",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill obsidian-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fobsidian-pack\u002Fskills\u002Fobsidian-incident-runbook\u002FSKILL.md",true,[],[79,119,143,168,194,216],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":46},"01M6FEGPPK0ZTKCCM0R3E3KS33","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,28,111,112,113,114,115,116,117,118],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","component","routing","state management","state","shadcn","file","ui","Tools","Tailwind","html","single-file","simple","ui components","multi","for","jsx","suite",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":46},"01M6FEE9VTK1W4GY21AKREJXRG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[131,132,133,98,134,135,94,136,137,138,108,139,140,141,142,31,116],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","logs","applications","behavior","local",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":46},"01M6FE20F7ZTQBFWKF4MPJ2SBX","neuropixels-analysis","Neuropixels neural recording analysis. Load SpikeGLX\u002FOpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen\u002FIBL curation, AI-assisted visual analysis, for Neuropixels 1.0\u002F2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FSKILL.md",[],[151,152,153,154,41,155,156,157,28,158,159,160,161,162,163,164,31,165,166,167,116,29],"analysis","neuropixels analysis","spike","metrics","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":46},"01M6FDP0PDK6F1GGX395C7625Z","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[179,180,181,182,183,184,185,186,187,188,189,190,191,32,31,116,192,29,193],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","Existing","new",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":198,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":46},"01M6FDM8Y7VK7NYG9SM7QPA3PW","notebooklm","Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FSKILL.md",[201],{"categoryNo":176,"categoryName":177,"taxonomyType":90,"taxonomyTypeDesc":91},[196,203,204,205,206,207,208,138,209,210,28,211,212,213,214,116,215],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":229,"publishedAt":46},"01M6FDHPXE10J3XGTCH5HBHS1M","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FSKILL.md",[223,226],{"categoryNo":224,"categoryName":225,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":227,"categoryName":228,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000016","图像与多媒体",[230,231,232,180,233,109,234,235,185,28,236,32,237,238,239,116,240,29],"slack gif creator","slack","gif","validation","constraints","Animation","me","make","Utilities","concepts","request"]