[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F6JV0SRDTYERCHEBG4MFGC":3,"skill-same:01M6F6JV0SRDTYERCHEBG4MFGC":77},{"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":18,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6F6JV0SRDTYERCHEBG4MFGC","exa-incident-runbook",null,"Execute Exa incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Exa-related outages, investigating errors,\nor running post-incident reviews for Exa integration failures.\nTrigger with phrases like \"exa incident\", \"exa outage\",\n\"exa down\", \"exa on-call\", \"exa emergency\", \"exa broken\".","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\u002Fexa-pack\u002Fskills\u002Fexa-incident-runbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"runbook","exa incident runbook","exa","incident","call","running","when","down","for","errors","reviews","with","post","trigger","io","incident response","use","read","broken","curl","grep","postmortem","Bash","post-incident","kubectl","integration","2026-11-10 10:12:30",false,"---\nname: exa-incident-runbook\ndescription: |\n  Execute Exa incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Exa-related outages, investigating errors,\n  or running post-incident reviews for Exa integration failures.\n  Trigger with phrases like \"exa incident\", \"exa outage\",\n  \"exa down\", \"exa on-call\", \"exa emergency\", \"exa broken\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Exa Incident Runbook\n\n## Overview\nRapid incident response procedures for Exa-related outages.\n\n## Prerequisites\n- Access to Exa dashboard and status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- Communication channels (Slack, PagerDuty)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | Exa API unreachable |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, non-critical errors |\n| P4 | No user impact | Next business day | Monitoring gaps |\n\n## Quick Triage\n\n```bash\n# 1. Check Exa status\ncurl -s https:\u002F\u002Fstatus.exa.com | jq\n\n# 2. Check our integration health\ncurl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.exa'\n\n# 3. Check error rate (last 5 min)\ncurl -s localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(exa_errors_total[5m])\n\n# 4. Recent error logs\nkubectl logs -l app=exa-integration --since=5m | grep -i error | tail -20\n```\n\n## Decision Tree\n\n```\nExa API returning errors?\n├─ YES: Is status.exa.com showing incident?\n│   ├─ YES → Wait for Exa to resolve. Enable fallback.\n│   └─ NO → Our integration issue. Check credentials, config.\n└─ NO: Is our service healthy?\n    ├─ YES → Likely resolved or intermittent. Monitor.\n    └─ NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 - Authentication\n```bash\n# Verify API key is set\nkubectl get secret exa-secrets -o jsonpath='{.data.api-key}' | base64 -d\n\n# Check if key was rotated\n# → Verify in Exa dashboard\n\n# Remediation: Update secret and restart pods\nkubectl create secret generic exa-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -\nkubectl rollout restart deployment\u002Fexa-integration\n```\n\n### 429 - Rate Limited\n```bash\n# Check rate limit headers\ncurl -v https:\u002F\u002Fapi.exa.com 2>&1 | grep -i rate\n\n# Enable request queuing\nkubectl set env deployment\u002Fexa-integration RATE_LIMIT_MODE=queue\n\n# Long-term: Contact Exa for limit increase\n```\n\n### 500\u002F503 - Exa Errors\n```bash\n# Enable graceful degradation\nkubectl set env deployment\u002Fexa-integration EXA_FALLBACK=true\n\n# Notify users of degraded service\n# Update status page\n\n# Monitor Exa status for resolution\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n? P1 INCIDENT: Exa Integration\nStatus: INVESTIGATING\nImpact: [Describe user impact]\nCurrent action: [What you're doing]\nNext update: [Time]\nIncident commander: @[name]\n```\n\n### External (Status Page)\n```\nExa Integration Issue\n\nWe're experiencing issues with our Exa integration.\nSome users may experience [specific impact].\n\nWe're actively investigating and will provide updates.\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\n# Generate debug bundle\n.\u002Fscripts\u002Fexa-debug-bundle.sh\n\n# Export relevant logs\nkubectl logs -l app=exa-integration --since=1h > incident-logs.txt\n\n# Capture metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=exa_errors_total&start=2h\" > metrics.json\n```\n\n### Postmortem Template\n```markdown\n## Incident: Exa [Error Type]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n\n### Summary\n[1-2 sentence description]\n\n### Timeline\n- HH:MM - [Event]\n- HH:MM - [Event]\n\n### Root Cause\n[Technical explanation]\n\n### Impact\n- Users affected: N\n- Revenue impact: $X\n\n### Action Items\n- [ ] [Preventive measure] - Owner - Due date\n```\n\n## Instructions\n\n### Step 1: Quick Triage\nRun the triage commands to identify the issue source.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Exa-side or internal.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders.\n\n## Output\n- Issue identified and categorized\n- Remediation applied\n- Stakeholders notified\n- Evidence collected for postmortem\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status page | Network issue | Use mobile or VPN |\n| kubectl fails | Auth expired | Re-authenticate |\n| Metrics unavailable | Prometheus down | Check backup metrics |\n| Secret rotation fails | Permission denied | Escalate to admin |\n\n## Examples\n\n### One-Line Health Check\n```bash\ncurl -sf https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.exa.status' || echo \"UNHEALTHY\"\n```\n\n## Resources\n- [Exa Status Page](https:\u002F\u002Fstatus.exa.com)\n- [Exa Support](https:\u002F\u002Fsupport.exa.com)\n\n## Next Steps\nFor data handling, see `exa-data-handling`.","# Exa Incident Runbook\n\n## Overview\nRapid incident response procedures for Exa-related outages.\n\n## Prerequisites\n- Access to Exa dashboard and status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- Communication channels (Slack, PagerDuty)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | Exa API unreachable |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, non-critical errors |\n| P4 | No user impact | Next business day | Monitoring gaps |\n\n## Quick Triage\n\n```bash\n# 1. Check Exa status\ncurl -s https:\u002F\u002Fstatus.exa.com | jq\n\n# 2. Check our integration health\ncurl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.exa'\n\n# 3. Check error rate (last 5 min)\ncurl -s localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(exa_errors_total[5m])\n\n# 4. Recent error logs\nkubectl logs -l app=exa-integration --since=5m | grep -i error | tail -20\n```\n\n## Decision Tree\n\n```\nExa API returning errors?\n├─ YES: Is status.exa.com showing incident?\n│   ├─ YES → Wait for Exa to resolve. Enable fallback.\n│   └─ NO → Our integration issue. Check credentials, config.\n└─ NO: Is our service healthy?\n    ├─ YES → Likely resolved or intermittent. Monitor.\n    └─ NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 - Authentication\n```bash\n# Verify API key is set\nkubectl get secret exa-secrets -o jsonpath='{.data.api-key}' | base64 -d\n\n# Check if key was rotated\n# → Verify in Exa dashboard\n\n# Remediation: Update secret and restart pods\nkubectl create secret generic exa-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -\nkubectl rollout restart deployment\u002Fexa-integration\n```\n\n### 429 - Rate Limited\n```bash\n# Check rate limit headers\ncurl -v https:\u002F\u002Fapi.exa.com 2>&1 | grep -i rate\n\n# Enable request queuing\nkubectl set env deployment\u002Fexa-integration RATE_LIMIT_MODE=queue\n\n# Long-term: Contact Exa for limit increase\n```\n\n### 500\u002F503 - Exa Errors\n```bash\n# Enable graceful degradation\nkubectl set env deployment\u002Fexa-integration EXA_FALLBACK=true\n\n# Notify users of degraded service\n# Update status page\n\n# Monitor Exa status for resolution\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n? P1 INCIDENT: Exa Integration\nStatus: INVESTIGATING\nImpact: [Describe user impact]\nCurrent action: [What you're doing]\nNext update: [Time]\nIncident commander: @[name]\n```\n\n### External (Status Page)\n```\nExa Integration Issue\n\nWe're experiencing issues with our Exa integration.\nSome users may experience [specific impact].\n\nWe're actively investigating and will provide updates.\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\n# Generate debug bundle\n.\u002Fscripts\u002Fexa-debug-bundle.sh\n\n# Export relevant logs\nkubectl logs -l app=exa-integration --since=1h > incident-logs.txt\n\n# Capture metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=exa_errors_total&start=2h\" > metrics.json\n```\n\n### Postmortem Template\n```markdown\n## Incident: Exa [Error Type]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n\n### Summary\n[1-2 sentence description]\n\n### Timeline\n- HH:MM - [Event]\n- HH:MM - [Event]\n\n### Root Cause\n[Technical explanation]\n\n### Impact\n- Users affected: N\n- Revenue impact: $X\n\n### Action Items\n- [ ] [Preventive measure] - Owner - Due date\n```\n\n## Instructions\n\n### Step 1: Quick Triage\nRun the triage commands to identify the issue source.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Exa-side or internal.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders.\n\n## Output\n- Issue identified and categorized\n- Remediation applied\n- Stakeholders notified\n- Evidence collected for postmortem\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status page | Network issue | Use mobile or VPN |\n| kubectl fails | Auth expired | Re-authenticate |\n| Metrics unavailable | Prometheus down | Check backup metrics |\n| Secret rotation fails | Permission denied | Escalate to admin |\n\n## Examples\n\n### One-Line Health Check\n```bash\ncurl -sf https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.exa.status' || echo \"UNHEALTHY\"\n```\n\n## Resources\n- [Exa Status Page](https:\u002F\u002Fstatus.exa.com)\n- [Exa Support](https:\u002F\u002Fsupport.exa.com)\n\n## Next Steps\nFor data handling, see `exa-data-handling`.",{"name":5,"author":50,"license":15,"version":51,"description":52,"allowed-tools":53},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Exa incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Exa-related outages, investigating errors,\nor running post-incident reviews for Exa integration failures.\nTrigger with phrases like \"exa incident\", \"exa outage\",\n\"exa down\", \"exa on-call\", \"exa emergency\", \"exa broken\".\n","Read, Grep, Bash(kubectl:*), Bash(curl:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fexa-pack\u002Fskills\u002Fexa-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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill exa-incident-runbook",{"tool":69,"command":70},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill exa-incident-runbook",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill exa-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fexa-pack\u002Fskills\u002Fexa-incident-runbook\u002FSKILL.md",true,[],[78,117,141,167,194,216],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":91,"publishedAt":45},"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",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,35,110,111,112,113,114,27,115,116],"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":128,"publishedAt":45},"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",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[129,130,131,97,132,133,93,134,135,136,107,137,138,139,140,30,27],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","logs","applications","behavior","local",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":45},"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",[],[149,150,151,152,153,154,155,156,35,157,158,159,160,161,162,163,30,164,165,166,27,25],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","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":82,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":45},"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":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",[178,179,180,181,182,183,184,185,186,187,188,189,190,191,30,27,192,25,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":45},"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":89,"taxonomyTypeDesc":90},[196,203,204,205,206,207,208,136,209,210,35,211,212,213,214,27,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":82,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":229,"publishedAt":45},"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":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":227,"categoryName":228,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000016","图像与多媒体",[230,231,232,179,233,108,234,235,184,35,236,191,237,238,239,27,240,25],"slack gif creator","slack","gif","validation","constraints","Animation","me","make","Utilities","concepts","request"]