[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F6ZWEBRCYPCTRT3QSR8D7H":3,"skill-same:01M6F6ZWEBRCYPCTRT3QSR8D7H":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},"01M6F6ZWEBRCYPCTRT3QSR8D7H","granola-incident-runbook",null,"Incident response procedures for Granola meeting capture issues.\nUse when handling meeting capture failures, system outages,\nor urgent troubleshooting situations.\nTrigger with phrases like \"granola incident\", \"granola outage\",\n\"granola emergency\", \"granola not recording\", \"granola down\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1992,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fgranola-pack\u002Fskills\u002Fgranola-incident-runbook\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"runbook","granola incident runbook","incident","granola","use","when","down","for","recording","with","trigger","io","incident response","edit","write","read","capture","curl","troubleshooting","system","Bash","issues","2026-11-10 10:12:30",false,"---\nname: granola-incident-runbook\ndescription: |\n  Incident response procedures for Granola meeting capture issues.\n  Use when handling meeting capture failures, system outages,\n  or urgent troubleshooting situations.\n  Trigger with phrases like \"granola incident\", \"granola outage\",\n  \"granola emergency\", \"granola not recording\", \"granola down\".\nallowed-tools: Read, Write, Edit, Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Granola Incident Runbook\n\n## Overview\nStandard operating procedures for responding to Granola incidents and meeting capture failures.\n\n## Incident Severity Levels\n\n| Level | Description | Response Time | Examples |\n|-------|-------------|---------------|----------|\n| P1 | Critical | \u003C 15 min | Complete outage, data loss |\n| P2 | High | \u003C 1 hour | Recording failures, sync issues |\n| P3 | Medium | \u003C 4 hours | Single user issues, slow processing |\n| P4 | Low | \u003C 24 hours | UI bugs, minor inconveniences |\n\n## Incident Response Flow\n\n```\nIncident Detected\n       ↓\nAssess Severity (5 min)\n       ↓\nCheck Status Page (1 min)\n       ↓\n┌──────────────────────┐\n│ Granola Issue?       │\n├──────────────────────┤\n│ Yes → Workaround     │\n│ No  → Local Debug    │\n└──────────────────────┘\n       ↓\nCommunicate Status\n       ↓\nTrack to Resolution\n       ↓\nPost-Incident Review\n```\n\n## Quick Status Check\n\n### Step 1: Check Granola Status\n```bash\n# Check status page\ncurl -s https:\u002F\u002Fstatus.granola.ai\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# Or visit: https:\u002F\u002Fstatus.granola.ai\n```\n\n### Step 2: Test Local Connectivity\n```bash\n# Test API connectivity\ncurl -I https:\u002F\u002Fapi.granola.ai\u002Fhealth\n\n# Expected: HTTP 200 OK\n```\n\n### Step 3: Check Local App Status\n```bash\n# macOS - Check if Granola is running\npgrep -l Granola\n\n# Check Granola logs\ntail -f ~\u002FLibrary\u002FLogs\u002FGranola\u002Fgranola.log\n```\n\n## Incident: Recording Not Starting\n\n### Symptoms\n- Meeting starts but Granola doesn't record\n- No recording indicator visible\n- Calendar event not detected\n\n### Immediate Actions\n```markdown\n## Quick Fix (\u003C 5 min)\n\n1. [ ] Manually click \"Start Recording\" in Granola\n2. [ ] Check calendar is connected (Settings > Integrations)\n3. [ ] Verify meeting is on synced calendar\n4. [ ] Restart Granola app\n5. [ ] Check audio permissions granted\n```\n\n### Root Cause Investigation\n```markdown\n## Investigate (if quick fix fails)\n\n1. Calendar Sync Issue:\n   - Last sync time?\n   - OAuth token valid?\n   - Correct calendar selected?\n\n2. Audio Permission:\n   - System Preferences > Security > Microphone\n   - Is Granola listed and checked?\n\n3. App State:\n   - Force quit and restart\n   - Clear cache if needed\n   - Check for updates\n```\n\n## Incident: No Audio Captured\n\n### Symptoms\n- Recording indicator shows\n- Transcript is empty or says \"No audio\"\n- Notes are blank\n\n### Immediate Actions\n```markdown\n## Quick Fix\n\n1. [ ] Check audio input device in System Preferences\n2. [ ] Verify physical mic is not muted\n3. [ ] Test mic with other app (Voice Memos)\n4. [ ] Restart Granola app\n5. [ ] Rejoin meeting if possible\n```\n\n### Workaround\n```markdown\n## If Audio Cannot Be Captured\n\n1. Take manual notes during meeting\n2. Record with backup tool (QuickTime, OBS)\n3. Upload\u002Ftranscribe after meeting\n4. Document for post-incident review\n```\n\n## Incident: Processing Stuck\n\n### Symptoms\n- Meeting ended but notes not appearing\n- Processing indicator spinning > 10 min\n- Error message about processing\n\n### Immediate Actions\n```markdown\n## Quick Fix\n\n1. [ ] Wait up to 15 minutes (large meetings take longer)\n2. [ ] Check internet connectivity\n3. [ ] Check Granola status page for delays\n4. [ ] Restart Granola app\n5. [ ] Contact support if > 20 min\n```\n\n### Support Escalation\n```markdown\n## Contact Support\n\nEmail: help@granola.ai\n\nInclude:\n- Meeting date\u002Ftime\n- Meeting ID (if available)\n- Duration of meeting\n- Error messages shown\n- Steps already tried\n```\n\n## Incident: Integration Failure\n\n### Symptoms\n- Notes not syncing to Slack\u002FNotion\u002Fetc.\n- Zapier Zaps failing\n- Error in integration logs\n\n### Immediate Actions\n```markdown\n## Quick Fix\n\n1. [ ] Check integration status (Settings > Integrations)\n2. [ ] Reconnect if showing \"Disconnected\"\n3. [ ] Test integration manually\n4. [ ] Check destination app permissions\n5. [ ] Verify Zapier Zap is enabled\n```\n\n### Manual Workaround\n```markdown\n## Manual Sync\n\nIf integration broken:\n1. Export note as Markdown\n2. Manually paste to Notion\u002FSlack\n3. Create tasks manually in Linear\n4. Update CRM by hand if needed\n```\n\n## Incident: Complete Outage\n\n### Symptoms\n- Granola app won't load\n- Status page shows outage\n- Multiple users affected\n\n### Immediate Actions\n```markdown\n## During Outage\n\n1. [ ] Acknowledge internally (Slack)\n2. [ ] Enable backup note-taking\n3. [ ] Monitor status page\n4. [ ] Document affected meetings\n\nCommunication Template:\n\"Granola is currently experiencing an outage.\nPlease take manual notes. We're monitoring\nthe situation and will update in 30 minutes.\"\n```\n\n### Backup Procedures\n```markdown\n## Alternative Note-Taking\n\n1. Designate note-taker per meeting\n2. Use Google Docs or Notion directly\n3. Record via Zoom\u002FMeet native recording\n4. Upload to Granola when service restored\n```\n\n## Communication Templates\n\n### Internal Notification (Slack)\n```\n:warning: Granola Incident\n\nStatus: [Investigating\u002FIdentified\u002FMonitoring\u002FResolved]\nImpact: [Description of impact]\nWorkaround: [Available workaround]\nETA: [Expected resolution time]\nUpdates: Every 30 minutes\n\nNext update: [Time]\n```\n\n### User Notification (Email)\n```\nSubject: Granola Service Update\n\nWe're aware of issues with [specific issue] affecting\n[scope of impact].\n\nImpact: [What users will experience]\nStatus: [Current status]\nWorkaround: [Steps users can take]\n\nWe'll update you within [timeframe].\n\n- The Granola Team\n```\n\n## Post-Incident\n\n### Incident Report Template\n```markdown\n## Incident Report: [Title]\n\n**Date:** [Date\u002FTime]\n**Duration:** [Start to resolution]\n**Severity:** [P1\u002FP2\u002FP3\u002FP4]\n**Impact:** [Number of users, meetings affected]\n\n**Timeline:**\n- HH:MM - Incident detected\n- HH:MM - Investigation started\n- HH:MM - Root cause identified\n- HH:MM - Resolution applied\n- HH:MM - Service restored\n\n**Root Cause:**\n[Description of what caused the incident]\n\n**Resolution:**\n[What was done to resolve]\n\n**Prevention:**\n[Steps to prevent recurrence]\n\n**Lessons Learned:**\n- [Key takeaways]\n```\n\n### Review Meeting Agenda\n```markdown\n## Post-Incident Review\n\n1. Incident summary (5 min)\n2. Timeline review (10 min)\n3. What went well (5 min)\n4. What could improve (10 min)\n5. Action items (10 min)\n6. Assign owners and deadlines (5 min)\n```\n\n## Emergency Contacts\n\n### Granola Support\n- Email: help@granola.ai\n- Enterprise: dedicated support channel\n- Status: status.granola.ai\n\n### Internal Escalation\n```markdown\n## Escalation Path\n\n1. Primary: [IT Support]\n2. Secondary: [Granola Admin]\n3. Management: [Team Lead]\n4. Executive: [VP\u002FCTO] - P1 only\n```\n\n## Resources\n- [Granola Status](https:\u002F\u002Fstatus.granola.ai)\n- [Support Center](https:\u002F\u002Fgranola.ai\u002Fhelp)\n- [Known Issues](https:\u002F\u002Fgranola.ai\u002Fupdates)\n\n## Next Steps\nProceed to `granola-data-handling` for data management procedures.\n","# Granola Incident Runbook\n\n## Overview\nStandard operating procedures for responding to Granola incidents and meeting capture failures.\n\n## Incident Severity Levels\n\n| Level | Description | Response Time | Examples |\n|-------|-------------|---------------|----------|\n| P1 | Critical | \u003C 15 min | Complete outage, data loss |\n| P2 | High | \u003C 1 hour | Recording failures, sync issues |\n| P3 | Medium | \u003C 4 hours | Single user issues, slow processing |\n| P4 | Low | \u003C 24 hours | UI bugs, minor inconveniences |\n\n## Incident Response Flow\n\n```\nIncident Detected\n       ↓\nAssess Severity (5 min)\n       ↓\nCheck Status Page (1 min)\n       ↓\n┌──────────────────────┐\n│ Granola Issue?       │\n├──────────────────────┤\n│ Yes → Workaround     │\n│ No  → Local Debug    │\n└──────────────────────┘\n       ↓\nCommunicate Status\n       ↓\nTrack to Resolution\n       ↓\nPost-Incident Review\n```\n\n## Quick Status Check\n\n### Step 1: Check Granola Status\n```bash\n# Check status page\ncurl -s https:\u002F\u002Fstatus.granola.ai\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# Or visit: https:\u002F\u002Fstatus.granola.ai\n```\n\n### Step 2: Test Local Connectivity\n```bash\n# Test API connectivity\ncurl -I https:\u002F\u002Fapi.granola.ai\u002Fhealth\n\n# Expected: HTTP 200 OK\n```\n\n### Step 3: Check Local App Status\n```bash\n# macOS - Check if Granola is running\npgrep -l Granola\n\n# Check Granola logs\ntail -f ~\u002FLibrary\u002FLogs\u002FGranola\u002Fgranola.log\n```\n\n## Incident: Recording Not Starting\n\n### Symptoms\n- Meeting starts but Granola doesn't record\n- No recording indicator visible\n- Calendar event not detected\n\n### Immediate Actions\n```markdown\n## Quick Fix (\u003C 5 min)\n\n1. [ ] Manually click \"Start Recording\" in Granola\n2. [ ] Check calendar is connected (Settings > Integrations)\n3. [ ] Verify meeting is on synced calendar\n4. [ ] Restart Granola app\n5. [ ] Check audio permissions granted\n```\n\n### Root Cause Investigation\n```markdown\n## Investigate (if quick fix fails)\n\n1. Calendar Sync Issue:\n   - Last sync time?\n   - OAuth token valid?\n   - Correct calendar selected?\n\n2. Audio Permission:\n   - System Preferences > Security > Microphone\n   - Is Granola listed and checked?\n\n3. App State:\n   - Force quit and restart\n   - Clear cache if needed\n   - Check for updates\n```\n\n## Incident: No Audio Captured\n\n### Symptoms\n- Recording indicator shows\n- Transcript is empty or says \"No audio\"\n- Notes are blank\n\n### Immediate Actions\n```markdown\n## Quick Fix\n\n1. [ ] Check audio input device in System Preferences\n2. [ ] Verify physical mic is not muted\n3. [ ] Test mic with other app (Voice Memos)\n4. [ ] Restart Granola app\n5. [ ] Rejoin meeting if possible\n```\n\n### Workaround\n```markdown\n## If Audio Cannot Be Captured\n\n1. Take manual notes during meeting\n2. Record with backup tool (QuickTime, OBS)\n3. Upload\u002Ftranscribe after meeting\n4. Document for post-incident review\n```\n\n## Incident: Processing Stuck\n\n### Symptoms\n- Meeting ended but notes not appearing\n- Processing indicator spinning > 10 min\n- Error message about processing\n\n### Immediate Actions\n```markdown\n## Quick Fix\n\n1. [ ] Wait up to 15 minutes (large meetings take longer)\n2. [ ] Check internet connectivity\n3. [ ] Check Granola status page for delays\n4. [ ] Restart Granola app\n5. [ ] Contact support if > 20 min\n```\n\n### Support Escalation\n```markdown\n## Contact Support\n\nEmail: help@granola.ai\n\nInclude:\n- Meeting date\u002Ftime\n- Meeting ID (if available)\n- Duration of meeting\n- Error messages shown\n- Steps already tried\n```\n\n## Incident: Integration Failure\n\n### Symptoms\n- Notes not syncing to Slack\u002FNotion\u002Fetc.\n- Zapier Zaps failing\n- Error in integration logs\n\n### Immediate Actions\n```markdown\n## Quick Fix\n\n1. [ ] Check integration status (Settings > Integrations)\n2. [ ] Reconnect if showing \"Disconnected\"\n3. [ ] Test integration manually\n4. [ ] Check destination app permissions\n5. [ ] Verify Zapier Zap is enabled\n```\n\n### Manual Workaround\n```markdown\n## Manual Sync\n\nIf integration broken:\n1. Export note as Markdown\n2. Manually paste to Notion\u002FSlack\n3. Create tasks manually in Linear\n4. Update CRM by hand if needed\n```\n\n## Incident: Complete Outage\n\n### Symptoms\n- Granola app won't load\n- Status page shows outage\n- Multiple users affected\n\n### Immediate Actions\n```markdown\n## During Outage\n\n1. [ ] Acknowledge internally (Slack)\n2. [ ] Enable backup note-taking\n3. [ ] Monitor status page\n4. [ ] Document affected meetings\n\nCommunication Template:\n\"Granola is currently experiencing an outage.\nPlease take manual notes. We're monitoring\nthe situation and will update in 30 minutes.\"\n```\n\n### Backup Procedures\n```markdown\n## Alternative Note-Taking\n\n1. Designate note-taker per meeting\n2. Use Google Docs or Notion directly\n3. Record via Zoom\u002FMeet native recording\n4. Upload to Granola when service restored\n```\n\n## Communication Templates\n\n### Internal Notification (Slack)\n```\n:warning: Granola Incident\n\nStatus: [Investigating\u002FIdentified\u002FMonitoring\u002FResolved]\nImpact: [Description of impact]\nWorkaround: [Available workaround]\nETA: [Expected resolution time]\nUpdates: Every 30 minutes\n\nNext update: [Time]\n```\n\n### User Notification (Email)\n```\nSubject: Granola Service Update\n\nWe're aware of issues with [specific issue] affecting\n[scope of impact].\n\nImpact: [What users will experience]\nStatus: [Current status]\nWorkaround: [Steps users can take]\n\nWe'll update you within [timeframe].\n\n- The Granola Team\n```\n\n## Post-Incident\n\n### Incident Report Template\n```markdown\n## Incident Report: [Title]\n\n**Date:** [Date\u002FTime]\n**Duration:** [Start to resolution]\n**Severity:** [P1\u002FP2\u002FP3\u002FP4]\n**Impact:** [Number of users, meetings affected]\n\n**Timeline:**\n- HH:MM - Incident detected\n- HH:MM - Investigation started\n- HH:MM - Root cause identified\n- HH:MM - Resolution applied\n- HH:MM - Service restored\n\n**Root Cause:**\n[Description of what caused the incident]\n\n**Resolution:**\n[What was done to resolve]\n\n**Prevention:**\n[Steps to prevent recurrence]\n\n**Lessons Learned:**\n- [Key takeaways]\n```\n\n### Review Meeting Agenda\n```markdown\n## Post-Incident Review\n\n1. Incident summary (5 min)\n2. Timeline review (10 min)\n3. What went well (5 min)\n4. What could improve (10 min)\n5. Action items (10 min)\n6. Assign owners and deadlines (5 min)\n```\n\n## Emergency Contacts\n\n### Granola Support\n- Email: help@granola.ai\n- Enterprise: dedicated support channel\n- Status: status.granola.ai\n\n### Internal Escalation\n```markdown\n## Escalation Path\n\n1. Primary: [IT Support]\n2. Secondary: [Granola Admin]\n3. Management: [Team Lead]\n4. Executive: [VP\u002FCTO] - P1 only\n```\n\n## Resources\n- [Granola Status](https:\u002F\u002Fstatus.granola.ai)\n- [Support Center](https:\u002F\u002Fgranola.ai\u002Fhelp)\n- [Known Issues](https:\u002F\u002Fgranola.ai\u002Fupdates)\n\n## Next Steps\nProceed to `granola-data-handling` for data management procedures.\n",{"name":5,"author":51,"license":15,"version":52,"description":53,"allowed-tools":54},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Incident response procedures for Granola meeting capture issues.\nUse when handling meeting capture failures, system outages,\nor urgent troubleshooting situations.\nTrigger with phrases like \"granola incident\", \"granola outage\",\n\"granola emergency\", \"granola not recording\", \"granola down\".\n","Read, Write, Edit, Bash(curl:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fgranola-pack\u002Fskills\u002Fgranola-incident-runbook",233,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-15 01:54:15",{"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 granola-incident-runbook",{"tool":70,"command":71},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill granola-incident-runbook",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill granola-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fgranola-pack\u002Fskills\u002Fgranola-incident-runbook\u002FSKILL.md",true,[],[79,118,142,167,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,31,116,117],"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","jsx","suite",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":129,"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",[125,128],{"categoryNo":126,"categoryName":127,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[130,131,132,98,133,134,94,135,136,137,108,138,139,140,141,33,31],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","logs","applications","behavior","local",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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",[],[150,151,152,153,154,155,156,157,28,158,159,160,161,162,163,164,33,165,32,166,31,29],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","load",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"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",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[178,179,180,181,182,183,184,185,186,187,188,189,190,191,33,31,192,29,193],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","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":175,"categoryName":176,"taxonomyType":90,"taxonomyTypeDesc":91},[196,203,204,205,206,207,208,137,209,210,28,211,212,213,214,31,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,179,233,109,234,235,184,28,236,191,237,238,239,31,240,29],"slack gif creator","slack","gif","validation","constraints","Animation","me","make","Utilities","concepts","request"]